Repository navigation
Closed
Labels
pre-existingReview finding classed pre-existing per local-strict-review Disposing of FindingsReview finding classed pre-existing per local-strict-review Disposing of FindingsproseA defect in rule or procedure textA defect in rule or procedure text
Description
Tracker for AUDIT.md. Filed under #1315's roll-up of the open prose backlog: every finding a bundle issue enumerated against this unit is listed here once, one line each, naming the issue it came from, and the bundle is closed as a duplicate of this tracker so the finding is not lost and the bundle stops being a unit of work. A new pre-existing finding on this unit gathers here per pr-review-conduct's Merge Gate, numbering continuing this list. This tracker closes when the unit is rewritten and each line below is settled or superseded.
- A multi-line Bash example in section 6 opens without set -Eeuo pipefail, so a failed gh api inside it continues and an incomplete audit reads as clean. (19 Carried-Content Defects From Downstream PR Reviews (guard, resync, drive-pr, git-commit, pr-review, promotion recipe, AUDIT.md, GOVERNANCE.md, merge-bot stub) #1113)
- Two prose-gate misses in carried text: British 'afterwards' in section 2 against the US-English convention, and the coined compound 'all-drifts' in section 6. (19 Carried-Content Defects From Downstream PR Reviews (guard, resync, drive-pr, git-commit, pr-review, promotion recipe, AUDIT.md, GOVERNANCE.md, merge-bot stub) #1113)
- Section 6's
configure.sh check <owner>/<repo> release|operationalis a shell pipeline when pasted, not a placeholder; the same shape recurs in two skills. (Three Findings Against Carried AUDIT.md and GOVERNANCE.md, Raised on a Downstream Promotion #1197) - Section 6's Dependabot runner check looks only for cancelled runs with zero steps and misses a job that sits queued indefinitely on the same misconfiguration. (Three Findings Against Carried AUDIT.md and GOVERNANCE.md, Raised on a Downstream Promotion #1197)
Metadata
Metadata
Assignees
Labels
pre-existingReview finding classed pre-existing per local-strict-review Disposing of FindingsReview finding classed pre-existing per local-strict-review Disposing of FindingsproseA defect in rule or procedure textA defect in rule or procedure text
Activity
ptr727 commentedon Sep 14, 2026
Two new
pre-existingfindings on this unit, from a carried-content review pass onfeature/blocked-upstream-issue-rule, numbering continuing the list in the body.AUDIT.md:175: the<!-- Workflow -->link-group header has no definitions under it. The next non-blank line is<!-- Repo -->at :177.[workflows]at :205, the entry the header exists for and the one it still holds inSTANDUP.md, now sits in theRepogroup. Every carrying repository inherits the dangling header.AUDIT.md:165: "Branch from the target'sdevelop(ormainfor amain-only repo)" names a repository shape this same file's section 4 declares nonconformant. The branch-model dimension asserts that "mainanddevelopboth exist and are protected", andspec/project-types.jsondeclarescrossCutting.branch-modelwithappliesTo: "*"and checkbranch.both-protected.GOVERNANCE.md"Branching Model" scopes the exception tomain-only content, not to amain-only repo. Followed literally on a repository wheredevelopis missing or merely unfetched, a converging agent branches its fix onto the promotion branch instead of reporting the missingdevelopas the branch-model finding it is.A third finding from the same pass is filed separately as #1593, since its fix belongs in
reports/_template.mdrather than in this file:AUDIT.md:133sends a report author to that template, whoseDimensionstable omits five dimensions section 4 names and carries one nothing declares.Record a Hub Blocker Where the Work Waits, and Stop Pre-Authorizing t…
Promote develop to main: Record a Hub Blocker Where the Work Waits (#…
ptr727 commentedon Oct 23, 2026
Closed under the maintainer's decision (ptr727, 2026-10-23) on #3391: the backlog keeps real bugs with a stated failure, features the maintainer wants, and open decisions. A finding the review loop filed on code or text a change did not touch, a refactor or consolidation chore, a tracker, a wording item, or a guard shape no session has produced is closed rather than worked. Reopen with the input and the wrong result if this issue states one.