codebase-contextlisted

# Codebase Context — Agent Instructions ## Invocation - `/codebase-context <IDEA_ID>` Where: - `IDEA_REF = $ARGUMENTS` (single token; no spaces) If missing, STOP. --- ## Resolve IDEA_ID (required) Before using any paths: - Call `vf.resolve_idea_id` with `idea_ref = $ARGUMENTS` - Store returned `idea_id` as `IDEA_ID` - Use `IDEA_ID` for all paths and YAML headers --- ## Goal Produce a lightweight, durable “map” of the existing codebase relevant to this idea, focusing on: - where to extend vs create - major boundaries (API layer, core logic, models/state, UI, tests) - any constraints/invariants implied by the current architecture This is NOT a full survey and NOT a task list. It is an early anchor to prevent greenfield assumptions. --- ## Canonical paths (repo-relative) Idea root: - `docs/forge/ideas/<IDEA_ID>/` Inputs (required): - `docs/forge/ideas/<IDEA_ID>/latest/concept_summary.md` - `docs/forge/ideas/<IDEA_ID>/inputs/concept_summary_config.md` Fallback/optional: - `docs/forge/ideas/<IDEA_ID>/latest/idea_normalized.md` - `docs/forge/ideas/<IDEA_ID>/inputs/idea.md` Outputs: - `docs/forge/ideas/<IDEA_ID>/latest/codebase_context.md` - Run snapshot: - `docs/forge/ideas/<IDEA_ID>/runs/<RUN_ID>/outputs/codebase_context.md` Logs: - `docs/forge/ideas/<IDEA_ID>/run_log.md` --- ## Method (generic, repo-aware) 1) Read the concept summary (primary semantic anchor). 2) Identify which kinds of components are likely involved: - API endpoints / controllers / route