fixed-income-credit-analysislisted

## Path Resolution See `dev/engine/agent-protocol.md` §1 — engine/ and templates/ paths resolve to the package root in both plugin-install and open-as-project modes. ## Invocation Protocol **Non-Negotiables (see AGENTS.md)**: no analysis without a Path Sheet · no numbers without a `doc §section` citation (`engine_undefined` otherwise) · no report outside `dev/templates/` · no delivery without a QA Verdict · no invented dimensions or vocabulary · follow the path's Playbook (`dev/engine/path-playbooks/<path_id>.md`). When this Skill is invoked: 1. **Path-sheet-driven (preferred).** If the user message carries a Path Sheet produced by the `credit-analysis-router` skill, read `dev/engine/path-playbooks/<path_id>.md` first, then the engine documents in the sheet's `engine_reading_order` order, and validate against its `quality_gates`. 2. **Explicit registered path_id.** If the user explicitly names a registered path (e.g., "run WP-RO-01"), treat that as the path selection: load the Playbook, then the core set — `dev/engine/engine-overview.md` + `dev/engine/dual-track-methodology.md` — plus any topic-specific doc the request names. 3. **No Path Sheet and no explicit path_id (strict).** If the request would produce a credit conclusion/rating/score, **STOP — do not analyze.** Route through the `credit-analysis-router` skill first, or ask the Q1–Q4 questions (role / object / depth / data) yourself to pick a path from `dev/engine/work-path-registry.md`. **Exception**: pure knowle