@tangle-network/starter-foundry 0.7.3 → 0.13.2

package/LICENSE-APACHE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,212 +1,101 @@
 # starter-foundry
 
-Deterministic project scaffold engine for AI coding platforms. Routes a user prompt to the right project structure, composes files, and gives the AI agent a concrete build plan — all in under 10ms.
+A deterministic project-scaffold engine for AI coding agents. It routes a natural-language prompt to the right project structure, composes the files, and hands the agent a concrete build plan — in **under 10 ms, with no LLM call on the hot path**.
 
 ```
 "Build a Next.js SaaS with Stripe billing and team management"
-  → nextjs-ts + capability:saas-teams + capability:tailwind + capability:layout-dashboard
-  → 14 files composed
-  → Build plan: create /settings/team, /dashboard, wire /api/team/invite, build TeamMemberList, InviteForm, Sidebar
+  → nextjs-ts + saas-teams + tailwind + layout-dashboard
+  → 14 files written, plus a build plan:
+    create /settings/team and /dashboard, wire /api/team/invite,
+    build TeamMemberList, InviteForm, Sidebar
 ```
 
-## How it works
-
-```
-User prompt → planPrompt() → composeStarter() → scaffold + build plan → AI agent starts building
-              ~1ms            ~3ms               ~5ms
-```
-
-The hot path is fully deterministic — no LLM calls, no network. A keyword scorer routes prompts to families, a capability detector attaches specialization layers, and the compose engine writes template files to disk.
-
-## Registry
-
-| | Count | Examples |
-|---|---|---|
-| **Families** | 94 | nextjs-ts, react-vite-ts, agent-service-ts, forge-contracts, solana-native-rust, python-http, go-net-http, sveltekit-ts, wasm-rust, bun-http, tangle-blueprint, kotlin-multiplatform |
-| **Capability layers** | 104 | See categories below |
-| **Slot layers** | 28 | database (sqlite/postgres/mongodb/convex), auth (clerk/better-auth/supabase), payments (stripe/coinbase-commerce), sdk (evm-wallet/solana-web3/coinbase-cdp), queue (bullmq/trigger-dev), industry (10 verticals) |
-| **Partners** | 19 | Arbitrum, Avalanche, Chainlink, Coinbase, EigenLayer, Farcaster, Hyperliquid, Lens, Linea, Monad, Polygon, Sei-EVM, Solana, Sui, Tangle, Tempo, Tether, USDC-Circle, XLayer |
-| **Product archetypes** | 115+ | "Twitter clone" → fullstack-ts + realtime-ws + saas-teams |
-
-### Capability layers by category
-
-**Layout (rich UI — production-ready React components):**
-layout-dashboard (sidebar + KPIs + activity feed), layout-landing (hero + features + pricing), layout-chat (message list + streaming input + sidebar), layout-admin (TanStack data table + entity form), layout-auth (sign-in/sign-up pages), layout-settings (profile/billing/team tabs)
-
-**Crypto frontend UI:**
-crypto-swap-ui (DEX swap card + token selector + pool card), crypto-staking-ui (staking dashboard + validator card), crypto-bridge-ui (bridge card + tx history), crypto-portfolio-ui (portfolio overview + token rows), crypto-governance-ui (proposal cards + voting), crypto-launchpad-ui (sale card + vesting schedule)
-
-**AI/Agent UI:**
-ai-chat-sessions (ChatGPT-style session list + folders + header), ai-agent-orchestrator (multi-agent timeline + tool call traces), ai-rag-chat (source citations + knowledge base manager), ai-voice-chat (voice orb + transcript + call controls)
+The point: give the agent a real starting point instead of a blank directory. The routing is a keyword scorer plus a capability detector — fully reproducible, no network, no model.
 
-**Agent frameworks:** agent-rag, agent-langgraph, agent-mastra, agent-multi-agent, agent-trading, agent-voice, agent-slack, agent-github, agent-browser, agent-code-review, agent-customer-support, agent-data-pipeline, agent-intel, agent-openclaw, agent-hermes, agent-ai-sdk
-
-**DeFi/Crypto config:** defi-lending, defi-dex, defi-perpetuals, defi-yield, defi-restaking, defi-bridge, solana-amm, solana-perps, solana-staking, solana-nft, solana-prediction, solana-launchpad, solana-keeper, move-amm, move-staking, move-nft, move-oracle, move-launchpad, fhe-private-token, fhe-private-voting, fhe-sealed-auction
-
-**EVM infra:** evm-account-abstraction, evm-chain-monitor, evm-deploy-foundry, evm-layerzero-oft, evm-protocol-api, evm-wallet-dashboard
+## Install
 
