squad-kit 0.1.0 → 0.2.0

package/CHANGELOG.md

@@ -0,0 +1,105 @@
+# Changelog
+
+All notable changes to this project are documented here.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.2.0] - 2026-04-22
+
+### tracker-intake-fetch
+
+**Added**
+
+- `squad new-story --id <ID>` auto-fetches title, description, labels, and attachments (≤ 10 MB each) from the configured tracker. Supported: Jira Cloud, Azure DevOps Services.
+- `.squad/secrets.yaml` as a second credential source (after environment variables) for planner keys and tracker tokens. Created with mode `0600` on POSIX; auto-added to `.gitignore`.
+- `squad init` now prompts for tracker credentials when a supported tracker is chosen, and offers to save the planner key inline as an alternative to exporting an env var.
+- `squad status` shows tracker type, workspace, and credential source (`env` / `secrets.yaml` / `missing`).
+- `squad new-story` flags: `--no-fetch`, `--no-attachments`, `--attachment-mb <n>`.
+- `squad new-story --no-tracker` — skip tracker id and fetch for a single story in a workspace that normally requires tracker ids. Interactive mode now offers "skip tracker for this story" alongside "enter id" when required.
+
+**Changed**
+
+- `squad new-story` accepts the feature slug as an optional positional; prompts when it is omitted in a TTY (including a picker for existing feature folders). Passing `-y` / `--yes` keeps fail-fast behaviour when the slug is missing. `CI=1` forces non-interactive mode even in a TTY.
+- `squad tracker link` accepts both the story path and the tracker id as optional positionals; prompts with a story picker and id input when omitted. `-y` / `--yes` and `CI=1` force non-interactive fail-fast.
+- CLI-wide: commands treat missing required input as promptable in a TTY; `-y` / `--yes` and `CI=1` opt out.
+- Credential resolution order documented: env var → `.squad/secrets.yaml` → prompt → fail. Applies to both planner and tracker credentials.
+
+**Security**
+
+- `.squad/config.yaml` continues to reject secret-shaped keys (`apiKey`, `token`, …). Secrets live in `.squad/secrets.yaml` only.
+- Auto-managed `.gitignore` block covers `.squad/secrets.yaml`, `.squad/stories/**/attachments/`, and `.squad/.trash/`.
+
+### Added
+
+- `squad config` command group with `show`, `set planner`, `set tracker`, `unset planner`, `unset tracker`, and `remove-credential <section>` subcommands. Every field in `.squad/config.yaml` and `.squad/secrets.yaml` can now be edited interactively without opening a text editor.
+- `squad init` on an existing workspace now offers **Reconfigure planner / Reconfigure tracker / Overwrite / Cancel** instead of silently bailing. `--force` keeps the old overwrite behaviour for scripts.
+
+- `squad upgrade` self-update command. Detects the package manager used to install squad-kit, fetches the latest version from npm, and runs the appropriate global-install command after confirmation. Refuses dev installs and major version bumps (print-manual-guide instead).
+- `squad migrate` command applies one-shot 0.1.x → 0.2.0 structural migrations (delete legacy prompts, gitignore, secrets perms, planner budget defaults, config normalisation). Idempotent; destructive by design; gated behind a confirmation prompt unless `--yes` is passed.
+- `squad doctor` command: a full health check covering planner config, tracker credentials, model list probes (no completion calls), `.gitignore` managed block, `secrets.yaml` permissions, legacy `.squad/prompts/`, and `.squad/` layout. `--fix` applies non-destructive repairs only; destructive fixes belong in `squad migrate`.
+- `planner.modelOverride` (per-provider) lets you pin a different plan-phase model id without editing squad-kit source.
+- `pnpm verify:models` (`scripts/verify-models.ts`) probes provider model list APIs before publish so pinned ids cannot drift unnoticed.
+- Clear, actionable error when the planner model returns 404 (upgrade, config override, or `squad doctor`).
+- `squad status` marks the planner row with `(override)` when `modelOverride` is active for the current provider.
+- Direct planner API (optional): Anthropic, OpenAI, Google. Squad calls the planner for you and writes the plan file.
+- Demand-driven context: planner reads files on request via a bounded budget (file count, bytes, wall-clock).
+- Interactive picker in `squad new-plan` over un-planned intakes.
+- Already-planned guard with `--yes` override.
+- `--api`, `--copy`, `--feature`, `--all` flags on `new-plan`.
+- `squad init` asks about planner setup; `--planner <provider>` for non-interactive.
+- `squad status` shows planner provider, model, and env-var presence.
+- `squad list` shows which plans were generated by the API vs copy-paste.
+- Visual identity: mint-green brand, custom spinner frames, banner, summary boxes, consistent prefixes across all commands.
+- `squad rm` command group: `rm story`, `rm plan`, `rm feature`, each with `--dry-run`, `--trash`, `-y`, and interactive pickers. Deleting a story cascades to the matching plan file and overview row. `.squad/.trash/<timestamp>/` is now git-ignored automatically.
+
+### Changed
+
+- Every user-facing error now ends with a recommended next command (for example, `Run \`squad doctor\` to diagnose`). Failures no longer dead-end users at an error string.
+- `ensureGitignore` now includes `.squad/.trash/` in the managed block. Existing users will see the line appended on the next `squad doctor --fix` or any command that calls `ensureGitignore`.
+- Anthropic plan model pinned to the versioned Claude API id `claude-opus-4-7` (replacing the prior alias default) and execute remains dated `claude-haiku-4-5-20251001`, per Anthropic’s model overview — run `pnpm verify:models` after changes.
+- `new-plan <intake>` is now optional; omit to pick interactively.
+- `--no-copy` renamed to `--no-clipboard` (old flag removed). `--copy` now forces copy-paste mode.
+- Prompts (`generate-plan.md`, `intake.md`, `story-skeleton.md`) now ship entirely within the squad-kit package. Fresh installs no longer create a `.squad/prompts/` directory. Stale `.squad/prompts/` from 0.1.x installs is ignored at runtime and cleaned up by `squad migrate`.
+
+### Breaking changes for 0.1.x users
+
+- 0.1.x users who upgrade should run `squad migrate` once per repo. A `.squad/prompts/` folder left from 0.1.x is deleted outright (prompts are now bundled in the squad-kit package).
+- If you customised `.squad/prompts/*.md`, those customisations are no longer used. The canonical prompts are in the installed squad-kit package. To customise, fork squad-kit and patch `templates/prompts/`. (This is intentional: behaviour was inconsistent before — some commands ignored the user copy — and silent version drift was breaking workflows.)
+
+### Security
+
+- Config loader rejects any YAML entry whose key looks like `apiKey`, `token`, `secret`, or `credential`.
+
+### Known limitations
+
+- OpenAI and Google planner model ids in squad-kit remain provider “latest”-style names for 0.2.0; dated snapshots for those providers are planned for 0.2.1 once verified.
+
+### Non-goals (still deferred)
+
+- OpenAI-compatible generic endpoint (OpenRouter, Ollama, local). Targeted for 0.3.
+- `squad implement` command. Targeted for 0.3.
+- MCP server, telemetry.
+
+## [0.1.0] - 2026-04-21
+
+First public release.
+
+### Added
+
+- `squad init` — scaffolds `.squad/` with `config.yaml`, prompt templates, and agent slash commands.
+- `squad new-story <feature-slug>` — creates `.squad/stories/<feature>/<id>/intake.md` with `attachments/`.
+- `squad new-plan <intake-path>` — composes the plan-generation meta-prompt inline with the intake, prints to stdout, and copies to clipboard.
+- `squad status` — reports story / plan counts and next global `NN`.
+- `squad list [--feature <slug>]` — table of stories and their plan state.
+- `squad tracker link <story> <id>` — upserts a tracker id on an existing intake.
+- Agent slash-command templates for **Claude Code**, **Cursor**, **GitHub Copilot**, and **Gemini CLI**.
+- Tracker id validators for **GitHub**, **Linear**, **Jira**, and **Azure DevOps** (no API calls; format validation only).
+- Plan-generation meta-prompt (`generate-plan.md`), intake template (`intake.md`), and plan skeleton reference (`story-skeleton.md`).
+- Documentation: `docs/philosophy.md`, `docs/getting-started.md`, `docs/customization.md`, `docs/vs-spec-kit.md`.
+
+[Unreleased]: https://github.com/AzmSquad/squad-kit/compare/v0.2.0...HEAD
+[0.2.0]: https://github.com/AzmSquad/squad-kit/compare/v0.1.0...v0.2.0
+[0.1.0]: https://github.com/AzmSquad/squad-kit/releases/tag/v0.1.0

package/README.md

@@ -1,16 +1,25 @@
 # squad-kit
 
+[![npm version](https://img.shields.io/npm/v/squad-kit.svg)](https://www.npmjs.com/package/squad-kit)
+[![CI](https://github.com/AzmSquad/Squad-Kit/actions/workflows/ci.yml/badge.svg)](https://github.com/AzmSquad/Squad-Kit/actions/workflows/ci.yml)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
+[![Website](https://img.shields.io/badge/site-squad--kit.netlify.app-7cffa0?labelColor=0a0a0c)](https://squad-kit.netlify.app)
+
 **Plan once, execute cheap.** A 3-step SDD-style workflow CLI for AI-assisted coding: **raw story → good plan → implementation**.
 
+Website & docs: **[squad-kit.netlify.app](https://squad-kit.netlify.app)**
+
+
 Your expensive model plans once. A cheap model executes many times. Squad-kit owns the folder conventions, the plan meta-prompt, and the agent slash-commands so the token cost goes where it pays off.
 
 ```
 .squad/
-├── prompts/                # meta-prompts you can edit
 ├── stories/<feature>/<id>/ # intake + attachments (one per story)
 └── plans/<feature>/        # NN-story-<slug>.md (one per executable plan)
 ```
 
+Plan meta-prompts (`generate-plan.md`, `story-skeleton.md`, intake template) are **bundled inside the squad-kit npm package**, not copied into your repo. Upgrade the CLI to change them; to fork and customise, patch `templates/prompts/` in a fork of squad-kit.
+
 ---
 
 ## Why not Spec-Kit?
@@ -19,11 +28,11 @@ Both aim at spec-driven development. They make different bets.
 
 | | squad-kit | Spec-Kit |
 |---|---|---|
-| Commands | `init`, `new-story`, `new-plan`, `status`, `list`, `tracker link` | `constitution`, `specify`, `clarify`, `plan`, `tasks`, `analyze`, `checklist`, `implement` |
+| Commands | `init`, `new-story`, `new-plan`, `status`, `doctor`, `migrate`, `upgrade`, `list`, `rm`, `tracker link` | `constitution`, `specify`, `clarify`, `plan`, `tasks`, `analyze`, `checklist`, `implement` |
 | `/implement` turn starts with | one plan file (~5–15 KB) | 5–7 command templates + cross-artifact reads (~15–25 KB) |
 | Model-tier awareness | Built into the philosophy (planner ≠ executor) | Not prescribed |
 | Generated artifacts per story | `intake.md`, `NN-story-<slug>.md`, overview row | `spec.md`, `plan.md`, `data-model.md`, `contracts/`, `research.md`, `quickstart.md`, `tasks.md` |
-| Customization | Prompts live in your repo as plain Markdown. Edit freely. | Template override stack with presets/extensions |
+| Customization | Prompts ship with the CLI (fork squad-kit to change them). | Template override stack with presets/extensions |
 | Runtime | Node + TypeScript, npm-distributable | Python + `uv` |
 | Scope | Intentionally small | Broad, with safety nets (`clarify`, `analyze`) |
 
@@ -31,14 +40,24 @@ Spec-Kit ships safety rails. Squad-kit ships the cheap path and gets out of the
 
 See [`docs/philosophy.md`](docs/philosophy.md) for the token math and [`docs/vs-spec-kit.md`](docs/vs-spec-kit.md) for the full comparison.
 
+### Tracker auto-fetch (new in 0.2.0)
+
+When a supported tracker is configured, `squad new-story <feature> --id <ID>` pulls the work item's title, description, labels, and attachments (≤ 10 MB each) directly into the intake. No more manual copy-paste.
+
+Supported trackers in 0.2.0: **Jira Cloud**, **Azure DevOps Services**.
+
+Credentials are prompted during `squad init` and stored in `.squad/secrets.yaml`, which squad-kit auto-adds to your `.gitignore`. Environment variables (`JIRA_API_TOKEN`, `AZURE_DEVOPS_PAT`, or the cross-provider `SQUAD_TRACKER_API_KEY`) also work if you prefer them.
+
+Pass `--no-fetch` to skip the call and scaffold an empty intake; `--no-attachments` to fetch metadata only.
+
 ---
 
 ## Install
 
 ```bash
-npm install -g squad-kit
+npm install -g squad-kit@0.2.0
 # or
-pnpm add -g squad-kit
+pnpm add -g squad-kit@0.2.0
 ```
 
 Requires Node 18+.
@@ -54,6 +73,33 @@ squad init                        # interactive: tracker, agents, name
 squad new-story auth --title "SSO support"
 # → edit .squad/stories/auth/sso-support/intake.md (paste title, description, criteria)
 
+# Write an intake without a tracker id (even when naming.includeTrackerId would normally require one):
+squad new-story feature-slug --no-tracker --title "quick exploration"
+# Per-invocation only — .squad/config.yaml is not modified.
+```
+
+### Managing configuration
+
+squad-kit stores settings in two files:
+
+- `.squad/config.yaml` — project name, tracker type, naming rules, planner provider.
+- `.squad/secrets.yaml` — API keys and tokens, `.gitignore`-d and chmod 0600.
+
+Never edit these by hand. Use:
+
+| Command | What it does |
+| --- | --- |
+| `squad config show` | Detailed view of both files (secrets masked). |
+| `squad config set planner` | Interactively change provider, model, and key. |
+| `squad config set tracker` | Interactively change tracker type, host, token. |
+| `squad config unset planner` | Disable the direct planner; keeps credentials. |
+| `squad config unset tracker` | Set tracker to `none`; keeps credentials. |
+| `squad config remove-credential planner` | Delete planner keys without touching config. |
+| `squad config remove-credential tracker` | Delete tracker keys without touching config. |
+| `squad status` | Quick operational summary (stories, plans). |
+| `squad doctor` | Full health check. |
+
+```bash
 # then, in your agent (Claude Code / Cursor / Copilot / Gemini):
 /squad-plan .squad/stories/auth/sso-support/intake.md
 
@@ -75,12 +121,99 @@ squad new-plan .squad/stories/auth/sso-support/intake.md   # prints to stdout, c
 
 | Command | What it does |
 |---|---|
-| `squad init` | Bootstrap `.squad/` with prompts, config, and agent slash-commands |
-| `squad new-story <feature> [--id ID] [--title ...]` | Scaffold a story intake folder |
+| `squad init` | Bootstrap `.squad/` with config and agent slash-commands (prompts are bundled in the package) |
+| `squad new-story [feature] [--id ID] [--title ...]` | Scaffold a story intake folder (optional feature prompts in a TTY) |
 | `squad new-plan <intake-path>` | Compose the plan-generation meta-prompt with the intake inlined; print to stdout + copy to clipboard |
-| `squad status` | Count stories/plans, show next global `NN`, warn on duplicates |
+| `squad status` | Count stories/plans, show next global `NN`, tracker/planner credential hints, warn on duplicates |
+| `squad doctor` | Run a health check on your `.squad/` workspace |
+| `squad doctor --fix` | Apply non-destructive repairs (`.gitignore` block, `secrets.yaml` mode `0600`, missing dirs) |
+| `squad doctor --json` | Emit results as JSON on stdout (for scripting) |
 | `squad list [--feature <slug>]` | Table of stories + their plan state |
-| `squad tracker link <story> <id>` | Attach or update a tracker id on an intake |
+| `squad rm` | Delete stories, plans, or whole features (`rm story` / `rm plan` / `rm feature`) with `--dry-run`, `--trash`, `-y` |
+| `squad tracker link [story] [id]` | Attach or update a tracker id on an intake (optional args prompt in a TTY) |
+| `squad migrate` | One-shot structural migrations from 0.1.x to 0.2.0 |
+| `squad migrate --dry-run` | Show what would change without applying |
+| `squad migrate --yes` | Skip the confirmation prompt |
+| `squad upgrade` | Check npm for a newer squad-kit release and install it |
+| `squad upgrade --check` | Only check; do not install |
+| `squad upgrade --yes` | Skip the confirmation prompt |
+
+### Removing things safely
+
+squad-kit never asks you to `rm -rf` by hand. Use:
+
+| Command | What it does |
+| --- | --- |
+| `squad rm story` | Interactive picker; deletes intake + plan + overview row. |
+| `squad rm story <path\|id>` | Same, targeted. |
+| `squad rm plan` | Interactive picker; deletes the plan file only. |
+| `squad rm feature` | Interactive picker; deletes every story + plan + overview. |
+| `... --dry-run` | Preview without changing anything. |
+| `... --trash` | Move into `.squad/.trash/<ts>/` instead of deleting. |
+| `... -y` | Skip the confirmation prompt (non-interactive). |
+
+`.squad/.trash/` is git-ignored automatically. Recover with `mv .squad/.trash/<ts>/<item> .squad/...`. Empty it when you are sure: `rm -rf .squad/.trash`.
+
+### `squad upgrade`
+
+`squad upgrade` queries `registry.npmjs.org` for the latest squad-kit release, detects your package manager (pnpm, npm, yarn, bun), and runs the appropriate global-install command with your confirmation. After upgrading, run `squad migrate` in each project to update the `.squad/` structure if needed.
+
+### `squad doctor`
+
+Use this when something feels misconfigured. By default it is read-only: it loads `.squad/config.yaml` and `.squad/secrets.yaml`, checks directory layout, warns if a legacy `.squad/prompts/` directory is still present (removed in 0.2.0), validates planner settings and API keys (including a lightweight `/v1/models` probe — never a paid completion), checks Jira/Azure tracker config and credentials, and optionally hits a small REST endpoint to verify connectivity.
+
+`--fix` only performs safe, idempotent fixes: creating missing `.squad/stories` or `.squad/plans`, appending the managed `.gitignore` block (including `.squad/.trash/` when missing), and tightening `secrets.yaml` permissions on POSIX. It does not delete files or rewrite config; for legacy prompts cleanup and other migrations, use `squad migrate`.
+
+### Upgrading from 0.1.x
+
+After upgrading the squad-kit package (`pnpm add -g squad-kit@latest`), run `squad migrate` once in each repo that uses squad-kit. This deletes the now-unused `.squad/prompts/` directory, ensures your `.gitignore` has the squad-kit block, tightens permissions on `.squad/secrets.yaml`, and normalises `.squad/config.yaml` formatting. Comments inside `config.yaml` will be dropped.
+
+---
+
+## CLI conventions
+
+### Interactive-first
+
+Every squad-kit command prompts for missing required input when run in a TTY. Use `-y` or `--yes` to opt out — missing input then fails fast instead of prompting. Useful in scripts and CI, e.g. `CI=1 squad new-story user-auth --id ENG-42 --yes`.
+
+Set `CI=1` to force non-interactive behaviour even in a TTY (matches how other tools behave in CI environments).
+
+## Direct planner (optional)
+
+Squad can call a strong planning model for you from the terminal so you do not have to paste the prompt into your agent. Off by default.
+
+1. `squad init --force` and answer **yes** to *Enable automatic plan generation?* (or re-run `squad init -y --planner anthropic`). Use `--skip-secrets-prompt` (or `--no-prompt-secrets`) if you want to skip all secret prompts in a TTY session.
+2. Export the provider's API key:
+
+   ```bash
+   export ANTHROPIC_API_KEY=...   # or OPENAI_API_KEY / GOOGLE_API_KEY
+   ```
+
+3. `squad new-plan` — pick an un-planned intake; squad reads only the files the planner asks for (bounded by `planner.budget`), writes the plan to `.squad/plans/<feature>/NN-story-<slug>.md`, and prints a summary.
+
+Optional: override the default plan-phase model id (per provider) without changing squad-kit:
+
+```yaml
+planner:
+  enabled: true
+  provider: anthropic
+  # Optional: pin a specific model for the plan phase, overriding the squad-kit default.
+  # Useful when riding a newer provider release ahead of a squad-kit update, or when the
+  # default has been deprecated.
+  modelOverride:
+    anthropic: claude-opus-5-0
+```
+
+Slash commands inside your agent (`/squad-plan`) continue to work unchanged — the agent already has your repo in scope.
+
+Squad-kit never reads API keys from `.squad/config.yaml`. You can set keys via environment variables, save them in `.squad/secrets.yaml` (prompted by `squad init` when the planner is enabled), or a mix. See [Secrets](#secrets) below.
+
+#### Secrets
+
+- `.squad/config.yaml` — shape and non-sensitive settings. Safe to commit.
+- `.squad/secrets.yaml` — API tokens for the planner and tracker. **Always git-ignored** (managed by squad-kit).
+- Environment variables override `.squad/secrets.yaml`.
+- Priority: env var → `.squad/secrets.yaml` → prompt (interactive) → fail.
 
 ---
 
@@ -109,22 +242,19 @@ naming:
   globalSequence: true
 ```
 
-`--id` on `new-story` is validated against the tracker's id format (e.g. `ENG-42` for Linear, `843806` for Azure). No API calls in v0.1.
+`--id` on `new-story` is validated against the tracker's id format. For **Jira** and **Azure DevOps**, with credentials configured, the CLI can [auto-fetch](#tracker-auto-fetch-new-in-020) issue metadata and attachments. Other trackers (GitHub, Linear) use id format validation only in v0.2.
 
 ---
 
-## What's *not* in v0.1
+## What's *not* in v0.2
 
 We ship lean on purpose. Current non-goals:
 
-- Direct Anthropic/OpenAI API invocation (cost stays with your agent subscription)
+- OpenAI-compatible generic endpoint (local models, OpenRouter, etc.); [Direct planner (optional)](#direct-planner-optional) covers hosted Anthropic, OpenAI, and Google
 - MCP server
 - `/clarify`, `/analyze`, constitution-equivalent
-- Tracker API calls (id validation only)
 - Telemetry
 
-Open to revisiting these for v0.2 based on usage.
-
 ---
 
 ## Tradeoffs to know

package/SECURITY.md

@@ -0,0 +1,57 @@
+# Security Policy
+
+## Supported versions
+
+Only the latest minor release of squad-kit receives security fixes.
+
+| Version | Supported |
+| ------- | --------- |
+| 0.2.x   | ✅        |
+| 0.1.x   | ❌        |
+| < 0.1   | ❌        |
+
+## Reporting a vulnerability
+
+**Please do not open a public GitHub issue for security reports.**
+
+Email the maintainer privately at **momenysr@gmail.com** with:
+
+- A description of the issue and its impact.
+- Steps to reproduce (proof-of-concept preferred).
+- Affected version(s) and environment (OS, Node version).
+- Any suggested mitigation, if you have one.
+
+You can expect:
+
+1. **Acknowledgement** within 72 hours.
+2. **Initial assessment** within 7 days.
+3. **Fix + coordinated disclosure** as quickly as the severity warrants — typically a patch release within 14 days for high-severity issues.
+
+Credit will be given in the release notes unless you prefer to remain anonymous.
+
+## Handling credentials
+
+squad-kit reads API tokens from (in order):
+
+1. **Environment variables** — `ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, `GOOGLE_API_KEY`, `SQUAD_PLANNER_API_KEY` for planner; `JIRA_API_TOKEN`, `AZURE_DEVOPS_PAT`, `SQUAD_TRACKER_API_KEY` for trackers.
+2. **`.squad/secrets.yaml`** — created with mode `0600` on POSIX; always included in `.gitignore` by `squad init`.
+3. **Interactive prompt** — when the terminal is a TTY and the command needs a credential that is missing.
+
+### Non-goals
+
+- `.squad/config.yaml` must never contain secrets. Loading it with a key matching `apiKey`, `api_key`, `token`, `secret`, `credential`, or `credentials` raises a loud error.
+- squad-kit does not integrate with OS keychains in 0.2.0. The secrets file model is intentional: it is inspectable, excluded by ignore rules, and portable.
+- Credentials are never logged. Tracker error messages redact tokens; planner provider errors do the same.
+
+## Scope
+
+squad-kit is a local-only CLI. It can call **optional** network APIs (tracker fetch, direct planner) when the user enables those flows and provides credentials. It does not execute user code. Reports in scope include:
+
+- Arbitrary file read/write outside the workspace caused by malformed input (e.g. path-traversal via feature slugs or intake paths).
+- Command injection via clipboard helpers or spawned processes.
+- Supply-chain concerns in shipped dependencies (`@inquirer/prompts`, `commander`, `fs-extra`, `js-yaml`, `kleur`).
+
+Out of scope:
+
+- Content of user-authored intakes and plans under `.squad/stories/` and `.squad/plans/` (treat as trusted project input to your agents).
+- Vulnerabilities in the AI agents that consume squad-kit output (Claude Code, Cursor, Copilot, Gemini). Report those upstream.