Stack Detection

Quick Guide: Read the evidence in front of you — manifests, lockfiles and framework configs, one pass per workspace — and map each library to an id from a catalog acquired at run time. Where the user names only what they want to build, offer candidate built-in stacks and wait for the pick. Load states come from the product's preload mapping, or lazy; an exclusive-category disagreement is surfaced, never resolved; whatever the payload cannot carry goes in the report. The output is a SeedPayload plus a report, published by the user through npx agents-inc share --stdin — the run writes, installs and posts nothing.

Detailed Resources:

• examples/core.md — a three-workspace monorepo walked end to end: traversal, mapping, an exclusive-category conflict, the payload and the report
• examples/intent.md — the same output reached from intent alone: candidates, the user's pick, and the gap the pick leaves
• reference.md — the SeedPayload contract, what each catalog route yields, payload defaults, report sections

Which path applies