-**Other:** marketplace, webrtc, shadcn, tailwind, chart-widget, json-render, saas-billing, saas-teams, realtime-ws, deploy-docker, deploy-github-actions, infra-k8s, infra-terraform, infra-pulumi, exchange-binance, exchange-coinbase, exchange-okx, gpu-modal, gpu-replicate, gpu-together, effect-ts, logging, webhook-processor, market-sim, icons, typography, tangle-custody, tangle-oracle, ai-chat-ui, ai-agent-dashboard, ai-fine-tuning, admin-crud
+```sh
+npm i @tangle-network/starter-foundry        # library
+npx @tangle-network/starter-foundry --help   # CLI
+```
 
-### Variants
+Requires Node ≥ 20.
 
-Layout layers support **visual variants** — different design treatments of the same component structure. The compose engine picks a variant deterministically from the project name, so every scaffold looks distinct but the result is reproducible.
+## Quickstart
 
-| Layer | Variants |
-|---|---|
-| layout-landing | gradient-hero, minimal-clean, dark-product |
-| layout-dashboard | sidebar, topnav |
+Scaffold a project from a prompt into the current directory:
 
-## Programmatic API
+```sh
+npx @tangle-network/starter-foundry compose-prompt --prompt "realtime chat app with auth" --out .
+```
 
-```typescript
-import { planPrompt, composeStarter, createContextPack } from 'starter-foundry'
+Or drive the pipeline from code:
 
-const plan = await planPrompt({
-  prompt: 'Build a RAG chatbot with vector search',
-  partner: null,
-})
+```ts
+import { planPrompt } from '@tangle-network/starter-foundry/planner'
+import { composeStarter } from '@tangle-network/starter-foundry/compose'
 
-const result = await composeStarter({ spec: plan.spec, outDir: '/tmp/project' })
-const context = await createContextPack({ spec: plan.spec, outDir: '/tmp/project' })
+const plan = planPrompt('realtime chat app with auth')   // family + capability layers
+const result = await composeStarter({ spec: plan.spec, outDir: './app' })
+console.log(result.files, result.buildPlan)
 ```
 
-## CLI
+## How it works
 
-```bash
-npm run build && node dist/cli.js <command>
 ```
-
-| Command | Description |
-|---------|-------------|
-| `plan --prompt <text> [--partner <id>]` | Route a prompt to a family + capabilities |
-| `compose --spec <path> --out <dir>` | Compose a starter project |
-| `workspace-compose --spec <path> --out <dir>` | Compose a multi-project workspace |
-| `validate --spec <path>` | Run validation checks |
-| `context --spec <path>` | Generate a context pack with build plan |
-| `bench --spec <path> [--runs <n>]` | Benchmark compose + validate timing |
-| `prove --corpus <path> --out <dir>` | Run proof suite over a prompt corpus |
-| `catalog` | List all families and layers |
-
-## Toolchain (for `pnpm test`)
-
-A handful of integration tests validate composed scaffolds end-to-end and
-need real binaries on `PATH`. Without them the tests fail with
-`spawn <bin> ENOENT`. `pnpm pretest` probes the env and prints install
-hints; the actual tests are strict (no auto-skip).
-
-| Tool | Needed for | Install |
-|---|---|---|
-| `forge` | `forge-contracts` family validation, `xlayer-foundry-deploy` / `layerzero-oft` / `account-abstraction` specs, `runPromptCorpus` multichain scenario, workspace benchmark | `curl -L https://foundry.paradigm.xyz \| bash && ~/.foundry/bin/foundryup` |
-| `cargo` | `solana-program` toolchain validation in workspace tests | `curl --proto "=https" --tlsv1.2 -sSf https://sh.rustup.rs \| sh` |
-
-After installing forge, ensure `~/.foundry/bin` is on your `PATH`
-(`foundryup` adds it to `~/.zshenv`/`~/.bashrc`; restart shell or
-`source` the rc file).
-
-## Routing
-
-Three layers, evaluated in order:
-
-1. **Product archetypes** — "Twitter clone" → fullstack-ts. 115+ known product patterns.
-2. **Keyword scoring** — Each family manifest declares tiered keywords. Highest match wins.
-3. **Fuzzy fallback** — Levenshtein distance ≤ 1 catches typos ("Ract" → "react").
-
-After family selection, **capability detection** scans the prompt against capability keywords and attaches matching layers.
-
-## Quality
-
-| Metric | Value |
-|--------|-------|
-| Route accuracy (training corpus, 60 scenarios) | 100% |
-| Route accuracy (held-out corpus, 43 scenarios) | 100% |
-| Route accuracy (IdeasAI corpus, 60 scenarios) | 100% |
-| Unit + integration tests | 615/615 |
-| Scaffold audit pass rate | 85/89 (4 toolchain-blocked) |
-| Compose latency (warm) | ~5ms |
-
-### Template regeneration pipeline
-
-The `src/training/template_v1/` pipeline rewrites scaffold template files from the convergent-patterns miner, guarded by a four-stage audit: **compose → install → typecheck → correctness**. The correctness stage catches classes of bug the TypeScript compiler can't: unused imports in the candidate file (since no family tsconfig enables `noUnusedLocals`), missing `<script src=...>` targets, and `document.getElementById('X')` calls with no matching HTML id. Any stage failing rejects the candidate before it can land.
-
-Run: `pnpm tsx src/training/template_v1/run.ts --template-key <file> --family <id> --template-target <path> --source-path <repo path> [--apply --yes]`
-
-## Install
-
-```bash
-npm install
-npm run build
-npm test
+prompt ──► planPrompt() ──► composeStarter() ──► files + build plan ──► agent builds
+            ~1 ms            ~5 ms
 ```
 
