@dmsdc-ai/aigentry-telepty 0.3.5 → 0.4.0

package/BUS_EVENT_SCHEMA.md

@@ -1,206 +0,0 @@
-# Telepty Bus Event Schema Standard
-
-Version: 2.0 (2026-03-15)
-Agreed by: telepty, deliberation, devkit, brain, orchestrator
-
-## Transport
-
-- **HTTP**: `POST /api/bus/publish` with JSON body
-- **WebSocket**: `ws://HOST:3848/api/bus` send JSON message
-- Both paths trigger bus auto-router for routable events
-
-## Envelope Structure (All Events)
-
-```json
-{
-  "version": 1,
-  "message_id": "string (UUID or prefixed ID)",
-  "kind": "string (event type)",
-  "source": "string (sender identifier)",
-  "source_host": "string (machine_id of sender, e.g. hostname or Tailscale IP)",
-  "target": "string | null (target session ID, optional @host suffix)",
-  "ts": "ISO 8601 timestamp"
-}
-```
-
-### Canonical Field Names
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `version` | number | Envelope schema version (currently 1) |
-| `kind` | string | Event type (NOT `type` — `kind` is canonical) |
-| `target` | string | Target telepty session ID. May include `@host` suffix for remote |
-| `source` | string | Sender identifier (format: `project:session_id`) |
-| `source_host` | string | Machine ID of sender (hostname or TELEPTY_MACHINE_ID) |
-| `message_id` | string | Unique message identifier |
-| `ts` | string | ISO 8601 timestamp |
-
-## Cross-Machine Addressing
-
-### Session Locator
-Every session is uniquely identified by a locator triple:
-```json
-{ "machine_id": "hostname", "session_id": "aigentry-devkit-001", "project_id": "aigentry-devkit" }
-```
-
-### Remote Target Format
-`target` field supports `@host` suffix: `aigentry-devkit-001@100.100.100.5`
-- Router strips suffix, resolves session on local daemon
-- For cross-machine relay (P3), daemon forwards to target host
-
-### Machine ID
-- Default: `os.hostname()`
-- Override: `TELEPTY_MACHINE_ID` env var
-- Exposed in: `GET /api/meta` (`machine_id` field), session `locator` object, bus event `source_host`
-
-### Global Session ID Uniqueness (P4)
-- Convention: `{project}-{NNN}` (e.g. `aigentry-devkit-001`)
-- Cross-machine uniqueness: guaranteed by `locator.machine_id` prefix in bus events
-- Collision resolution: `resolveSessionAlias` returns local session only; remote sessions discovered via `source_host` field
-- If two machines have `aigentry-devkit-001`, inject uses `target@host` to disambiguate
-- Short form `aigentry-devkit-001` resolves to LOCAL session; remote requires explicit `@host`
-
-### Peer Auth
-- Localhost: always trusted
-- Tailscale (100.x.y.z): trusted by default
-- Custom peers: `TELEPTY_PEER_ALLOWLIST=ip1,ip2` env var
-- All others: require `x-telepty-token` header
-
-## Routable Events (Auto-Router)
-
-### `turn_request`
-
-Published by deliberation to request a turn from a session. Telepty daemon auto-routes to target session PTY.
-
-```json
-{
-  "message_id": "turn_request-<uuid>",
-  "session_id": "<deliberation_session_id>",
-  "project": "<project_name>",
-  "kind": "turn_request",
-  "source": "deliberation:<deliberation_session_id>",
-  "target": "<telepty_session_id>[@<host>]",
-  "reply_to": "<deliberation_session_id>",
-  "trace": ["project:<name>", "speaker:<id>", "turn:<turn_id>"],
-  "payload": {
-    "turn_id": "string",
-    "round": "number",
-    "max_rounds": "number",
-    "speaker": "string (target telepty session ID)",
-    "role": "string | null",
-    "prompt": "string (full prompt text — inject as-is to PTY)",
-    "prompt_sha1": "string (40-char SHA1)",
-    "history_entries": "number",
-    "transport_timeout_ms": "number",
-    "semantic_timeout_ms": "number"
-  },
-  "ts": "ISO 8601"
-}
-```
-
-**Important Notes:**
-- `session_id` is the DELIBERATION session ID, NOT the target telepty session
-- `target` is the telepty session ID to inject into
-- `payload.prompt` is the full text to write to PTY (no further processing needed)
-- `@host` suffix on target: strip before resolving, use for remote routing
-
-**Auto-Router Behavior:**
-1. Daemon receives turn_request via HTTP POST or WS
-2. Extracts `target` field, strips `@host` suffix
-3. Resolves session via `resolveSessionAlias()`
-4. Delivers `payload.prompt` to session PTY (kitty primary, WS fallback)
-5. Emits `inject_written` ack on bus
-
-### `inject_written` (ACK)
-
-Emitted by telepty after successful auto-route delivery.
-
-```json
-{
-  "type": "inject_written",
-  "inject_id": "UUID",
-  "sender": "daemon",
-  "target_agent": "<session_id>",
-  "source_type": "bus_auto_route",
-  "delivered": true,
-  "timestamp": "ISO 8601"
-}
-```
-
-## Session Lifecycle Events
-
-### `session_register`
-```json
-{ "type": "session_register", "sender": "daemon", "session_id": "string", "command": "string", "cwd": "string", "timestamp": "ISO 8601" }
-```
-
-### `session.replaced`
-```json
-{ "type": "session.replaced", "sender": "daemon", "old_id": "string", "new_id": "string", "alias": "string", "timestamp": "ISO 8601" }
-```
-
-### `session.idle`
-```json
-{ "type": "session.idle", "session_id": "string", "idleSeconds": "number", "lastActivityAt": "ISO 8601", "timestamp": "ISO 8601" }
-```
-
-### `session_health` (periodic, every 10s)
-```json
-{ "type": "session_health", "session_id": "string", "payload": { "alive": true, "pid": "number|null", "type": "string", "clients": "number", "idleSeconds": "number|null" }, "timestamp": "ISO 8601" }
-```
-
-## Inject Events
-
-### `inject_written`
-```json
-{ "type": "inject_written", "inject_id": "UUID", "sender": "daemon", "target_agent": "string", "content": "string", "from": "string|null", "reply_to": "string|null", "thread_id": "string|null", "reply_expected": "boolean", "timestamp": "ISO 8601" }
-```
-
-### `message_routed`
-```json
-{ "type": "message_routed", "message_id": "UUID", "from": "string", "to": "string", "reply_to": "string", "inject_id": "UUID", "deliberation_session_id": "string|null", "thread_id": "string|null", "timestamp": "ISO 8601" }
-```
-
-## Handoff Events
-
-### `handoff.created` / `handoff.claimed` / `handoff.executing` / `handoff.completed`
-```json
-{ "type": "handoff.<status>", "handoff_id": "UUID", "source_session_id": "string|null", "deliberation_id": "string|null", "auto_execute": "boolean", "task_count": "number", "timestamp": "ISO 8601" }
-```
-
-## Thread Events
-
-### `thread.opened`
-```json
-{ "type": "thread.opened", "thread_id": "UUID", "topic": "string", "orchestrator_session_id": "string|null", "participant_session_ids": ["string"], "timestamp": "ISO 8601" }
-```
-
-### `thread.closed`
-```json
-{ "type": "thread.closed", "thread_id": "UUID", "topic": "string", "message_count": "number", "timestamp": "ISO 8601" }
-```
-
-## Termination Signal Detection
-
-Messages containing these strings suppress auto-reply guide footer:
-- `no further reply needed`
-- `thread closed` / `closed on X side`
-- `ack received` / `ack-only`
-- `회신 불필요` / `스레드 종료`
-
-## Inject API Reference
-
-### `POST /api/sessions/:id/inject`
-
-```json
-{
-  "prompt": "string (REQUIRED — canonical body field)",
-  "from": "string (sender session ID)",
-  "reply_to": "string (defaults to from if omitted)",
-  "thread_id": "string (optional)",
-  "reply_expected": "boolean (optional)",
-  "no_enter": "boolean (skip Enter after inject)"
-}
-```
-
-**Note:** The canonical body field is `prompt`, NOT `text`, `content`, or `message`.

package/CLAUDE.md

@@ -1,100 +0,0 @@
-# telepty — PTY Multiplexer & Session Orchestrator
-
-aigentry 에코시스템의 **통신 인프라**. 멀티 AI 세션을 생성·연결·제어하는 PTY 멀티플렉서.
-
-## 에코시스템 내 역할
-
-9개 aigentry 세션(orchestrator, brain, amplify, dustcraw 등) 간 통신을 담당:
-- 세션 생성/관리 (`allow`, `spawn`)
-- 메시지 전달 (`inject`, `broadcast`, `multicast`, `reply`)
-- 실시간 모니터링 (`tui`, `monitor`, `listen`)
-- 세션 간 토론 조율 (`deliberate`)
-
-## 아키텍처
-
-```
-CLI (cli.js) ──→ HTTP/WS ──→ Daemon (daemon.js:3848)
-                                ├── Session WS (/api/sessions/:id)
-                                ├── Event Bus WS (/api/bus)
-                                └── REST API (/api/sessions/*)
-```
-
-### 핵심 모듈
-
-| 파일 | 줄수 | 역할 |
-|------|------|------|
-| `cli.js` | ~1950 | CLI 명령 + allow-bridge (PTY 래핑) |
-| `daemon.js` | ~1550 | HTTP/WS 서버, 세션 상태, inject 전달 |
-| `tui.js` | ~500 | blessed 기반 TUI 대시보드 |
-| `session-routing.js` | 81 | 세션 ID 해석, alias 매칭, 호스트 그룹핑 |
-| `daemon-control.js` | 223 | 싱글톤 daemon PID 관리 |
-| `auth.js` | 33 | UUID 토큰 기반 인증 |
-| `interactive-terminal.js` | 71 | raw mode stdin/stdout 관리 |
-| `skill-installer.js` | 269 | Claude/Codex/Gemini 스킬 설치 |
-
-### Inject 전달 경로 (wrapped session)
-
-1. **Primary**: `kitty @ send-text` (터미널 직접 전달, allow-bridge 우회)
-2. **Fallback**: WS → allow-bridge → `child.write()` (PTY)
-3. **Submit**: `osascript` Return 키 → kitty fallback → WS `\r`
-
-busy 세션: CR은 큐에 대기 중인 텍스트와 함께 큐잉 후 올바른 순서로 flush.
-
-## 명령어
-
-```bash
-# 테스트
-npm test                    # 43 tests (node:test)
-
-# 실행
-telepty daemon              # daemon 시작 (포트 3848)
-telepty allow --id <name> claude  # 세션 래핑
-telepty tui                 # TUI 대시보드
-telepty list                # 세션 목록
-telepty inject <id> "msg"   # 메시지 주입
-telepty broadcast "msg"     # 전체 브로드캐스트
-telepty session start --launch  # kitty 탭으로 다중 세션 시작
-
-# 릴리스
-npm version patch --no-git-tag-version && npm publish --access public
-```
-
-## 주요 규칙
-
-- inject 후 submit은 항상 `osascript`로 통일 (`--no-enter` + osascript keystroke)
-- inject 시 발신자 session ID (`--from`)를 항상 포함
-- PTY `\r` 직접 의존 금지
-
-## 최근 주요 변경 (v0.1.58–0.3.3)
-
-| 버전 | 변경 |
-|------|------|
-| 0.3.3 | inject `--submit-force` (gate bypass) + idempotent `--submit-retry` (default 1, retry-safe 504만). 클라이언트 측 변경, daemon 무수정. task #347. |
-| 0.3.2 | Layer 3 prompt-symbol 렌더 게이트 — claude/codex/gemini 별 prompt symbol을 cmux read-screen으로 polling. |
-| 0.3.1 | 게이트 임계값 0.85 → 0.5 완화 + dispatch-on-timeout best-effort + send-key force=true 우회 추가. |
-| 0.3.0 | Render-gated submit (sessionStateManager 기반). Enter 송신 전 REPL ready 검증. |
-| 0.1.62 | TUI 태스크 추적 — bus 이벤트에서 [태그] 자동 파싱, 세션별 상태 표시 |
-| 0.1.61 | reconnect 시 resize/\x0c 제거 (멀티터미널 깜빡임 수정) |
-| 0.1.60 | TUI P1 — s=start, k=kill, p=purge stale |
-| 0.1.59 | wrapped inject 503 반환 + 테스트 43/43 정합성 |
-| 0.1.58 | inject busy-session CR/text 순서 수정 + kittyWindowId 캐시 무효화 |
-
-## 자율 재귀적 오케스트레이션
-
-이 세션은 작업 복잡도가 높거나, 독립 도메인이 식별되거나, 컨텍스트 분리가 필요하다고 판단되면 — 사용자 지시 없이 자율적으로:
-
-1. 자기 프로젝트 하위에 폴더를 생성한다
-2. 해당 폴더에 CLAUDE.md를 작성한다 (역할, 범위, 상위 세션과의 통신 방법)
-3. aigentry scaffold 또는 telepty allow로 하위 Claude 세션을 생성한다
-4. telepty inject로 하위 세션에 태스크를 주입한다
-5. 하위 세션의 결과를 수신하고 통합한다
-
-판단 기준:
-- 현재 작업이 2개 이상 독립 도메인을 포함할 때
-- 컨텍스트 윈도우의 30% 이상을 단일 하위 작업이 차지할 때
-- 반복적 전문 작업이 식별될 때 (SEO, 특정 채널, 특정 데이터 소스 등)
-
-원칙:
-- YAGNI: 진짜 필요할 때만 생성. 과잉 분리 금지.
-- 하위 세션 완료 시 오케스트레이터(상위)에게 반드시 보고.
-- 하위 세션의 결과물은 상위 프로젝트에 통합(커밋).

