Bug: raw-evidence-paths-tracked-on-main-unowned #884
Copy link
Copy link
Closed as not planned
Labels
bugSomething isn't workingSomething isn't working
Description
Activity
The following sections were present and filled in the promoted potential-bug entry (
docs/features/potential/promoted/2026-09-13-raw-evidence-paths-tracked-on-main-unowned.md) but were dropped bypotential_to_issuewhen this issue was created. Reposting them here per the known promotion-fidelity defect tracked in issue #887.Suspected Cause / Notes
The
## Committed Test Evidence Formatpolicy in CLAUDE.md is recent; the raw evidence predates it and was never sweep-cleaned because the one item scoped to do the sweep (602,host-identifier-leakage-sweep) was withdrawn frombugs-2026-09-11before it ran. No replacement item currently owns this scope. This is a documentation/process gap (no owner), not a code defect in any single feature's evidence.Proposed Fix / Validation Ideas
- Unit coverage areas: not applicable (documentation/evidence hygiene, not source code)
- Integration scenario to retest: a repository-wide sweep that (a) converts remaining raw
.trx/.cobertura.xmlevidence to the permitted JaCoCo/summary projections where the underlying figures are still needed, or (b) deletes the raw documents where the feature is already archived and the figures are preserved elsewhere, then verifiesgit ls-files -- 'docs/features/**/*.trx' 'docs/features/**/*.cobertura.xml'returns zero. - Manual verification notes: re-run the same
git ls-filesqueries after the sweep and confirm a zero count; also confirm no new raw evidence is introduced going forward (this should already be caught by the existing feature-review policy-audit process for new work).
Next Step
- Promote to GitHub issue (bug-report template)
- Move to active fix folder / branch
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
Summary
maincarries a large number of tracked raw evidence paths - raw coverage-collector documents (*.cobertura.xmland similar) and raw test-platform documents (*.trx) committed under feature folders'evidence/trees. CLAUDE.md now carries a## Committed Test Evidence Formatsection (line 412) that prohibits committing either document type in any form, including under a feature folder's evidence tree, because both carry absolute host paths and machine-specific identifiers. The repository does not conform to its own policy, and the sweep that was meant to remediate it has no current owner.Environment
git ls-files -- 'docs/features/**/*.trx',git ls-files -- 'docs/features/**/*.coverage' 'docs/features/**/*cobertura*.xml', run againstmain(HEADe6d86049e)docs/features/active/**/evidence/**onmainSteps to Reproduce
main(or any worktree at the same HEAD, e.g.e6d86049e).git ls-files -- 'docs/features/**/*.trx'. This independently returned 333 tracked.trxpaths under feature evidence trees (verified 2026-09-13).git ls-files -- 'docs/features/**/*.coverage' 'docs/features/**/*cobertura*.xml'. This independently returned a large additional set of tracked raw Cobertura documents under feature evidence trees (e.g.docs/features/active/2026-08-07-efcviewer-missing-lineage-and-segment-navigation-439/evidence/baseline/issue-439-baseline.cobertura.xml).## Committed Test Evidence Format: "A raw coverage collector document and a raw test-platform document are both prohibited. Neither may be added to git in any form, including under a feature folder's evidence tree."main, a set difference of zero, meaning no in-flight item added any of them - all 572 predate the policy.Expected Behavior
mainshould carry zero raw coverage-collector documents and zero raw test-platform documents under any feature folder's evidence tree. Only the two permitted projections (a package-level JaCoCo projection of the post-processed Cobertura document, and the one-line first-party coverage summary) and the trx-derived test-result summary should be committed.Actual Behavior
maincarries hundreds of raw.trxfiles and raw.cobertura.xmlfiles underdocs/features/active/**/evidence/**, predating the CLAUDE.md policy that now prohibits them. This was the job of issue 602 (Repository-wide host-identifier leakage: absolute user-profile paths, account and host names in tracked files- the same class of defect, since these evidence documents also carry absolute host paths and machine-specific identifiers). Item 602 was withdrawn from the parallel runbugs-2026-09-11before execution (confirmed 2026-09-13 indocs/features/parallel/bugs-2026-09-11/parallel-status.mdon theparallel/bugs-2026-09-11-planbranch: row| 602 | docs/features/active/2026-09-12-host-identifier-leakage-sweep-602 | - | C3 | opus | withdrawn | not_started | - | - |). No other item in that run or elsewhere has since picked up the sweep, so it currently has no owner.Logs / Screenshots
git ls-files -- 'docs/features/**/*.trx'againstchor/defect-filings-2026-09-13(HEADe6d86049e, same asmain) returned 333 lines, first entrydocs/features/active/2026-08-24-breadcrumb-coordinator-hub-defects-501/evidence/baseline/trx/p0-t17/p0-t17.trx. A second query for*.coverage/*cobertura*.xmlreturned dozens more raw Cobertura documents across multiple feature folders (efcviewer-missing-lineage-...-439,breadcrumb-coordinator-hub-defects-501,breadcrumb-router-navigation-defects-498,qfc-collection-controller-defects-468,quickfiler-bug-family-446,webview2-host-initializer-defects-476, and others).Impact / Severity
High because the repository is provably out of compliance with its own committed-evidence policy at scale (hundreds of files), the tracked files carry absolute host paths and machine-specific identifiers as the policy itself notes, and there is currently no owner driving remediation after item 602's withdrawal.
Source
From: docs/features/potential/2026-09-13-raw-evidence-paths-tracked-on-main-unowned.md