-Requires Node.js >= 20.
-
-## Adding families or capabilities
-
-1. Create `registry/families/{id}/manifest.json` or `registry/layers/capability/{id}/manifest.json`
-2. Add template files in `files/` subdirectory
-3. For rich UI layers: provide real `.tsx` components (not config stubs)
-4. For variants: add `variants/` subdirectory with alternative file sets + `"variants": [...]` in manifest
-5. Run `npm run sync:warm-list` to update the container warm cache
-6. Run `npm test` — the meta test enforces every capability has a coverage test
+1. **plan** — score the prompt against the family registry, attach capability/slot layers.
+2. **compose** — write the family template plus every layer's files, resolving variants deterministically from the project name.
+3. **build plan** — emit the concrete next steps (routes to create, components to build, APIs to wire) for the agent.
 
-## Integration
+Each stage is a CLI subcommand (`plan`, `compose`, `context`) and a library export, so you can stop at a spec, a file tree, or a full plan.
 
-starter-foundry powers the free-text scaffold path in blueprint-agent. When a user types a prompt, starter-foundry routes, composes, and provides the build plan.
-
-```typescript
-import { planPrompt, composeStarter } from 'starter-foundry'
-
-const plan = await planPrompt({ prompt: userMessage, partner })
-if (plan.kind === 'starter') {
-  const result = await composeStarter({ spec: plan.spec, outDir })
-}
-```
-
-**Integrating into a downstream agent runtime?** See **[docs/INTEGRATION.md](./docs/INTEGRATION.md)** — programmatic API, multi-family workspaces, the 4 telemetry events to emit, scrubbing rules, and how to consume the pipeline's rankings.
+## Registry
 
-## Buildout pipeline (agent-behavior → registry signal)
+The value is the registry — versioned scaffold families and composable layers:
 
