Repository navigation
2.0.0-rc.13: poteto-help says one installer run covers every home, and names Codex skills $t3-pstack:<name> - #33
Merged
Conversation
Two lines in poteto-help came from replacements in tools/substitutions.json, not from Lauren, and both were wrong. Setup step 1 said to install t3-pstack "once per harness that T3 runs". One `npx -y github:chhoumann/t3-pstack install` run installs it in every Claude Code and Codex config home T3 can run, as the README's "Install, update, and check" says, so step 1 now says that. The skill-name line gave Codex's form as `$poteto-mode`. Codex names a plugin's skills with the plugin prefix: after a throwaway-HOME install from this checkout, the Codex 0.163.0 app-server's skills/list returns t3-pstack:poteto-mode, t3-pstack:poteto-help, and t3-pstack:setup-pstack. The line now reads `$t3-pstack:poteto-mode`, as the README does. Both replacements changed in substitutions.json and in the derived copy of poteto-help alike. bun tools/sync.mjs at 6b78e9f still counts poteto-help unchanged, and each component's dry run matches main's. No other skill, playbook, hook, README line, or rule writes a bare `$<skill>` or a per-harness install.
VERSION, the manifests, and package.json move to 2.0.0-rc.13. CHANGES.md gets the entry with its behavior-delta table, and the README's pinned installer command names the new tag. The pins stay at 6b78e9f, so NOTICE.md, NOTICE-skills.md, and poteto-mode's copy of the notice do not change. The skill count stays 63.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two lines in
poteto-helpwere wrong. Both came from our own replacements intools/substitutions.json, not from Lauren. This PR fixes both rules and the derived copy together, then releases 2.0.0-rc.13. The pins stay at6b78e9f.Setup step 1 (line 38,
tools/substitutions.jsonline 29)The README's "Install, update, and check" says one
npx -y github:chhoumann/t3-pstack installrun installs into every Claude Code and Codex config home T3 can run. The step said to install once per harness.Before:
After:
Codex skill name (line 58,
tools/substitutions.jsonline 65)Before:
After:
Live Codex evidence
I installed this branch's checkout into a throwaway
HOMEwithtools/install.mjs install --source <checkout>, withCLAUDE_CONFIG_DIR,CODEX_HOME,T3CODE_HOME, andXDG_CONFIG_HOMEunset. Then I asked that home's Codex app-server forskills/list, through the installer's ownAppServerclient:Every t3-pstack skill is listed as
t3-pstack:<name>. The only names without a prefix are Codex's own built-ins. That matches the README's$t3-pstack:<name>on Codex.Other occurrences
I grepped the skills, playbooks, agents, hooks, README, CONTRIBUTING, CONTEXT, and substitutions for a
$<skill>invocation over all 63 skill names, and for "once per", "per harness", "each harness", and every install wording. Only the two lines above, and their two rules, were wrong. The other install lines, such as poteto-help'sinstalls in Claude Code and Codex with npxparagraph and the README and CONTEXT descriptions, already say one run covers every home.How the derived file was regenerated
The port's copy of poteto-help took each new replacement through an exact one-match string swap, the same swap as in the rule.
bun tools/sync.mjs <component> 6b78e9f --dry-runthen still counts poteto-help as unchanged (119 unchanged, 15 declared forks), and each of the three components' output is identical to main's. As a control, putting the old$poteto-modeback in the derived file alone makes the pstack dry run fail, with poteto-help flagged as an undeclared fork.--bootstrapwas not used.Checks
GIT_CONFIG_GLOBAL=/dev/null bun test tests/ --timeout 30000: 550 pass, 46 skip, 0 failbun run typecheck,bun test orch watch-pr check-plan.test.ts, Prettier on the four files): green, 119 passbun tools/generate.mjs --check: 17 generated files current, all checks passbun tools/sync.mjs {pstack,cursor-team-kit,thermos} 6b78e9f --dry-run: exit 0, no undeclared fork, no denylist hit, no rule that matches nothingt3-sheet.mjson this machine's sheet and catalog: every role line parses and dispatchesNeither hooks file changes.
Note
Low Risk
Documentation and substitution-rule text only; no installer, hook, or workflow logic changes.
Overview
Releases 2.0.0-rc.13 with doc-only fixes in poteto-help (and matching
tools/substitutions.jsonrules) so setup guidance matches how the installer actually works.Get set up step 1 no longer says install once per harness; it states that a single
npx -y github:chhoumann/t3-pstack installupdates every Claude Code and Codex config home T3 uses. The harness skill-name note now shows Codex invocations as$t3-pstack:poteto-modeinstead of bare$poteto-mode, aligned with Codex’s plugin-prefixed skill IDs. Version strings and the README tag example are bumped to rc.13; upstream pins stay at Lauren’s6b78e9f.Reviewed by Cursor Bugbot for commit f324c59. Bugbot is set up for automated code reviews on this repo. Configure here.