docs(potential): file the 2026-09-11 consolidated bug-run intake and record the close of parallel run bugs-2026-09-02

[drmoisan]

Suggested title

docs(potential): file the 2026-09-11 consolidated bug-run intake and record the close of parallel run bugs-2026-09-02

Summary

• Adds eight potential entries under docs/features/potential/ that form the intake for the consolidated bug parallel run planned on 2026-09-11.
• Five are bug entries, each consolidating open bug issues that share one root cause or one sweep: the minor-audit trio (Bug: gate-scan-bound-log-line-content-unasserted #794, Bug: undisposed-cancellation-token-sources #840, Bug: progresstrackerasync-is-dormant-production-code #841), the test-evidence projection convention and identity-leak tooling (Bug: trx-evidence-host-tokens-and-malformed-xml #671, Bug: committed-host-identity-leaks #728, tooling half of Repository-wide host-identifier leakage: absolute user-profile paths, account and host names in tracked files #602), the CLAUDE.md coverage-threshold and toolchain-command corrections (Bug: claude-md-cut3-names-uninvoked-coverage-command #828, 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, Bug: quickfiler-coverage-filesize-evidence-debt #727 sub-finding 5), the CI coverage-threshold and Pester gates (CI collects coverage but enforces no threshold: _mstest-coverage.yml never converts to Cobertura or compares a floor #561, No Pester job in CI: production PowerShell under scripts/vscode has zero CI coverage #562), and the QfcQueue enqueue-path seams (Bug: quickfiler-coverage-filesize-evidence-debt #727 sub-finding 4).
• Three are deferral entries for the Bug: quickfiler-coverage-filesize-evidence-debt #727 refactor sub-findings that are excluded from the bug run: QfcFormController.EventHandlers coverage uplift, StoreWrapperController absent from the coverage report, and the four remaining files over the 500-line ceiling.
• Regenerates docs/features/parallel/bugs-2026-09-02/parallel-status.md to record the close of that open-mode run.
• Documentation only. No code, test, workflow, or configuration file changes.

Why

The repository carries 20 open issues labeled bug. A review of all of them on 2026-09-11 found that several share a root cause or a single sweep, that three are fixable only upstream in drm-copilot, and that #727 bundles six unrelated sub-findings. Running them as 20 separate items would multiply preparation, review, and PR overhead. The consolidated entries let the parallel planner promote one issue per delivery, with the originating issues closed by that delivery's PR.

Each consolidated bug entry records the maintainer decision it depends on, taken on 2026-09-11 and posted as comments on #563, #583, #671, and #727: line floor 80% and branch floor 75% for C#, 80% line for PowerShell, thresholds recorded in CLAUDE.md alone, the three existing coverage-exemption classes kept as written, seams rather than exemptions for COM-bound async members, and projection-only committed test evidence with raw output discarded.

The bugs-2026-09-02 run was in open mode with all 15 items merged. Open mode never auto-completes, so it was closed explicitly before a new run is planned; the regenerated status projection records that close.

What Changed

Consolidated bug entries (5)

• 2026-09-11-minor-audit-trio-gate-log-assertion-cts-disposal-dormant-tracker.md (+69)
• 2026-09-11-test-evidence-projection-convention-and-identity-leak-tooling.md (+73)
• 2026-09-11-claude-md-coverage-thresholds-and-toolchain-command-corrections.md (+65)
• 2026-09-11-ci-coverage-threshold-and-pester-gates.md (+71)
• 2026-09-11-qfcqueue-enqueue-path-lacks-injectable-seams.md (+66)

Deferral feature entries (3)

• 2026-09-11-qfcformcontroller-eventhandlers-coverage-uplift.md (+37)
• 2026-09-11-storewrappercontroller-absent-from-coverage-report.md (+36)
• 2026-09-11-quickfiler-utilitiescs-file-size-ceiling-splits.md (+47)

Parallel run record (1)

• docs/features/parallel/bugs-2026-09-02/parallel-status.md (+18/-3): run close recorded, one run-scoped close mutation, recolor_generation unchanged at 1. Thirteen items keep merge_status: merged rather than worktree_removed because their worktrees were reclaimed by an out-of-band cleanup, not by the run's gated removal step; the difference is terminal for every validator predicate.

Architecture / How It Fits Together

Potential entries are the intake format the parallel-plan skill accepts alongside issue numbers. During preparation, a child orchestrator promotes each entry to a GitHub issue through the drm-copilot promotion lifecycle and creates its active feature folder; the entry's Closes line tells the delivery's PR which originating issues to close. The deferral entries stay in docs/features/potential/ until a later run picks them up. The parallel-status document is a generated projection of the run checkpoint and is never hand-authored.

Verification

Completed

• Every fact cited in the entries was checked against main on 2026-09-11: coverage figures from PR fix(coverage): expose a de-duplicated first-party Cobertura aggregation (#815) #829 (C# line 84.56%, branch 79.24%), PowerShell line coverage 78.3% from the Bug: coverage-assembly-discovery-excludes-own-worktree-root #752 baseline, tracked evidence counts (332 .trx, 248 .cobertura.xml), file line counts, and the presence of each cited source construct.
• The run close was validated with the orchestration-artifacts validator under the completion predicate for open mode.

Recommended

• None beyond the standard CI checks. actionlint and format-check do not process Markdown; the C# build and test jobs run against an unchanged tree.

Backward Compatibility / Migration Notes

None. No production, test, or configuration file is touched.

Risks and Mitigations

• An entry's scope could be wider than a single delivery. Each consolidated entry lists its files and the reason its members belong together; the parallel planner's blast-radius computation will surface contention if a grouping is wrong, and the planner can split an item before execution.
• The Pester gate entry depends on raising PowerShell coverage from 78.3% to 80%. The entry states that the item halts and reports rather than lowering the floor if 80% is not reachable.

Review Guide

1. The five consolidated bug entries: check that each grouping shares a root cause or a sweep, and that each Closes line names only issues the delivery will fully resolve.
2. The three deferral entries: confirm they are scoped as refactor work and scheduled after the bug run.
3. parallel-status.md: the appended close mutation and the note on the thirteen merged items.

Follow-ups

• Plan and execute the consolidated bug parallel run over these entries plus issues Bug: breadcrumb-webview2-init-fails-resource-not-in-correct-state #792, Bug: quickfiler-itemviewer-ui-marshalling-seam #743, Bug: gettableinviewasync-returns-null-on-timeout #838, Bug: createcancellationtoken-has-no-production-caller #839, Bug: quickfiler-date-time-format-missing-invariant-culture #742, KaStringAsync.KeyEquals branch 1 computes a prefix-only Substring offset under a Contains guard #583, Bug: uithread-iscompleted-branch2-residual-and-ac5-apartment-measurement #816, and Repository-wide host-identifier leakage: absolute user-profile paths, account and host names in tracked files #602.
• Upstream prompt artifact for Bug: parallel-run-merge-gate-misparses-pr-number #691 and the enforcement half of 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 (drm-copilot owned files); the artifact for Bug: parallel-run-merge-gate-misparses-pr-number #691 exists locally and is committed separately.
• Deferral entries to be promoted after the run merges.

GitHub Auto-close

• None. This PR files intake entries and closes no issue.

🤖 Generated with Claude Code