context-packetlisted

<essential_principles> context-packet is a file-based context resolution library for AI agent DAG workflows. Three primitives, zero dependencies. **Core loop:** Define a graph. Resolve upstream context. Do work. Submit a packet. Repeat. **Four interfaces:** - **MCP server** — registered as `context-packet` in Claude Code. Agent gets tools to resolve/submit within a full session with all capabilities. The recommended approach for Claude Code workflows. - **CLI** — `context-packet init|resolve|submit|read|status|hash|run` — any process that can shell out - **`run` command** — `context-packet run --agent "claude -p" --input "..."` — executes entire DAG automatically with parallel node execution - **TypeScript API** — `init()`, `resolve()`, `submit()`, `read()`, `status()`, `run()` **Graph features:** - `depends_on` — execution order edges (must complete before this node runs) - `consumes` — data edges (need the packet, no ordering constraint) - `system` — system prompts at graph level (all nodes) and node level (specialization) - `config.maxTokens` ��� per-node token budget for upstream context resolution **Key concepts:** - `Packet` — structured JSON record: status, summary, body, data, artifacts, input_hash - `.context-packet/` — all state lives on disk as plain JSON files. Delete to reset, copy to share. - Token budgeting — `resolve()` accepts `maxTokens`, truncates distant nodes first, always keeps summaries - Anti-injection — upstream data wrapped in `[DATA FROM "node"