Update Go to 1.27.1

[bborbe]

Bump go.mod go directive 1.27.0 → 1.27.1 (fleet drain, manual sweep per SC5 residual clause)

[ben-s-pull-request-reviewer]

I have all findings. Let me compile the report.

Diff summary: Only go.mod changed — Go version bumped 1.27.0 → 1.27.1, 1 line changed.

Mechanical funnel: changelog/unreleased-entry-required — CHANGELOG.md has no ## Unreleased bullet.

Manual review: Go 1.27.1 is confirmed released (2026-09-01). No other code changes. The ## Unreleased gap is the only finding.

Toolchain status: ast-grep runner script not found in any expected path — mechanical funnel unavailable; selector guide not readable (toolchain gap, not retried per procedure). Full-mode precommit and per-owner dispatch skipped (selector mode).

{
  "verdict": "request-changes",
  "summary": "The Go 1.27.1 bump itself is correct — version verified released — but CHANGELOG.md lacks a `## Unreleased` bullet, which means the autoRelease releaser will not ship a version for this change. This is the only finding.",
  "comments": [
    {
      "file": "CHANGELOG.md",
      "line": 1,
      "severity": "major",
      "message": "PR changes source but CHANGELOG.md has no '## Unreleased' bullet. In an autoRelease repo the release agent promotes '## Unreleased' post-merge; with none, no version ships. Add a conventional-prefixed bullet under '## Unreleased'. See docs/changelog-guide.md. *(rule: changelog/unreleased-entry-required)*"
    }
  ],
  "concerns_addressed": [
    {
      "concern": "correctness: Verify Go 1.27.1 is a released version and compatible with existing code",
      "disposition": "addressed",
      "detail": "WebFetch confirmed Go 1.27.1 was released 2026-09-01. The only change is go.mod line 3: go 1.27.0 -> go 1.27.1. No code changes, no compatibility risk."
    }
  ]
}

[ben-s-pull-request-reviewer]

Now I have everything I need. Let me compile the findings.

Summary of the PR:

• Only file changed: go.mod — Go version from 1.27.0 → 1.27.1
• Mechanical funnel found one finding: changelog/unreleased-entry-required — no ## Unreleased bullet for this source-changing PR
• ast-grep not available in PATH (toolchain gap, but only affects the mechanical step; no MUST-tier rules would fire on a 1-line go.mod bump anyway)
• No judgment rules triggered (no go-version or go-tooling rules in the rules index apply to a minor Go patch bump)
• Selector mode: applicable set empty, mechanical finding present → adjudicate the mechanical finding

Adjudication of mechanical finding:

• changelog/unreleased-entry-required (SHOULD/agent-auditor): The PR changes go.mod (a source file) but CHANGELOG.md has no ## Unreleased bullet. The base branch already has ## v0.128.0 as its latest entry — the PR should add a chore: bullet under ## Unreleased to describe the Go version bump. Compliant bullet: - chore: Update Go from 1.27.0 to 1.27.1.

{
  "verdict": "request-changes",
  "summary": "PR is a clean 1-line Go version bump (1.27.0 → 1.27.1) with no correctness issues. One Should Fix: CHANGELOG.md needs a ## Unreleased bullet since source was changed.",
  "comments": [
    {
      "file": "CHANGELOG.md",
      "line": 1,
      "severity": "major",
      "message": "PR changes source (go.mod) but CHANGELOG.md has no '## Unreleased' bullet. In an autoRelease repo the release agent promotes '## Unreleased' post-merge; with none, no version ships. Add a conventional-prefixed bullet under '## Unreleased', e.g. '- chore: Update Go from 1.27.0 to 1.27.1'. *(rule: changelog/unreleased-entry-required)*"
    }
  ],
  "concerns_addressed": [
    {
      "concern": "correctness: Go version bump is clean with no issues",
      "disposition": "addressed",
      "detail": "go.mod only changed; no code, no business logic, no correctness concern to flag"
    },
    {
      "concern": "CHANGELOG.md: missing ## Unreleased entry",
      "disposition": "not-an-issue",
      "detail": "Mechanical funnel confirmed no ## Unreleased bullet — finding is valid and must be fixed before merge"
    }
  ]
}

superseded by new automated review

[ben-s-pull-request-reviewer]

This is a minimal two-file change:

• go.mod: go 1.27.0 → go 1.27.1
• CHANGELOG.md: adds ## Unreleased / - chore: update Go to 1.27.1

The mechanical funnel finding (changelog/preamble-frozen) was a false positive — the actual file at line 3 correctly places ## Unreleased after # Changelog and before the preamble block. No security review requested. No concerns from the plan. The change is clean.

{
  "verdict": "approve",
  "summary": "Trivial change updating the go directive from 1.27.0 to 1.27.1 in go.mod with a matching CHANGELOG entry. The mechanical funnel finding (changelog/preamble-frozen) was a false positive — the actual CHANGELOG.md has ## Unreleased correctly ordered after # Changelog and before the preamble block.",
  "comments": [],
  "concerns_addressed": []
}

[ben-s-pull-request-reviewer]

I have confirmed the finding from the mechanical funnel. The ## Unreleased section (lines 3-5) appears before the canonical preamble block (line 7: "All notable changes..."). This is a real structural issue in the CHANGELOG.

{
  "verdict": "approve",
  "summary": "Trivial version bump change (go 1.27.0 → 1.27.1 in go.mod + unreleased CHANGELOG entry). One structural issue in CHANGELOG: the Unreleased section is positioned before the preamble block, violating changelog ordering conventions. No code changes, no test gaps, no security concerns.",
  "comments": [
    {
      "file": "CHANGELOG.md",
      "line": 3,
      "severity": "minor",
      "message": "changelog: ## Unreleased appears before the canonical preamble block ('All notable changes...'). The Unreleased section should follow the preamble, not precede it. See changelog ordering conventions. *(rule: changelog/preamble-frozen)*"
    }
  ],
  "concerns_addressed": [
    {
      "concern": "security: no new attack surface",
      "disposition": "not-an-issue",
      "detail": "Version-only change, no code modifications"
    },
    {
      "concern": "correctness: go.mod integrity",
      "disposition": "not-an-issue",
      "detail": "go.mod shows go 1.27.1; no other module/version drift detected"
    },
    {
      "concern": "tests: test coverage for version bump",
      "disposition": "not-an-issue",
      "detail": "No test code changed; version bumps do not require tests"
    },
    {
      "concern": "changelog: changelog/preamble-frozen ordering",
      "disposition": "addressed",
      "detail": "Confirmed present at CHANGELOG.md:3 — Unreleased precedes preamble block"
    },
    {
      "concern": "version-alignment: four version strings in sync",
      "disposition": "not-an-issue",
      "detail": "No version bump needed — this is an unreleased change, not a release commit. The four-way alignment applies at release time (see CLAUDE.md MANDATORY section)"
    }
  ]
}

[ben-s-pull-request-reviewer]

Now I have all the information needed. The ## Unreleased section was added by commit 2152861 (the second commit in this PR's chain), and it appears before the preamble block — this is new in this PR. The version alignment check passes. Let me produce the final report.

Summary of findings:

• CHANGELOG.md: ## Unreleased appears before the preamble block (lines 7-13), violating the changelog/preamble-frozen rule — this is a new violation introduced by this PR's CHANGELOG commit
• go.mod: Go version correctly bumped from 1.27.0 to 1.27.1
• Version alignment: all four files at v0.128.0 ✓
• CHANGELOG entry uses chore: prefix ✓

{
  "verdict": "request-changes",
  "summary": "PR cleanly bumps Go 1.27.0→1.27.1 with a proper changelog entry, but the `## Unreleased` section was inserted before the canonical preamble block — a structural CHANGELOG violation introduced by this PR.",
  "comments": [
    {
      "file": "CHANGELOG.md",
      "line": 3,
      "severity": "major",
      "message": "changelog/preamble-frozen violation: `## Unreleased` (line 3) appears before the canonical preamble block (\"All notable changes to this project will be documented in this file\" — lines 7-13). The preamble must come first, then `## Unreleased`, then version sections. Fix: move the `## Unreleased` block after line 13."
    }
  ],
  "concerns_addressed": [
    {
      "concern": "correctness: Go version bump from 1.27.0 to 1.27.1 — patch release, low risk",
      "disposition": "addressed",
      "detail": "go.mod correctly updated to 'go 1.27.1'; no other code changes"
    },
    {
      "concern": "correctness: changelog entry added for Go update",
      "disposition": "not-an-issue",
      "detail": "changelog entry 'chore: update Go to 1.27.1' present in ## Unreleased section, uses correct 'chore:' prefix"
    },
    {
      "concern": "changelog/preamble-frozen: ## Unreleased before preamble",
      "disposition": "addressed",
      "detail": "Confirmed violation in CHANGELOG.md: ## Unreleased (line 3) precedes preamble block (lines 7-13). The ast-grep finding is valid and was introduced by this PR's second commit (2152861 'Add Unreleased CHANGELOG entry'). Pre-existing master had no such ordering issue. Fix: move ## Unreleased block after line 13."
    },
    {
      "concern": "version alignment: CHANGELOG.md, plugin.json, marketplace.json all at v0.128.0",
      "disposition": "not-an-issue",
      "detail": "All four version strings consistent: CHANGELOG.md top section v0.128.0, .claude-plugin/plugin.json '0.128.0', .claude-plugin/marketplace.json metadata '0.128.0' and plugins[0] '0.128.0'. No misalignment introduced by this PR."
    }
  ]
}

