Skip to content

Port the tools/ and release scripts #332

Open
1 of 7 issues completed
Open

Description

@tbhb-agent

Outcome

The logic in this repository's tools/ and release shell scripts is replaced by Go commands, per #588, which sends all of this tooling to Go and to no other language. The scripts covered are tools/skill-tokens.sh, tools/generate-skills.sh, tools/skill-limits.sh, tools/check-script-hygiene.sh, tools/release-readiness.sh, tools/release-verify.sh and tools/mise-bootstrap. tools/check-versions.sh is already a forwarder to agentrepo check-versions and tools/release-dispatch.sh only sequences cog, gh and a readiness gate, so both stay thin shell. Command names follow the #174 decisions. This issue closes when its children close.

Done when

Children

Each is a native sub-issue of #332, verified on 2026-10-31. Labels are change:feat plus the refinement label shown.

Status: six children are open (#807, #808, #809, #811, #812, #813) and one is closed (#810). #807 is open and carries refinement:ready.

Relation to #588: #332 is a direct sub-issue of #588. None of #807 through #813 is a direct sub-issue of #588 (its 47 direct sub-issues do not include them), so all seven are grandchildren of #588 through #332.

Out of scope

Owner

The repository maintainers.

Activity

  1. added
    change:featPR adds or changes a feature (Conventional Commit type feat)
    on Oct 20, 2026
  2. removed
    change:featPR adds or changes a feature (Conventional Commit type feat)
    on Oct 22, 2026
  3. tbhb-agent commented on Oct 31, 2026

    @tbhb-agent
    ContributorAuthor

    Refinement: NOT READY — Add evidence-based epic closure to the plan

    Checked: #332 and its comments, #588, and children #807–#813 individually. The listed child states, sizes, and refinement labels match the issues. The children cover the prior port table: each ported script has a child, and tools/check-versions.sh and tools/release-dispatch.sh are identified as thin shell. The scope aligns with #588’s Go-only direction.

    Gaps

    1. Major — Port the tools/ and release scripts #332’s Done when does not require a closing comment that checks the epic’s Done when against evidence. Child plans’ final status comments do not cover that requirement. Add it to the epic’s Done when.
    2. Minor — The plans refer generally to repository leak scans, but do not name the required checks: gitleaks, check-leaks.sh with the private-strings list, and leak review of each post. Spell these out so D4’s planning coverage is checkable.

    Split: No uncovered script or overlap found. The proposed scope is broad for several S-sized children, especially #807–#809 and #811; reconsider those estimates against their cross-platform and compatibility verification plans.

    Definition of done

    • D4 The leak scans come back clean: gitleaks, devtools' check-leaks.sh with the repository's private-strings list, and the leak review of each post.
    • epic-1 Each child issue has closed, or closed as not planned with a reason.
    • epic-2 A closing comment checks its "Done when" with evidence.

    Round: 1 of 3

  4. changed the issue type fromtoon Oct 31, 2026
  5. tbhb-agent commented on Oct 31, 2026

    @tbhb-agent
    ContributorAuthor

    Refinement: READY — Epic closure and leak checks are covered

    Checked: #332 and its round-1 comment, #588, and children #807–#813 individually. The outcome follows #588’s Go-only direction. The current body adds the closing-comment evidence check and names all required leak checks.

    Gaps: None

    Split: No overlap or uncovered script found. The children cover every script in the earlier port table: #807–#813 own the seven Go ports; tools/check-versions.sh and tools/release-dispatch.sh are explicitly kept thin. Child states and sizes match the body: #810 is closed and M; the others are open, with #807–#809 and #811 S, and #812–#813 M. No remaining over-engineering defect found.

    Definition of done

    • D4 The leak scans come back clean: gitleaks, devtools' check-leaks.sh with the repository's private-strings list, and the leak review of each post.
    • epic-1 Each child issue has closed, or closed as not planned with a reason.
    • epic-2 A closing comment checks its "Done when" with evidence.

    Round: 2 of 3

  6. added
    refinement:readyPassed the Definition of Ready; may be picked up
    and removed
    refinement:activeA refinement round is open; not ready for implementation
    on Oct 31, 2026
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

    refinement:readyPassed the Definition of Ready; may be picked up

    Type

    Fields

    Work type

    Planned

    Priority

    Intangible

    Projects

    • Status
      Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions