Skip to content

Tracker: AUDIT.md #1357

Closed
Closed

Description

@ptr727

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.

  1. 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)
  2. 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)
  3. Section 6's configure.sh check <owner>/<repo> release|operational is 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)
  4. 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)

Activity

  1. added
    pre-existingReview finding classed pre-existing per local-strict-review Disposing of Findings
    proseA defect in rule or procedure text
    on Sep 5, 2026
  2. ptr727 commented on Sep 14, 2026

    @ptr727
    OwnerAuthor

    Two new pre-existing findings on this unit, from a carried-content review pass on feature/blocked-upstream-issue-rule, numbering continuing the list in the body.

    1. 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 in STANDUP.md, now sits in the Repo group. Every carrying repository inherits the dangling header.

    2. AUDIT.md:165: "Branch from the target's develop (or main for a main-only repo)" names a repository shape this same file's section 4 declares nonconformant. The branch-model dimension asserts that "main and develop both exist and are protected", and spec/project-types.json declares crossCutting.branch-model with appliesTo: "*" and check branch.both-protected. GOVERNANCE.md "Branching Model" scopes the exception to main-only content, not to a main-only repo. Followed literally on a repository where develop is missing or merely unfetched, a converging agent branches its fix onto the promotion branch instead of reporting the missing develop as 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.md rather than in this file: AUDIT.md:133 sends a report author to that template, whose Dimensions table omits five dimensions section 4 names and carries one nothing declares.

  3. ptr727 commented on Oct 23, 2026

    @ptr727
    OwnerAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    pre-existingReview finding classed pre-existing per local-strict-review Disposing of FindingsproseA defect in rule or procedure text

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions