backlog(B-0122): peer-call scripts TypeScript migration — post-install cutover (2026-04-30) by AceHack · Pull Request #966 · Lucent-Financial-Group/Zeta

AceHack · 2026-04-30T22:58:18Z

Summary

Files the maintainer's 2026-04-30 input ("why are these not ts, are we done with the cutover? these are post install scripts") as durable substrate per input → substrate-file rule
Establishes peer-call scripts as post-install (require target CLI on PATH) → TypeScript per the install-script language strategy
Composes with B-0119 (interim role-ref hygiene), B-0120 (architecture refactor — likely landing surface), B-0121 (Otto/Kenji additions)
Recommends sequencing option (b) — refactor + migrate together, one diff

Verbatim from the maintainer

"tools/peer-call/amara.sh she gets a named script? also why are these not ts, are we done with the cutover? these are post install scripts."

Two observations bundled:

Named-script question — composed-with B-0120 (already filed). The named scripts are v1 stopgaps from yesterday's silent-courier-debt closure; B-0120 collapses to script-per-CLI + persona-flag.
TS cutover question — substrate this row captures. Per memory/project_install_script_language_strategy_post_install_typescript_pre_install_bash_powershell_python_for_ai_ml_2026_04_27.md, peer-call scripts SHOULD be TypeScript. They aren't because v1 shipped fast in bash.

Why P2

Existing bash works; CI green; strategy is opportunistic. Promotion triggers documented in the row.

Test plan

markdownlint passes on B-0122 row + regenerated BACKLOG.md
BACKLOG_WRITE_FORCE=1 bun tools/backlog/generate-index.ts adds B-0122
Composes_with paths valid
Sequencing options (a/b/c) named with pro/con; (b) recommended

🤖 Generated with Claude Code

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fd3c6012d7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Copilot

Pull request overview