-The `scripts/*-buildout*.mjs` pipeline mines Claude Code session transcripts of real agent buildouts on top of starter-foundry scaffolds and produces two ranked reports: **missing capabilities** (packages agents install because our router didn't attach the right layer) and **bad templates** (files agents rewrite within the first few turns).
+| | Count | What it is |
+|---|---|---|
+| Families | 94 | Base project types (`nextjs-ts`, `forge-contracts`, `solana-native-rust`, `python-http`, …) |
+| Capability layers | 104 | UI/feature overlays (`layout-dashboard`, `saas-teams`, `crypto-swap-ui`, `agent-rag`, …) |
+| Slot layers | 28 | Swappable infra: database, auth, payments, sdk, queue, industry |
+| Partner layers | 19 | Chain/protocol presets (Coinbase, EigenLayer, Solana, Tangle, …) |
+| Archetypes | 115+ | Prompt shorthands ("Twitter clone" → `fullstack-ts + realtime-ws + saas-teams`) |
 
-### Run it
+List the live registry instead of trusting a table that can go stale:
 
-```bash
-pnpm build
-node scripts/run-buildout-pipeline.mjs   # mine → join → analyze
+```sh
+npx @tangle-network/starter-foundry list                    # families + layers
+npx @tangle-network/starter-foundry select --prompt "..."   # what a prompt routes to
 ```
 
-Outputs:
-- `.evolve/buildout-analysis.json` — per-scenario pass rate, top-added packages, top-rewritten files (committed evidence)
-- `.evolve/capability-gaps.json` — ranked (scenario, capability) router misses
-- `.evolve/traces/buildouts.jsonl` — append-only corpus (gitignored, regenerable)
-
-### Stages
-
-| Script | Input | Output |
-|---|---|---|
-| `mine-buildout-sessions.mjs` | `~/.claude/projects/**/factory-local-phase2-*/*.jsonl` | `.evolve/traces/buildouts.jsonl` |
-| `join-buildout-outcomes.mjs` | VB execution traces + buildouts | buildouts.jsonl annotated with outcomes |
-| `analyze-buildouts.mjs` | joined buildouts | `.evolve/buildout-analysis.json` |
-| `infer-capability-gaps.mjs` | joined buildouts + `registry/package-to-capability.json` | `.evolve/capability-gaps.json` |
+## CLI
 
-### Fault tolerance
+| Command | Purpose |
+|---|---|
+| `compose-prompt --prompt <text> --out <dir>` | One shot: prompt → scaffold + build plan |
+| `plan --prompt <text>` | Route a prompt to a spec (family + layers) |
+| `select --prompt <text>` | Show the routing decision without composing |
+| `compose --spec <path> --out <dir>` | Compose a saved spec to disk |
+| `context --spec <path>` | Emit the agent build-plan context for a spec |
+| `validate --spec <path>` | Check a spec against the registry |
+| `list` | Print the live registry |
 
-- **Resumable**: per-session mtime stored in `.evolve/traces/.buildouts-miner-state.json`. Unchanged sessions skip; next run is ~0ms.
-- **Concurrent-safe**: O_EXCL lock file prevents simultaneous miner entry. Stale locks (PID not alive) auto-steal.
-- **Corruption-tolerant**: a malformed state file is logged and reseeded instead of crashing.
-- **Schema-versioned**: bumping `BUILDOUT_SCHEMA_VERSION` auto-rebuilds from source.
-- **Append-only output**: JSONL with per-row schema version; malformed lines are skipped by every consumer.
+`--help` lists the full set (mining, evaluation, workspace composition, release).
 
-### Adding a new source (GLM, GPT, etc.)
+## Library exports
 
-Write a new miner script (e.g., `mine-glm-sessions.mjs`) that emits rows conforming to `BuildoutEvent` in `src/lib/buildout-traces.ts` — same append-only JSONL, same schema version, different `sourceModel` value. The join + analyze stages consume it unchanged.
+`@tangle-network/starter-foundry` ships typed subpath exports: `/planner`, `/compose`, `/compose-prompt`, `/agent-context`, `/registry`, `/context`, `/build-plan`, `/industries`, `/workspace`, `/keywords`, `/types`.
 
-### Extending `registry/package-to-capability.json`
+## Documentation
 
-When an agent installs package X, we want our router to pre-attach the capability X maps to. Add an entry:
+- `docs/INTEGRATION.md` — embedding the engine in a product
+- `docs/cookbooks/` — end-to-end recipes
+- `docs/reference/` — family and capability reference
 
-```json
-"package-name": { "capability": "capability:foo", "confidence": 0.9 }
-```
+## License
 
-`tests/package-to-capability.test.ts` validates every capability ID against the live registry at build time.
+Licensed under either of **MIT** ([LICENSE-MIT](./LICENSE-MIT)) or **Apache-2.0** ([LICENSE-APACHE](./LICENSE-APACHE)) at your option.

package/corpus/template-family-mapping.json

@@ -50,7 +50,6 @@
   "agent-runtime-rust": "agent-service-rust",
   "agent-webapp": "fullstack-ts",
   "langgraph-multi-agent-python": "agent-service-py",
-  "langgraph-agent-platform-ts": "agent-service-ts",
   "mastra-agent-studio": "agent-service-ts",
   "openai-realtime-voice-agent": "agent-service-ts",
   "browser-automation-agent": "playwright-worker",