docs(regeneration): wrap-up — reconcile IFC-2704 artifacts, knowledge reference, QA checklist
Merged
PO
4mo ago+242+242+012345678901234567890123456789-16-16-01234567890123456789
Summary
Documentation wrap-up for the selective post-merge regeneration work, on top of
pmi-20260713-perf-merge-artifacts-generators (the implementation landed there via #10033).
Documentation-only; no code or generated files change.
Changes
- Reconcile IFC-2704 spec/plan/tasks with shipped reality — the generator-to-artifact cascade
is targeted (capture the generators' tracked output, regenerate only the artifacts that read it,
widen on an unresolved tracked set or a capture failure); the config flag ships enabled by
default; the per-merge log line is at debug level; the selection code shipped as the
selective_regen/andcore/regeneration/packages. Adds the orphan-instance and
generator-failure-isolation edge cases and a remediation task (T046) to land the
integration_dockermerge suite. - New maintenance reference
dev/knowledge/backend/selective-merge-regeneration.md— the
capture-to-dispatch flow, selection, the generator cascade, fallback reasons, and key files;
cross-linked fromarchitecture.mdand the siblingmerge-recompute.md. - Manual QA checklist
dev/specs/ifc-2704-incremental-merge-regen/qa-checklist.md— customer
surface scenarios (selective narrowing, the reversible flag, the direct-merge cascade) plus edge
cases.
How tested
/pre-ci: Python and docs formatters clean, ruff clean, lockfile in sync, generated docs and
generated backend files show no diff. The branch diff versus its base is documentation-only, so
the backend lint / unit / frontend / schema phases are unaffected (code is identical to the
CI-green base).
How to review
Read the three docs. The knowledge reference is the primary new artifact; the spec/plan/tasks
edits are a reconciliation against the implementation already on the base branch.
🤖 Generated with Claude Code