bcquality/.gitignore
Copilot 5c4bb480c9 Own knowledge-index generation in BCQuality (runtime + CI), not the consumer
The index is now produced by BCQuality itself: Entry's preparation step
rebuilds knowledge-index.json over the live, already-pruned clone at the start
of every run, and a new CI workflow validates the generator's health
(determinism, full coverage, selection-input integrity). Consumers no longer
invoke or know about the index.

Rebuilding over the pruned clone (vs shipping a committed full-corpus index)
keeps the index exact for any consumer policy: it can never list a denied
article, so policy-excluded rules cannot leak into discovery. READ now states
the index is discovery-only -- a finding must cite an article opened in full,
and rows whose file is absent are discarded before ranking.

- skills/entry.md: new 'Preparation -- knowledge index' precondition
- skills/read.md: index ownership + discovery-only invariant
- microsoft/skills/review/*.md (6): 'BCQuality builds' (not 'the filter emits')
- agent-consumption.md 5a: runtime+CI ownership rationale
- .github/workflows/knowledge-index.yml + scripts/Test-KnowledgeIndex.ps1: generator guard
- .gitignore: never commit the runtime index

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-06-04 14:21:14 +02:00

29 lines
377 B
Text

# Environment
*.env
.env.*
# Python
__pycache__/
*.pyc
*.pyo
.venv/
.pytest_cache/
# Editors
.vs/
.vscode/
.idea/
# OS
.DS_Store
Thumbs.db
# Node (if scripts ever need it)
node_modules/
# Build artifacts
*.log
# Runtime artifact: the knowledge index is rebuilt over each consumer's
# pruned clone by Entry's preparation step; it is never committed.
/knowledge-index.json