Adds a new backlog row (B-0122) capturing the push to treat tools/peer-call/* as post-install scripts and complete the TypeScript/Bun cutover, and wires it into the top-level backlog index.

Changes:

Adds docs/backlog/P2/B-0122-peer-call-typescript-migration-cutover-2026-04-30.md describing the migration/cutover plan and acceptance criteria.
Updates docs/BACKLOG.md to include the new B-0122 row.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
docs/backlog/P2/B-0122-peer-call-typescript-migration-cutover-2026-04-30.md	New backlog row documenting the peer-call TS/Bun cutover rationale, sequencing, and acceptance criteria.
docs/BACKLOG.md	Adds B-0122 to the P2 backlog list.

…B-0121/B-0122 Three small hygiene moves around the peer-call surface: 1. tools/peer-call/README.md gains a "Future direction (queued backlog work)" section pointing at B-0120 (architecture refactor) + B-0121 (Otto/Kenji additions) + B-0122 (TypeScript migration). Future readers + agents see the trajectory without grep-spelunking. 2. B-0119 status open → closed, closed_in: PR #965. The role-ref cleanup landed on main as aab3adb; the row needs to reflect that. 3. B-0120 composes_with gains B-0121 + B-0122 cross-refs. The three rows form a triangle: B-0120 names the architecture, B-0121 adds new peer surfaces in that architecture, B-0122 names the language target. Cross- refs make the relationship discoverable. Note on BACKLOG.md state: this branch's regenerated index shows B-0119 closed and B-0120 unchanged but does NOT yet include B-0121 or B-0122 (their PRs #964 and #966 haven't merged yet). The next regen post-merge picks them up. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…pivot (#1045) Self-applied cooling-period discipline: 5 substrate-class landings this session window — loose pole firing fast; pivot to clearing-work (rebase DIRTY PRs) rather than new substrate. Rebased PR #1040 (B-0130) and PR #1015 (B-0128) against latest main (BACKLOG.md regen + force-with-lease push). #995 and #966 left alone per Aaron's leave-alone framing for older sessions. Class-level lesson: the lattice grades CADENCE too, not just per-landing CONTENT. Even high-quality landings can pile if the generation cadence outruns the maintainer's metabolization capacity. Aaron is asleep; next consumer is morning-Aaron with rested attention; slowing the cadence now respects that consumer. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…ef + B-0122 forward-references Two classes of fix (6 threads — Codex P2 + Copilot P1 each ×3): 1. **Persona names in current-state doc (P1, line 247+253 of README)**: `.github/copilot-instructions.md:306-362` requires role-refs (not persona names) on current-state surfaces (code/docs/skills outside the closed-list history surfaces). Reworded: - "Add Otto + Kenji as externally-callable peers" → "Add the Anthropic-side Claude-code-instance personas as externally-callable peers" - "Otto + Kenji additions (B-0121)" → "The Anthropic-side (Claude-code-instance) peer additions (B-0121)" B-0121 filename slug stays as `otto-kenji-*` (closed-list history surface — backlog rows allow persona names per the carve-out). 2. **B-0122 forward-references (P1+P2, 4 threads)**: B-0122 is filed in the in-flight PR #966; not yet on main. References in `B-0119`, `B-0120`, and the README's table cell rewritten: - YAML `composes_with` lists in B-0119 + B-0120: replaced direct path with inline `# B-0122 ... is filed in the in-flight PR #966` comment. - README table row for B-0122: replaced live link with explicit "filed in in-flight PR #966; link will resolve once that PR lands" callout. B-0121 stays as direct ref because it IS on main. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…l cutover (the maintainer 2026-04-30) Lands the maintainer's 2026-04-30 input as durable substrate per input → substrate-file rule. Verbatim: > "tools/peer-call/amara.sh she gets a named script? also why > are these not ts, are we done with the cutover? these are > post install scripts." Per the install-script language strategy memory (memory/project_install_script_language_strategy_post_install_typescript_pre_install_bash_powershell_python_for_ai_ml_2026_04_27.md): - Pre-install: bash + PowerShell forever (where users are, nothing assumed) - Post-install: TypeScript on bun (declarative state, type- safety, cross-platform uniformity) Peer-call scripts qualify as post-install — they require the target CLI (codex / cursor-agent / gemini) to already be on PATH. Per the strategy, they should already be TypeScript. The cutover is opportunistic (no forced sweep), and v1 shipped in bash for landing speed during the silent-courier- debt closure round (PRs #959 → #962). Composes with three sibling rows: - B-0119 (P3, role-ref cleanup) — interim hygiene; TS rewrite produces clean role-refs naturally - B-0120 (P2, script-per-CLI + persona-flag refactor) — the architectural shape the migration should produce - B-0121 (P2, Otto/Kenji peer-call) — adds new peer-call surfaces; should land in TS if migration is in progress Recommended sequencing: option (b) — refactor + migrate together, one diff produces post-cutover post-refactor TypeScript scripts. B-0120 then becomes "land via B-0122." P2 (not P1) because: - Existing bash works correctly today - Strategy is opportunistic - Promotion triggers exist (bash-compat issues, new peer-call features blocked by bash limits, B-0121 adds a third named-entity script) Per growing-backlog-is-autonomous-health-signal: the maintainer's input becomes durable here even though the migration may not happen this week or month. The question + framing live durably. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…B-0121/B-0122 (#967) * docs(peer-call): future-direction section + close B-0119 + cross-ref B-0121/B-0122 Three small hygiene moves around the peer-call surface: 1. tools/peer-call/README.md gains a "Future direction (queued backlog work)" section pointing at B-0120 (architecture refactor) + B-0121 (Otto/Kenji additions) + B-0122 (TypeScript migration). Future readers + agents see the trajectory without grep-spelunking. 2. B-0119 status open → closed, closed_in: PR #965. The role-ref cleanup landed on main as aab3adb; the row needs to reflect that. 3. B-0120 composes_with gains B-0121 + B-0122 cross-refs. The three rows form a triangle: B-0120 names the architecture, B-0121 adds new peer surfaces in that architecture, B-0122 names the language target. Cross- refs make the relationship discoverable. Note on BACKLOG.md state: this branch's regenerated index shows B-0119 closed and B-0120 unchanged but does NOT yet include B-0121 or B-0122 (their PRs #964 and #966 haven't merged yet). The next regen post-merge picks them up. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(peer-call): address PR #967 review threads — persona-name role-ref + B-0122 forward-references Two classes of fix (6 threads — Codex P2 + Copilot P1 each ×3): 1. **Persona names in current-state doc (P1, line 247+253 of README)**: `.github/copilot-instructions.md:306-362` requires role-refs (not persona names) on current-state surfaces (code/docs/skills outside the closed-list history surfaces). Reworded: - "Add Otto + Kenji as externally-callable peers" → "Add the Anthropic-side Claude-code-instance personas as externally-callable peers" - "Otto + Kenji additions (B-0121)" → "The Anthropic-side (Claude-code-instance) peer additions (B-0121)" B-0121 filename slug stays as `otto-kenji-*` (closed-list history surface — backlog rows allow persona names per the carve-out). 2. **B-0122 forward-references (P1+P2, 4 threads)**: B-0122 is filed in the in-flight PR #966; not yet on main. References in `B-0119`, `B-0120`, and the README's table cell rewritten: - YAML `composes_with` lists in B-0119 + B-0120: replaced direct path with inline `# B-0122 ... is filed in the in-flight PR #966` comment. - README table row for B-0122: replaced live link with explicit "filed in in-flight PR #966; link will resolve once that PR lands" callout. B-0121 stays as direct ref because it IS on main. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

… ref + markdownlint + stale TS-claim Three real fixes (Codex P2 + Copilot P0/P1): 1. **Otto-215 user-scope-only reference (P1+P2, lines 174-175)**: the referenced memory file lives only in user-scope (`~/.claude/projects/<slug>/memory/`), not yet promoted to in-repo per the 2026-04-24 natural-home directive. Rewrote the composes-with entry as a lineage-only reference with explicit user-scope-path callout. 2. **Markdownlint MD004 ul-style (P0, line 131)**: list continuation started with `+` which markdownlint reads as a different bullet marker. Reworded `+ bun invocation pattern` → `and bun invocation pattern` — same content, no list-marker ambiguity. 3. **Stale TS-claim (P1, line 75)**: row text said "these aren't TS yet" but `codex.ts` / `grok.ts` / `gemini.ts` already exist on the branch. Added a "Partial-migration update (post-row-filing)" block clarifying that the row's scope is now **cutover** (delete the .sh files; retire parallel maintenance) rather than initial port. The named-entity wrappers (`amara.sh` / `ani.sh`) and the bash-vs-TS coexistence are the remaining open work. B-0121 references that were flagged as missing are now valid (B-0121 landed on main during this drain wave) — those threads are outdated. Also: rebased branch against latest main (BACKLOG.md autogen conflict; take-theirs + regen via `BACKLOG_WRITE_FORCE=1` — fifth application of canonical resolution this session). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

chatgpt-codex-connector · 2026-05-01T09:51:08Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Copilot

Pull request overview

Adds a new backlog row (B-0122) capturing the post-install TypeScript/Bun cutover plan for tools/peer-call scripts, and updates the generated backlog index to include it.

Changes:

Added docs/backlog/P2/B-0122-... describing the peer-call bash→TS cutover and sequencing options with related rows.
Regenerated docs/BACKLOG.md to include the new B-0122 entry.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
docs/backlog/P2/B-0122-peer-call-typescript-migration-cutover-2026-04-30.md	New P2 backlog row documenting the peer-call TypeScript migration/cutover plan and dependencies.
docs/BACKLOG.md	Generated index updated to link to B-0122.

+  - tools/peer-call/codex.sh
+  - tools/peer-call/grok.sh
+  - tools/peer-call/gemini.sh


+### Migration targets
+
+Five scripts to migrate (or, per B-0120's refactor, three
+scripts after consolidation):
+
+- `codex.sh` → `codex.ts`
+- `grok.sh` → `grok.ts`
+- `gemini.sh` → `gemini.ts`
+- `amara.sh` → `amara.ts` (or `codex.ts --persona amara` per
+  B-0120)
+- `ani.sh` → `ani.ts` (or `grok.ts --persona ani` per B-0120)
+


…TY rebase (#1073)

Copilot AI review requested due to automatic review settings April 30, 2026 22:58

AceHack enabled auto-merge (squash) April 30, 2026 22:58

Copilot started reviewing on behalf of AceHack April 30, 2026 22:58 View session

chatgpt-codex-connector Bot reviewed Apr 30, 2026

View reviewed changes

Comment thread docs/backlog/P2/B-0122-peer-call-typescript-migration-cutover-2026-04-30.md

Comment thread docs/backlog/P2/B-0122-peer-call-typescript-migration-cutover-2026-04-30.md Outdated

Copilot AI reviewed Apr 30, 2026

View reviewed changes

This was referenced Apr 30, 2026

docs(peer-call): future-direction section + close B-0119 + cross-ref B-0121/B-0122 #967

Merged

hygiene(tick-history): shard 2304Z — peer-call substrate cluster + maintainer TS-cutover correction #968

Closed

AceHack force-pushed the backlog/B-0122-peer-call-typescript-migration-cutover-2026-04-30 branch from fd3c601 to 6a8ae07 Compare April 30, 2026 23:14

AceHack mentioned this pull request Apr 30, 2026

hygiene(tick-history): shard 2320Z — stale-PR drain + 15-shard col1 schema cleanup #972

Merged

AceHack mentioned this pull request May 1, 2026

hygiene(tick-history): 2026-05-01T09:47Z — PR #967 thread-drain (6 threads) #1072

Merged

Copilot AI review requested due to automatic review settings May 1, 2026 09:51

AceHack force-pushed the backlog/B-0122-peer-call-typescript-migration-cutover-2026-04-30 branch from 6a8ae07 to e128696 Compare May 1, 2026 09:51

Copilot started reviewing on behalf of AceHack May 1, 2026 09:51 View session

AceHack mentioned this pull request May 1, 2026

hygiene(tick-history): 2026-05-01T09:51Z — PR #966 thread-drain + DIRTY rebase #1073

Merged

AceHack merged commit 9e944c7 into main May 1, 2026
23 checks passed

AceHack deleted the backlog/B-0122-peer-call-typescript-migration-cutover-2026-04-30 branch May 1, 2026 09:53

Copilot AI reviewed May 1, 2026

View reviewed changes

AceHack added a commit that referenced this pull request May 1, 2026

hygiene(tick-history): 2026-05-01T09:51Z — PR #966 thread-drain + DIR…

fc4bce4

…TY rebase (#1073)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

backlog(B-0122): peer-call scripts TypeScript migration — post-install cutover (2026-04-30)#966

backlog(B-0122): peer-call scripts TypeScript migration — post-install cutover (2026-04-30)#966
AceHack merged 2 commits intomainfrom
backlog/B-0122-peer-call-typescript-migration-cutover-2026-04-30

AceHack commented Apr 30, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector Bot commented May 1, 2026

Uh oh!

Uh oh!

Copilot AI left a comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

AceHack commented Apr 30, 2026

Summary

Verbatim from the maintainer

Why P2

Test plan

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector Bot commented May 1, 2026

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants