@dmsdc-ai/aigentry-telepty 0.3.3 → 0.4.0

package/.claude/commands/telepty-manual-test.md

@@ -1,73 +0,0 @@
-# telepty-manual-test
-
-Guided manual test of the telepty enable (inject) feature. Runs step-by-step verification.
-
-## Instructions
-
-Execute each step sequentially, verifying results before proceeding.
-
-### Step 1: Ensure daemon is running
-```bash
-cd /Users/duckyoungkim/projects/aigentry-telepty
-curl -s http://127.0.0.1:3848/api/sessions 2>/dev/null || node daemon.js &
-sleep 1
-```
-
-### Step 2: Register a wrapped session via API
-```bash
-TOKEN=$(cat ~/.telepty/config.json 2>/dev/null | grep authToken | cut -d '"' -f 4)
-curl -s -X POST http://127.0.0.1:3848/api/sessions/register \
-  -H "Content-Type: application/json" \
-  -H "x-telepty-token: $TOKEN" \
-  -d '{"session_id": "manual-test-1", "command": "test", "cwd": "'"$(pwd)"'"}'
-```
-**Verify**: response has `type: "wrapped"` and status 201.
-
-### Step 3: Check session listing
-```bash
-curl -s http://127.0.0.1:3848/api/sessions -H "x-telepty-token: $TOKEN" | python3 -m json.tool
-```
-**Verify**: `manual-test-1` appears with `type: "wrapped"`.
-
-### Step 4: Test inject without owner (should fail)
-```bash
-curl -s -X POST http://127.0.0.1:3848/api/sessions/manual-test-1/inject \
-  -H "Content-Type: application/json" \
-  -H "x-telepty-token: $TOKEN" \
-  -d '{"prompt": "hello"}'
-```
-**Verify**: returns 503 with "not connected" error.
-
-### Step 5: Clean up test session
-```bash
-curl -s -X DELETE http://127.0.0.1:3848/api/sessions/manual-test-1 \
-  -H "x-telepty-token: $TOKEN"
-```
-**Verify**: returns status "closing".
-
-### Step 6: Verify session removed
-```bash
-curl -s http://127.0.0.1:3848/api/sessions -H "x-telepty-token: $TOKEN"
-```
-**Verify**: `manual-test-1` no longer in the list.
-
-### Step 7: Run automated tests
-```bash
-npm test
-```
-**Verify**: all 25 tests pass.
-
-### Report
-Summarize all verification results in a table:
-
-| Step | Check | Result |
-|------|-------|--------|
-| 2 | Register returns 201 + wrapped | ? |
-| 3 | Session in list with type | ? |
-| 4 | Inject without owner = 503 | ? |
-| 5 | DELETE returns closing | ? |
-| 6 | Session removed | ? |
-| 7 | All tests pass | ? |
-
-## Arguments
-- `$ARGUMENTS`: ignored

package/.claude/commands/telepty-start.md

@@ -1,25 +0,0 @@
-# telepty-start
-
-Start the telepty daemon process.
-
-## Instructions
-
-1. Check if daemon is already running:
-```bash
-curl -s http://127.0.0.1:3848/api/sessions 2>/dev/null && echo "RUNNING" || echo "NOT RUNNING"
-```
-
-2. If not running, start it:
-```bash
-cd /Users/duckyoungkim/projects/aigentry-telepty && node daemon.js &
-```
-
-3. Verify it started:
-```bash
-sleep 1 && curl -s http://127.0.0.1:3848/api/sessions
-```
-
-4. Report status.
-
-## Arguments
-- `$ARGUMENTS`: optional port override (e.g., "3849")

package/.claude/commands/telepty-test.md

@@ -1,25 +0,0 @@
-# telepty-test
-
-Run the telepty automated test suite and report results.
-
-## Instructions
-
-1. Run the full test suite:
-```bash
-cd /Users/duckyoungkim/projects/aigentry-telepty && npm test
-```
-
-2. Parse the output and report:
-   - Total tests, passed, failed
-   - If any failures: show the failing test name and error message
-   - If all pass: confirm with count
-
-3. If tests fail, investigate:
-   - Read the failing test in `test/daemon.test.js`
-   - Check if daemon.js has related issues
-   - Suggest or apply fixes
-   - Re-run tests to confirm
-
-## Arguments
-- No arguments: run all tests
-- `$ARGUMENTS`: if provided, use as a grep filter to run specific tests (e.g., "wrap", "register", "inject")

package/.claude/commands/telepty.md

@@ -1,82 +0,0 @@
-# telepty
-
-Help the user interact with the `telepty` daemon — check session IDs, list active sessions, inject commands, send bus events, and manage terminal windows.
-
-## Trigger
-
-When the user asks about their current session ID, wants to check/list active sessions, inject a prompt into a session, send a JSON event via the bus, subscribe to the bus, rename a session, or update telepty.
-
-## Instructions
-
-### 1. Check Current Session ID
-- Run: `echo $TELEPTY_SESSION_ID`
-- If empty: this shell is NOT inside a telepty session.
-- If set: display it. This is the ID other agents use to target this session.
-
-### 2. List All Sessions
-- Run: `telepty list`
-
-### 3. Send a Message to Another Agent
-Choose ONE of three methods based on intent:
-
-**Method A: Prompt Injection (Active Interruption)**
-The receiving AI will IMMEDIATELY read and execute the message as a prompt.
-```bash
-telepty inject <target_session_id> "<prompt text>"
-```
-For multiple targets: `telepty multicast <id1>,<id2> "<prompt>"`
-
-**Method B: Log Injection (Visual Notification)**
-The message appears on the receiving terminal screen for the user to see, but the AI does NOT execute it as a prompt.
-```bash
-telepty inject <target_session_id> "echo '\x1b[33m[Message from $TELEPTY_SESSION_ID]\x1b[0m <message text>'"
-```
-
-**Method C: Background JSON Bus (Passive/Silent)**
-Structured data transfer that won't disturb the receiving terminal screen.
-```bash
-TOKEN=$(cat ~/.telepty/config.json | grep authToken | cut -d '"' -f 4)
-curl -s -X POST http://127.0.0.1:3848/api/bus/publish \
-  -H "Content-Type: application/json" \
-  -H "x-telepty-token: $TOKEN" \
-  -d '{"type": "bg_message", "payload": "..."}'
-```
-
-### 4. Subscribe to the Event Bus
-```bash
-nohup telepty listen > .telepty_bus_events.log 2>&1 &
-```
-
-### 5. Open a New Ghostty Terminal Window
-Physically spawn a new terminal window already attached to a telepty session:
-```bash
-cat << 'EOF' > /tmp/telepty-auto.command
-#!/bin/bash
-telepty spawn --id <ID> <CMD>
-EOF
-chmod +x /tmp/telepty-auto.command
-open -a Ghostty /tmp/telepty-auto.command || open /tmp/telepty-auto.command
-```
-
-### 6. Terminal Title Convention
-Each telepty session displays its ID in the Ghostty tab title:
-- Local: `⚡ telepty :: {session_id}`
-- Remote: `⚡ telepty :: {session_id} @ {host}`
-
-### 7. Allow Inject on a CLI
-Run any command with inject allowed:
-```bash
-# With custom session ID
-telepty allow --id my-claude -- claude
-telepty allow --id codex-main -- codex
-telepty allow --id gemini-1 -- gemini
-
-# Auto-generated session ID
-telepty allow -- bash
-```
-The process runs locally (isTTY preserved), but registers with the daemon so inject works.
-
-### 8. Update
-```bash
-telepty update
-```

package/AGENTS.md

@@ -1,74 +0,0 @@
-# AGENTS.md — aigentry-telepty
-
-## Overview
-
-PTY Multiplexer & Session Orchestrator — aigentry 에코시스템의 **통신 인프라**.
-npm: `@dmsdc-ai/aigentry-telepty` | 멀티 AI 세션을 생성·연결·제어하는 PTY 멀티플렉서.
-
-## Architecture
-
-```
-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` | CLI 명령 + allow-bridge (PTY 래핑) |
-| `daemon.js` | HTTP/WS 서버, 세션 상태, inject 전달 |
-| `tui.js` | blessed 기반 TUI 대시보드 |
-| `session-routing.js` | 세션 ID 해석, alias 매칭, 호스트 그룹핑 |
-| `daemon-control.js` | 싱글톤 daemon PID 관리 |
-| `auth.js` | UUID 토큰 기반 인증 |
-| `interactive-terminal.js` | raw mode stdin/stdout 관리 |
-| `skill-installer.js` | CLI별 스킬 설치 (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.
-
-## Commands
-
-```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 탭으로 다중 세션 시작
-```
-
-## Key Rules
-
-- inject 후 submit은 항상 `osascript`로 통일 (`--no-enter` + osascript keystroke)
-- inject 시 발신자 session ID (`--from`)를 항상 포함
-- PTY `\r` 직접 의존 금지
-
-## Session Communication
-
-```bash
-# List active sessions
-telepty list
-
-# Send message to another session
-telepty inject --from aigentry-telepty-{cli} <target-session> "message"
-
-# Report to orchestrator
-telepty inject --ref --from aigentry-telepty-{cli} aigentry-orchestrator-claude "report"
-```
-
-## Work Principles
-
-- **Best-First**: 항상 최선의 해결책 선택. 차선책/우회 금지.
-- **Configurable**: 설정으로 제어 가능한 구조. 하드코딩 금지.
-- **Evidence-Based**: 추측 금지. 데이터/로그/테스트 결과 기반 판단.
-- **Fail Fast**: 에러 즉시 보고. 숨기지 않음.
-- **Constitution**: ~/projects/aigentry/docs/CONSTITUTION.md 준수.

package/BOUNDARY.md

@@ -1,31 +0,0 @@
-# telepty Responsibility Boundary
-
-## What telepty owns
-
-- **PTY lifecycle**: spawn, resize, kill PTY processes; emit session_spawn / session_register / session_rename events
-- **Raw stdin write**: accept inject requests and write bytes to the PTY fd (best-effort, fire-and-forget)
-- **stdout streaming**: pipe PTY output to connected WebSocket clients in real time
-- **Bus event broadcast**: publish structured events to all `/api/bus` subscribers
-- **Session lifecycle**: track active sessions, clean up on exit or owner disconnect
-- **Liveness heartbeat**: emit `session_health` every 10 seconds per active session
-
-## What telepty does NOT own
-
-- **CLI state management**: the caller owns its own state machine; telepty does not know what state an agent is in
-- **Inject processing confirmation**: telepty emits `inject_written` when bytes are handed to the OS; it cannot confirm the process consumed or acted on them
-- **Output parsing / interpretation**: telepty streams raw bytes; callers parse meaning
-- **Message guarantee / retry / ordering**: no retry logic, no queue, no ordering guarantees across multiple injects
-- **Session recovery / persistence**: sessions are in-memory; a daemon restart loses all sessions
-- **Cross-session routing**: routing logic (which session gets which message) belongs to the caller or an orchestration layer above telepty
-
-## PTY limitations
-
-- `inject_written` is **best-effort**: it confirms the write syscall to the OS PTY fd succeeded, not that the running process read or processed the input
-- The OS buffers stdin asynchronously; a process blocked, sleeping, or not reading stdin will silently queue the bytes
-- There is no read-back or echo confirmation; callers must observe stdout via the WebSocket stream to infer processing
-
-## Design principle
-
-> **telepty = stateless dumb pipe**
-
-telepty moves bytes. It does not interpret, retry, sequence, or guarantee delivery beyond the OS write call. All higher-level semantics (acknowledgement, ordering, state machines, recovery) are the responsibility of the layer above.

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