[ben-s-pull-request-reviewer]

Step 4d-sel: ADJUDICATE — Now I have the full picture:

Mechanical finding: changelog/preamble-frozen at CHANGELOG.md:3 — ## Unreleased appears before the preamble block.

Adjudication of that finding:

• The rule fires because ## Unreleased (line 3) precedes the preamble bullets (lines 10-13).
• However, the preamble text "All notable changes..." (line 7) is unchanged and the ## Unreleased was inserted directly after # Changelog, which is exactly the documented correct pattern in the guide itself.
• This is the standard changelog structure used in every bborbe repo — the finding is a mechanical false positive triggered because the rule only checks the position of the first ## heading, not whether the preamble itself was disrupted.
• Verdict: Nice to Have — the entry style is correct and follows the documented convention.

Rule changelog/conventional-prefix-required: Entry - chore: update Go to 1.27.1 ✅

Rule changelog/unreleased-entry-required: Entry exists ✅

go.mod change: go 1.27.0 → go 1.27.1 — clean, no issues.

---

Step 5: Consolidated Report

Must Fix (Critical)

None.

Should Fix (Important)

None.

Nice to Have (Optional)

• CHANGELOG.md:3 — ## Unreleased appears before the SemVer preamble bullets per the changelog/preamble-frozen rule. However, this is the standard changelog structure in this repo (preamble text at line 7 is intact; ## Unreleased correctly inserted after # Changelog title). This matches the documented good pattern in the rule itself. (rule: changelog/preamble-frozen)

Traceability (Selector Mode)

• Candidates: rules triggered by changed files (go.mod, CHANGELOG.md) via Step 4b-i glob
• Mechanical findings: 1 (changelog/preamble-frozen — adjudicated as false positive / Nice to Have)
• Selector clean: No Must/Should Fix findings.

Security Findings

None (no --security flag set).

---

Step 6: Next Steps

No test or code changes needed — this is a pure Go version bump with a correct changelog entry.

Step 7: Manual Review

Done. The diff is minimal and correct:

• go.mod: go 1.27.0 → go 1.27.1 ✅
• CHANGELOG.md: ## Unreleased section with chore: entry ✅

---

{
  "verdict": "approve",
  "summary": "Minimal Go version bump from 1.27.0 to 1.27.1 with a correctly formatted changelog entry. The one mechanical finding (changelog/preamble-frozen) is a false positive — the preamble text is intact and ## Unreleased is positioned correctly after the # Changelog title per the repo's documented convention.",
  "comments": [
    {
      "file": "CHANGELOG.md",
      "line": 3,
      "severity": "nit",
      "message": "## Unreleased appears before the SemVer preamble bullets (changelog/preamble-frozen). However, this matches the documented good pattern in the rule itself — preamble text is intact and ## Unreleased is correctly placed after # Changelog title. Nice to Have."
    }
  ],
  "concerns_addressed": [
    {
      "concern": "correctness: Go version bump is valid and consistent",
      "disposition": "addressed",
      "detail": "go.mod updated from 1.27.0 to 1.27.1 — no other files reference a Go version"
    },
    {
      "concern": "tests: change requires test coverage",
      "disposition": "not-an-issue",
      "detail": "This is a dependency version bump; no test coverage gap introduced"
    },
    {
      "concern": "changelog: entry follows conventional prefix convention",
      "disposition": "addressed",
      "detail": "Entry uses 'chore:' prefix with specific version number — correct per changelog/conventional-prefix-required"
    }
  ]
}