Skip to content

docs: record open-issue triage verdicts (#3-#9) - #17

Closed
systemfsoftware-maker wants to merge 2 commits into
masterfrom
feature/docs-open-issue-triage-verdicts
Closed

docs: record open-issue triage verdicts (#3-#9)#17
systemfsoftware-maker wants to merge 2 commits into
masterfrom
feature/docs-open-issue-triage-verdicts

Conversation

@systemfsoftware-maker

Copy link
Copy Markdown
Collaborator

What

Durable verdict record for the seven open issues (#3-#9, residual findings
from PR #10), plus the revised triage plan. A four-reviewer doc review
falsified the first plan draft's two planned closures, so the record keeps
all seven open with corrected mechanisms.

Verdicts

Issue Verdict Severity
#3 confirmed-defect P2
#4 real-but-corrected P2
#5 confirmed-defect P2
#6 real-but-corrected P3
#7 confirmed-defect P1 (guard inoperative)
#8 confirmed-defect P2
#9 confirmed-defect P2

Key corrections: #4 launcher BinaryNotFound path is live (platform
packages ship the binary); #8 check-matrix fails loudly, not vacuously;
#7's sha sidecar has no producer at HEAD (writer removed e92d150) so the
cross-check guard is non-functional; #9 corrected framing (real exposure on
the only publish path).

Evidence

  • docs/residual-review-findings/185fa9144.md — per-issue verdicts with
    file/line evidence and correction history
  • docs/plans/2026-08-21-001-docs-open-issue-triage-verdict-plan.md
    sources, adjudication, KTDs, DoD, verification contract

Safety

  • No GitHub issue mutation, no close runs
  • All seven issues stay open and unmodified
  • Code reviewed by correctness + project-standards reviewers; all three
    actionable findings validated by an independent validator batch and
    committed as 6916144

Closes nothing. Re-opens nothing.

Four-reviewer doc review falsified the two planned closures:
- #4 non-issue repudiated: launcher BinaryNotFound path is live
  (npm/packages/comment-checker/src/index.ts getBinaryPath);
  platform manifests ship files:[entry.bin]
- #9 stays open: no workflow YAML/expression validation anywhere
- #8 mechanism corrected: check-matrix gate fails loudly (probe:
  flow-style release.yml -> FAIL per target, exit 1), not vacuous

All seven issues remain open; verdict doc records corrected
mechanisms and severities. No GitHub issue mutation runs.
Code review (correctness + project-standards, validator-confirmed) found:
- #7: the .sha256 sidecar the cross-check reads has no producer at HEAD
  (writer removed in e92d150); the guard is inoperative, so #7 keeps filed
  P1 instead of the first-draft P3 correction.
- plan/record: ci.yml npm job gates list four checks, not two; none
  parses workflow YAML.

Verdict record and plan are re-anchored to the current tree; no issue
mutation is performed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants