docs(epic): regenerate quickfiler-suite-determinism epic-status after final merge

[drmoisan]

Suggested title

docs(epic): regenerate quickfiler-suite-determinism epic-status after final merge

Summary

• Regenerates the checkpoint-derived sections of the generated status projection
  docs/features/epics/quickfiler-suite-determinism-foundation/epic-status.md now that the epic's
  final integration pull request has landed on main.
• Records the final integration pull request and its CI gate in full: PR fix(quickfiler): suite-determinism foundation epic — remove live test form, repair keyboard-action and explorer-controller contract defects (#445, #449, #491) #595, merged as
  20462ed7fa4f4d9a23c02bc504f20b96b52f3060, gated by workflow run 32593830908 with 5 of 5 checks
  passing, with the run's headSha verified equal to the pull request's headRefOid before the
  gate was accepted.
• Adds a Completion Assessment section that states plainly which of the four epic completion
  requirements are satisfied and which are not, and why.
• Supersedes two kickoff-time notes that the actual outcome overtook, rather than deleting them, so
  a later reader can see what changed and why.
• Records the outstanding worktree cleanup and the reason it could not be performed.
• Documentation only. No production code, test code, build configuration, or workflow file is
  touched by this pull request.

Why

epic-status.md is a generated projection of artifacts/orchestration/epic-orchestrator-state.json,
regenerated by epic-orchestrator at kickoff, at every merge_status transition, at every wave
transition, and at final integration-pull-request completion. The last regeneration before this one
was taken at 2026-08-22T17-05, when the final pull request had not yet been opened. The document
therefore still described the run as in progress and still carried two instructions that the final
merge has since resolved. Regenerating it at the final boundary is the last of the four completion
requirements the epic orchestration procedure defines.

What Changed

Status header and wave table

• Last updated advanced to 2026-08-22T18-05.
• Next step advanced from open_final_integration_pr_to_main_closing_445_449_491 to
  EPIC_DELIVERED_WITH_ONE_CHILD_DESCOPED.
• The integration branch is marked as merged to main; wave 0 moves from in_progress to
  completed_with_one_child_descoped.
• The feature-status row for Bug: winformspumphost-tests-load-flaky-visible-window #511 now names its disposition inline (halted, premise_falsified,
  descoped) rather than showing a bare worktree_created that reads as unfinished work.

Final Integration Pull Request section

Previously a table of five em-dashes. Now records pr_number, pr_url, base_branch,
head_branch, head_sha, ci_gate, merge_commit_sha and merged_at, plus two new subsections:

• CI gate detail — a per-check table, and the observation that this pull request received real
  GitHub Actions CI precisely because it targets main, which is in the pull_request trigger list
  of .github/workflows/ci.yml, unlike every child pull request in the epic. It also records that
  scripts/orchestration/Invoke-CiGateParser.ps1 does not exist in this repository, so the gate was
  evaluated directly from gh pr checks and gh run view, and is reported parser-absent rather
  than fabricated or silently skipped.
• Issue disposition, verified after the merge — a table of all twelve issue states as read back
  with gh issue view after the merge: 445, 449 and 491 CLOSED; 511, 571, 583, 584, 586, 589, 592,
  593 and 594 OPEN.

Superseded notes

Two notes are marked superseded in place rather than removed:

• The kickoff-time expectation that the final pull request must carry the closing keywords for all
  five of 445, 449, 491, 511 and 571. It carried closing keywords for the three children that
  actually landed. 511 and 571 were left open deliberately, because closing them would assert a fix
  that does not exist.
• The instruction to re-check child Bug: quickfiler-test-form1-live-form #491's coverage AC10 against the integrated tree. Discharged:
  the mstest-coverage job passed on the integrated tree in run 32593830908.

The analyzer version-skew note is reframed from "live risk for the final PR" to "did not fire on the
final PR; still open". build-analyzers and build-nullable both passed, which the note itself
predicted would happen while the actions/cache fallback entry survives. The underlying defect is
unchanged and still open.

New Completion Assessment section

States the final position without softening it:

#	Requirement	Status
1	Every feature merged or worktree_removed	NOT SATISFIED, by design — #511 descoped
2	Final integration pull request merged, merge_commit_sha recorded	SATISFIED
3	epic-status.md reflects the completed state	SATISFIED by this change
4	Checkpoint passes require_complete=True	NOT SATISFIED, consequent on requirement 1

Requirements 1 and 4 fail together on the single descoped child and represent a deliberate
disposition, not an unfinished step. The section also records that all four child worktrees remain
framework-locked by the live session process, that removal was attempted three times and deferred
each time, and that forcing is prohibited.

Architecture / How It Fits Together

No runtime wiring is involved. epic.md remains the human-authored manifest and narrative source of
truth and is untouched. artifacts/orchestration/epic-orchestrator-state.json remains the durable,
machine-authoritative checkpoint; it is gitignored and is not part of this diff. epic-status.md is
the human-readable projection of that checkpoint, and is the only file this pull request modifies.

Verification

Completed:

• The upstream epic merge this document describes was itself gated by workflow run 32593830908
  against PR fix(quickfiler): suite-determinism foundation epic — remove live test form, repair keyboard-action and explorer-controller contract defects (#445, #449, #491) #595 head e7b4824a: actionlint, build-analyzers, build-nullable, format-check and
  mstest-coverage all pass.
• Every value written into the document was re-derived from gh pr view, gh pr checks,
  gh run view and gh issue view at the time of writing, not copied from in-memory state.
• git diff --stat confirms the change is confined to one Markdown file, +87/-18.

Recommended:

• Read the rendered Markdown tables on GitHub to confirm the new per-check and issue-disposition
  tables render correctly.

No toolchain gate applies to a Markdown-only change: the CSharpier check set excludes .md, and no
analyzer, nullable or MSTest stage reads this path.

Backward Compatibility / Migration Notes

None. No public API, contract, path or configuration changes. The document is a generated projection
with no consumers other than human readers.

Risks and Mitigations

• Risk: the document could drift from the checkpoint it projects. Mitigation: every field
  written here was re-derived from GitHub and git at the time of writing, and the checkpoint was
  updated in the same operation.
• Risk: a reader could mistake the superseded notes for current instructions. Mitigation:
  each is labelled superseded in place with the reason and the outcome that overtook it, rather than
  silently deleted.
• Rollback: revert the single commit. Nothing depends on this file.

Review Guide

One file, one theme. Suggested order: the Completion Assessment section first (it states the
outcome), then the Final Integration Pull Request section (it carries the evidence), then the
superseded notes (they explain what changed relative to the previous generation).

Follow-ups

• Issue Bug: winformspumphost-tests-load-flaky-visible-window #511 remains open. Its remedy was measured to be a no-op; the real cause is tracked as Pump-hosted QfcItemController tests expire at the 60s PumpTimeoutMs under CPU contention (real cause behind #511/#571) #592.
• Issue Bug: qfc-item-controller-init-tests-flaky-window-handle #571 remains open behind Pump-hosted QfcItemController tests expire at the 60s PumpTimeoutMs under CPU contention (real cause behind #511/#571) #592.
• Issues KaStringAsync.KeyEquals branch 1 computes a prefix-only Substring offset under a Contains guard #583, Bug: uithread-dispatcher-null-race-progresstrackerasync #584, Bug: utilitiescs-test-form1-live-form #586, Bug: collect-pr-context-shared-path-race-across-concurrent-children #589, orchestrator-state blocked_reason enum cannot express a premise-falsified halt drm-copilot#523 and Three pre-existing UtilitiesCS.Test flakes block any suite-wide zero-failure gate #594 remain open as follow-ups promoted during the epic.
• Worktree cleanup for the four locked child worktrees is outstanding and can be completed once the
  owning session process exits.

GitHub Auto-close

None. GitHub validation was unavailable in the context bundle and no autoclose issues were verified
or asserted. This pull request intentionally closes nothing: the three issues the epic delivered were
already closed by PR #595, and every remaining issue is genuinely unresolved.