package/GEMINI.md

@@ -1,10 +0,0 @@
-@AGENTS.md
-
-# Gemini CLI — aigentry-telepty
-
-## Gemini 전용 설정
-
-- 세션 ID: `aigentry-telepty-gemini`
-- 보고: `telepty inject --ref --from aigentry-telepty-gemini aigentry-orchestrator-claude "보고 내용"`
-- Gemini 강점 활용: upstream 이슈 검색, API 리서치, 문서화 우선
-- 헌법: `~/projects/aigentry/docs/CONSTITUTION.md`

package/URGENT_ISSUES.resolved.md

@@ -1 +0,0 @@
-RESOLVED - all 3 urgent issues fixed in 40b8e47

package/docs/reports/2026-05-05-issue-8-claude-review.md

@@ -1,194 +0,0 @@
-# Issue #8 Claude Review of Codex Implementation (2026-05-05)
-
-| Field | Value |
-|---|---|
-| Reviewer | Claude (cross-LLM rule — Codex impl → Claude review) |
-| Implementer | Codex (`aigentry-telepty-coder-issue-8`, closed) |
-| Range | `d7b8b21..d0f4495` (16 commits) + `aigentry-ssot@f4ff0cd` |
-| Spec | `~/projects/aigentry-telepty/docs/specs/2026-05-05-issue-8-telepty-init.md` (commits 609092b → 8d2dc94) |
-| Boundary ADR | `aigentry-orchestrator/docs/adr/2026-05-05-telepty-devkit-boundary.md` (e4b072b ACCEPTED) |
-| Test result | 269/269 full suite PASS; 15/15 init suite PASS |
-| Mode | Read-only audit per Invariant I1 |
-
----
-
-## §1 Summary
-
-- **Verdict:** **ACCEPT**
-- **Top issue:** None blocking. Two non-blocking process observations (N1: TDD ordering, N2: version bump deferred to release).
-- **Tests-pass / spec-fidelity gap:** **0 mismatches.** All 15 init tests map 1:1 to spec §8.1-§8.6 items; assertions match spec text (with one minor interpretation noted at §7.1).
-
----
-
-## §2 Spec Fidelity Audit
-
-| Check | Result | Evidence |
-|---|---|---|
-| CLI surface matches §3.1/§4 verbatim | PASS | `src/init/print-snippet.js:11` HELP string is `usage: telepty init --print-snippet [--target {claude\|agents\|gemini\|all}] [--format {markdown\|json}]` — byte-equal to spec §3.1 row 1 wording |
-| argv-only, stdin closed | PASS | `cli.js:844` dispatches `runInit(args.slice(1))`; `print-snippet.js` never reads stdin; test 12 verifies stdin pipe payload is ignored |
-| Exit codes 0/2/4 implemented (3 reserved-not-emitted) | PASS | `print-snippet.js:77,82,87,97,100`. Code 3 is "telepty too old" (only emitted by absent telepty itself; spec §3.5 confirms detection via shell exit 127 OR exit 3 — not by current telepty). |
-| Default `--target=all --format=markdown` | PASS | `print-snippet.js:43-44` defaults; test 9 verifies |
-| §3.2 markdown sentinel envelope | PASS | `print-snippet.js:28` emits `<!-- telepty-snippet/v1 BEGIN target=<t> sha256=<hex8> -->\n<body><!-- ... END target=<t> -->\n` matching spec §3.2 byte-for-byte |
-| §3.3 NDJSON shape | PASS | `print-snippet.js:31-38` emits `{version,target,sha256,body}` with full 64-hex digest; test 5 verifies |
-| §3.4 stderr policy (warnings only on happy path) | PASS | Test 13 asserts `result.stderr === ''` for `--target claude` |
-| `--target=all` separator (empty line between envelopes) | PASS | `print-snippet.js:96` joins with `'\n'` (single LF after each envelope's trailing LF → blank line); test 4 asserts the `END target=claude -->\n\n<!-- telepty-snippet/v1 BEGIN target=agents` literal |
-
-**8/8 fidelity checks PASS.**
-
----
-
-## §3 Boundary ADR Audit
-
-| Check | Result | Evidence |
-|---|---|---|
-| No file I/O on user dotfiles | PASS | `grep -nE 'writeFile\|writeFileSync\|appendFile\|chmod\|unlink' src/init/` returns zero matches; only `fs.readFileSync` of own `src/init/snippets/*.md` |
-| No subprocess invocation of devkit | PASS | `grep -nE 'child_process\|spawn\|exec\|aigentry\|scaffold' src/init/print-snippet.js` returns zero matches; `aigentry` only appears as descriptive text inside snippet body (per §3.1 rule 2) |
-| §3.4 row 1 "no file editing in telepty" | PASS | Verified by file-mutation grep above |
-| §3.5 mechanism-vs-content split (telepty = mechanism) | PASS | Snippet bodies describe telepty's own CLI surface only (rule 2); zero per-CLI placement guidance ("paste this into CLAUDE.md…") in body or section headers |
-| §3.3.1.5 telepty CI runs without `aigentry` | PASS | Manually verified: `env -i HOME=/tmp/empty PATH=/usr/bin:/bin:<node-dir> node cli.js init --print-snippet --target claude` → exit 0, full envelope emitted; test 15 enforces in-suite |
-
-**Boundary ADR: PASS (5/5).**
-
----
-
-## §4 OC Choice Verification
-
-| Choice | Spec | Impl Evidence | Result |
-|---|---|---|---|
-| **OC-1=B** | snippet bodies in `src/init/snippets/{claude,agents,gemini}.md` (NOT inline JS, NOT JSON manifest) | Three files exist, `loadBody()` reads via `fs.readFileSync(path.join(snippetDir, '${target}.md'), 'utf8')` | PASS |
-| **OC-2=B** | `npm run regen-fixtures` script + CI uses `git diff --exit-code` | `package.json:15` `regen-fixtures` script exists; `package.json:12,14` `test`/`test:ci` end with `&& git diff --exit-code tests/snippet-protocol/v1/` | PASS |
-| **OC-3=A** | section header is mechanism-only (no per-CLI prelude) | Each `snippets/<t>.md` line 1 is `## telepty-snippet:<target>`; no "Add this block to AGENTS.md" prelude anywhere in body | PASS |
-| **OQ-A** | G1 SSOT stub merged sibling cross-repo | `aigentry-ssot@f4ff0cd` adds `contracts/telepty-snippet-v1.md`; commit time 14:35:07 < final telepty commit 14:36:19 (correct atomic ordering); SSOT stub references spec doc URL | PASS |
-| **OQ-C** | markdown=8-char sha256 prefix; JSON=64-char full digest | Markdown sentinel: `sha256=305aad81` (8 hex); JSON record: `"sha256":"305aad8181c1e75bb94589386cbc34f2b5103d6b5c1f6a7f01c99f1fbf6ed8c3"` (64 hex). Test 1 asserts `/sha256=[0-9a-f]{8}/`; test 5 asserts `/^[0-9a-f]{64}$/`. SSOT stub publishes the 64-hex hash table per target. | PASS |
-
-**OC choices: 4/4 honored.** (OQ-A and OQ-C are bundled — count as 4 since orchestrator dispatch listed them as 4 distinct items; logical mapping = 5/5 if OQ-A and OQ-C are scored separately.)
-
----
-
-## §5 Constitutional Audit
-
-| Article | Check | Result |
-|---|---|---|
-| **1 경량** | No premature abstractions. Two helpers added beyond spec §7.3 skeleton: (a) `loadBody(target, options)` accepts `options.snippetDir` for test injection — justified by §8.3 test 11 spec text "non-existent template path injection"; (b) `cli.js` lazifies `getAuthToken()` — necessary so `init --print-snippet` works on a fresh machine with no `~/.telepty/config.json` (Article 9). Both are minimal seams, neither is speculative. | PASS |
-| **3 역할** | Telepty does mechanism (stdout contract + sha256 envelope) only. Snippet body content describes telepty's own CLI surface — rule 2 of §3.1 4-rule sharpening. | PASS |
-| **9 독립** | Verified manually: `env -i HOME=… PATH=…<no aigentry>… node cli.js init --print-snippet` exits 0 with full envelope. Test 15 enforces inside the test suite. | PASS |
-| **15 SSOT** | `aigentry-ssot/contracts/telepty-snippet-v1.md@f4ff0cd` registered before final telepty commit; spec doc and ADR references present in stub. | PASS |
-| **17 무의존** | `git diff d7b8b21 d0f4495 -- package.json` shows zero new entries under `dependencies`. Only test-runner additions and `regen-fixtures` script. | PASS |
-
-**Constitutional: 5/5.**
-
----
-
-## §6 Test Coverage vs Spec Map
-
-15 init tests → spec §8.1-§8.6. All consistent.
-
-| # | Test (file:line) | Spec § | Verdict |
-|---|---|---|---|
-| 1 | markdown for claude includes target+8-char sha256 (`init.test.js:94`) | §8.1.1 | ✓ literal |
-| 2 | markdown for agents (`:102`) | §8.1.2 | ✓ literal |
-| 3 | markdown for gemini (`:110`) | §8.1.3 | ✓ literal |
-| 4 | markdown all = 3 envelopes ordered claude→agents→gemini, blank-line separator (`:118`) | §8.1.4 | ✓ literal — also asserts `END target=claude -->\n\n<!-- telepty-snippet/v1 BEGIN target=agents` |
-| 5 | json all = 3 NDJSON typed records (4 keys, 64-char sha256) (`:132`) | §8.1.5 | ✓ literal — `Object.keys` deepEqual + per-key type assertions |
-| 6 | bodies no shell-substitution hazards (`:149`) | §8.2.6 | ✓ semantic — see §7.1 below for interpretation note |
-| 7 | bodies LF-only (`:162`) | §8.2.7 | ✓ literal |
-| 8 | byte-identical sequential invocations (`:170`) | §8.2.8 | ✓ literal |
-| 9 | print-snippet defaults exit 0, all/markdown (`:181`) | §8.3.9 | ✓ literal — also verifies default `--target=all` order |
-| 10 | unsupported target → exit 2, stderr matches, empty stdout (`:192`) | §8.3.10 | ✓ literal — stderr regex `/--target must be one of claude, agents, gemini, all/` exact |
-| 11 | internal failure → exit 4, empty stdout, stderr non-empty (`:200`) | §8.3.11 | ✓ literal — uses `snippetDir` injection (path-injection seam, matches spec wording "non-existent template path injection") |
-| 12 | stdin pipe ignored, output unchanged (`:214`) | §8.4.12 | ✓ stronger — pipes `'ignored stdin payload\n'` before close (spec said only "immediately closes child stdin") |
-| 13 | clean stderr happy path (`:224`) | §8.4.13 | ✓ literal |
-| 14 | golden fixtures byte-equal × 8 (`:231`) | §8.5.14 | ✓ literal — `fs.readFileSync` + `assert.strictEqual` × 4 targets × 2 formats; `npm test` also runs `git diff --exit-code tests/snippet-protocol/v1/` per spec §7.5 |
-| 15 | devkit-free PATH (`:245`) | §8.6.15 | ✓ literal — `pathWithoutAigentryExecutables()` filter + asserts exit 0 + `assert.equal(result.stdout, expected)` against `golden-all.md` |
-
-**Map consistency: 15/15.** No test misreads its spec section. No orphan tests, no orphan spec items.
-
----
-
-## §7 Cross-LLM Blind Spot Findings
-
-### §7.1 Test 6 wording-stretch (NON-BLOCKING)
-
-Spec §8.2 item 6 reads:
-
-> "For each target, body bytes contain none of: `$HOME`, `$(`, backtick (`` ` ``) outside fenced code blocks, literal `~` anywhere in body."
-
-The literal-strict reading of "backtick outside fenced code blocks" means **bare backticks should not appear at all** in the body (since the body has no fenced ```` ``` ```` blocks). However, the body does contain inline-code spans (single-backtick `<name>`, `telepty allow`, etc.) which are markdown-legitimate.
-
-The test (`init.test.js:156-158`) takes the **security-intent reading**: backticks are allowed inside inline code spans, but the inline code content must not contain shell metacharacters `[$;|&]`:
-
-```js
-for (const inlineCode of body.matchAll(/`([^`\n]+)`/g)) {
-  assert.doesNotMatch(inlineCode[1], /[$;|&]/);
-}
-```
-
-This stretches the spec wording but preserves the spec's stated security intent ("Defends §3.1.1.1 line 161 'no shell substitution.'"). Without this interpretation, the spec would be self-contradictory — the canonical body in §A intentionally uses inline backticks. **Recommendation:** spec §8.2 item 6 should be amended to say "no shell metacharacters inside inline-code spans" rather than the literally-impossible "no backtick outside fenced code blocks." Not a blocker; existing implementation is correct in spirit.
-
-### §7.2 `loadBody(target, options)` test seam (NON-BLOCKING)
-
-`print-snippet.js:17` accepts an `options.snippetDir` parameter that is not in spec §7.3 skeleton. This is the path-injection seam used by test 11 (`init.test.js:206`) to drive the exit-code-4 internal-failure branch. Spec §8.3 item 11 explicitly mentions "non-existent template path injection" as the test mechanism, so the helper is justified. Codex tendency: lightly extends API surface for test ergonomics — here the extension is limited (one option, single call site) and warranted.
-
-### §7.3 `cli.js` lazy `getAuthToken()` (NON-BLOCKING — actually defensible)
-
-`cli.js` was changed to lazify `getAuthToken()` from a module-load-time `const TOKEN`. Without this change, `telepty init --print-snippet` would fail on a fresh machine (no `~/.telepty/config.json`). **This is a prerequisite for Article 9 / §8 M3 compliance**, not scope creep — the test 15 devkit-free path would otherwise fail. Side benefit: every CLI command that doesn't need the daemon now starts without touching the config. Net positive.
-
-### §7.4 TDD ordering — spec procedural directive not honored at commit level (NON-BLOCKING)
-
-Spec §8 says "Each item is a failing-test-first checkpoint per `superpowers:test-driven-development`." Commit log shows:
-
-- `f5c6bad feat(init): emit claude markdown snippet` (introduces impl + 1 test as a single commit)
-- 14 follow-up `test(init): …` commits adding tests after-the-fact
-
-This is **test-after development packaged as TDD-style commits**, not red-green-refactor. All tests do pass, all spec items are covered, all assertions match spec text — so the **outcome** is identical to TDD. The **process** does not match spec wording. Codex tendency: optimizes for test pass speed by writing impl first, then back-filling tests in clean commits. Flagging for orchestrator awareness; not a correctness blocker.
-
-### §7.5 Cross-repo coupling check
-
-SSOT stub at `aigentry-ssot@f4ff0cd` and telepty PR are atomically deliverable (commit timestamps: SSOT 14:35:07 < final telepty 14:36:19). The SSOT stub references the spec doc path. Spec §7.6 also requires "telepty PR description cite SSOT SHA" — since these are local commits without a PR description yet, this requirement attaches to the eventual `git push` / PR creation step (out of this review's scope but flagged for the orchestrator's push action).
-
----
-
-## §8 Code Quality Notes
-
-- **Diff hygiene:** 16 commits, each test in its own commit (`test(init): …`). Excellent reviewability; bisect-friendly. Process flag at §7.4 about ordering does not detract from per-commit quality.
-- **No unused code:** `print-snippet.js:104-114` exports include `HELP`, `TARGETS`, `VERSION`, `buildOutput`, `emitJson`, `emitMarkdown`, `loadBody`, `main: buildOutput`, `sha256Hex`. The aliased `main: buildOutput` is consumed by `cli.js:843` (`const { main: runInit } = require(...)`); `buildOutput` directly is consumed by tests; helpers `emitJson`/`emitMarkdown`/`loadBody`/`sha256Hex` are not externally consumed (could be flagged as over-export, but test ergonomics make them defensible). NOT a blocker.
-- **No dead branches:** every condition path is tested (defaults, help, all/single targets, format markdown/json, bad target → 2, internal fail → 4).
-- **No security issues:** snippet bodies are static template files baked into the repo; no shell-eval, no template substitution, no env-var expansion. Test 6 (security intent) verifies inline-code spans stay free of `[$;|&]`.
-- **Stderr policy:** all 4 stderr writes use `error: …` prefix and a literal newline. Spec §3.4 says "warnings only" on happy path; all error stderr writes are accompanied by non-zero exit code, satisfying the "errors are reflected by exit code, stderr carries diagnostic" model.
-- **Argv parser:** `parseArgs` (lines 40-68) handles `--key value` and `--key=value` forms for `--target` and `--format`. Spec didn't mandate `--key=value` form, but supporting both is conventional and harmless. Edge case: unrecognized flags are silently ignored. Spec doesn't require strict argv validation; acceptable for v1.
-- **Version pin:** `package.json` is at `0.3.4`; spec target was "≥ 0.3.5 (next minor, additive)." The version bump to `0.3.5` is implicitly deferred to the actual `npm version` release commit (separate from this implementation PR). Acceptable as release-time work.
-
----
-
-## §9 Conditions (none blocking)
-
-No `ACCEPT_WITH_CONDITIONS` triggered. The four §7 findings are all NON-BLOCKING and either (a) a recommended spec-wording amendment (§7.1), (b) a defensible deviation explained by spec text (§7.2, §7.3), (c) a process observation that doesn't affect correctness (§7.4), or (d) a coordination note for the eventual PR push (§7.5).
-
-If the orchestrator wishes to attach optional follow-ups:
-1. **Spec amendment (recommended):** rewrite §8.2 item 6's "backtick outside fenced code blocks" to "no shell metacharacters `$;|&` inside inline-code spans" to match the implemented (and correct-in-spirit) test.
-2. **Release commit:** `npm version 0.3.5 --no-git-tag-version` + `npm publish` should be a separate commit after this PR's merge per §7.5 release-time deferral.
-
----
-
-## §10 Verdict + Push Recommendation
-
-**Final verdict:** **ACCEPT.**
-
-**Atomic batch push readiness:** **YES.**
-
-**Recommended commit range:**
-- `aigentry-telepty`: `d7b8b21..d0f4495` (16 commits, 15 tests + 8 fixtures + impl + cli wiring + scripts/regen-snippet-fixtures.js + version-test alignment)
-- `aigentry-ssot`: `f4ff0cd` (G1 SSOT stub, single commit)
-
-**Push order:** SSOT stub first (already committed at 14:35:07, before the final telepty test commit at 14:36:19); telepty PR description should cite `f4ff0cd` per spec §7.6 cross-repo coordination requirement.
-
-**Verification evidence captured this review:**
-- `npm test` → 269/269 pass (full suite); 15/15 init suite
-- `git diff --exit-code tests/snippet-protocol/v1/` clean (golden fixtures byte-equal)
-- Manual M3 smoke: `env -i HOME=/tmp/empty PATH=/usr/bin:/bin:<node> node cli.js init --print-snippet --target claude` → exit 0
-- SSOT body hashes verified equal to runtime `sha256` digests for all 3 targets
-- Boundary scan: zero file-mutation, zero subprocess-of-devkit in `src/init/`
-
----
-
-*End of review.*