docs(epic): regenerate the epic-status projection at epic completion

[drmoisan]

docs(epic): regenerate the epic-status projection at epic completion

Documentation only. One file changes: docs/features/epics/build-ci-coverage-gate-fidelity/epic-status.md.

Summary

• Records the terminal state of the build-ci-coverage-gate-fidelity epic, whose integration PR Epic: make the C# build, CI, and coverage gates report the truth #566 merged to main as 8bd23551 with all five required checks green on the first run and all nine issues auto-closed as COMPLETED.
• Corrects two defects the epic audit found in the prior projection: feature 457's row omitted PR chore(memory): record two orchestrator lessons from the #457 child run #543 entirely, and the Last updated marker predated data inside its own table.
• Adds the fan-in review results, the five known gaps that merged with the epic, and an explicit record of the one completion requirement that could not be satisfied.

Why

epic-status.md is a generated projection of the epic checkpoint, regenerated at each lifecycle boundary including final integration-PR completion. The prior revision was written before the integration PR existed, so its Integration PR table was empty and its Issues section described all nine issues as pending closure. Both are now resolved and the projection was stale.

What Changed

Section	Change
Header	Status is now COMPLETE; integration branch marked merged and retired; Last updated synchronized with content
Features	494 advanced to worktree_removed; merge_confirmed_at values corrected to the authoritative gh mergedAt timestamps; PR #543 disclosed for feature 457
Integration PR	Populated with PR #566, head 3e61c67e, the five required check results, merge commit 8bd23551, and merge time
Fan-In Review	New — two independent feature-review passes, both zero Blocking, plus the epic-review AC result
Known Gaps	New — #561 through #565, and the resulting partial discharge of leading indicator 2
Checkpoint Completion Status	New — records that require_complete cannot pass and why
Intermittent test	Fifth sample added: the final integration run passed
Issues	Rewritten from "pending closure" to the closed record with per-issue timestamps
Retained Branches	New — disposition of the two local-only unmerged branches

Verification

Completed — the facts recorded in this document were verified against git and gh before it was written: gh pr view 566, gh pr checks 566, gh run view 31867645467, and gh issue view for each of the nine issues. The epic checkpoint passes plain validate_orchestration_artifacts validation.

Recommended — none. This change adds no executable code and no test. CI runs on it because its base is main.

Backward Compatibility / Migration Notes

None. epic-status.md is a generated projection consumed by humans; nothing reads it programmatically. epic.md, the human-authored manifest, is untouched.

Risks and Mitigations

Risk	Mitigation
The projection disagrees with the checkpoint	The checkpoint remains machine-authoritative, and git / gh remain authoritative over both per the cache doctrine. Every figure here was read from gh rather than copied from the checkpoint.

Rollback: revert the commit. No behavior depends on this file.

Review Guide

Single file, single commit. The two sections worth attention are Known Gaps Merged With This Epic, which states that the coverage-threshold contradiction the epic set out to remove still exists, and Checkpoint Completion Status, which records the unsatisfiable require_complete gate rather than working around it.

Follow-ups

• Coverage threshold contradiction remains: CLAUDE.md/csharp.md say 80%, general-unit-test.md/quality-tiers.md say 85%/75%, and two live gates disagree #563 is the substantive open item: the coverage-threshold contradiction remains unreconciled across four governance documents and two live enforcement points.
• CI collects coverage but enforces no threshold: _mstest-coverage.yml never converts to Cobertura or compares a floor #561 and No Pester job in CI: production PowerShell under scripts/vscode has zero CI coverage #562 concern gates that do not exist in CI at all.
• CLAUDE.md cites ci.yml for three toolchain commands the #553 split moved into reusable workflows #564 and Invoke-MSTestWithCoverage.ps1 asserts coverage threshold before Set-Content, leaving the raw un-post-processed Cobertura on disk when the gate fails #565 are small corrections in the epic's own delivered surface.

GitHub Auto-close

None.