[promote persona-mention 2/3] Wire into ring-pins + deploy + bootstrap #784

Activity

1. don-petry

   added

   enhancementFeature requestsFeature requests

   on Jul 19, 2026
2. don-petry commented on Oct 11, 2026

   

   don-petry

   on Oct 11, 2026

   Last edited by don-petry

   ContributorAuthor

   More actions

   Bootstrap criterion reworded, 2026-10-11 (Don's decision).

   I ran DRY_RUN=true bash scripts/bootstrap-new-repo.sh petry-projects/incubator from an export of main at b1387cbd. It runs six steps: ring record, repo settings, rulesets, labels, CODEOWNERS check, .gitignore baseline. It seeds no workflow stub for any agent, so adding one for persona-mention would be a new mechanism, not a missing line.

   New repositories get the stub from petry-projects/repo-template (is_template: true), which carries .github/workflows/persona-mention.yml pinned @persona-mention/v1-stable, and from the weekly standards sweep. The issue body and the epic now say that.

   State of the three edits this story asked for, on main:

   Edit	Where
   persona-mention in the ring-pin reusables	scripts/lib/ring-pins.sh:46
   persona-mention.yml in the deployed set	scripts/deploy-standard-workflows.sh:129
   persona-mention agent and rings	standards/canary-rings.json:1032

   incubator carries the stub at @persona-mention/v1-stable (blob ee2f94c4), which is stronger than the dry-run the criterion asked for.

   Two things still open, neither part of this story:

   • repo-template, incubator, broodly, broodminder-data and empower-personal-dashboard are on the earlier 66-line stub, which has no pull_request trigger. The sweep on 2026-10-12 08:16 UTC is expected to open the sync PRs.
   • The dry-run exposed a path bug in bootstrap's settings step: bootstrap-new-repo.sh passes owner/repo to apply-repo-settings.sh #1308.

   I did not re-run the test suites for the three edits; the table above is a read of main.
3. don-petry

   closed this as completedon Oct 11, 2026