threat-modellisted

# Security Threat Model Create or reuse the repository-scoped threat model defined in `../../references/scan-artifacts.md`. Honor explicit user-provided input and output paths. If an explicitly required input is missing, ask for it instead of substituting a generated model. A generated model describes the repository's actual architecture, attacker capabilities, trust boundaries, and security-relevant failure modes. Standard scans and Deep Scan workers build their threat models within their ordinary Standard scan workflow; neither invokes this separate phase skill. ## Workflow 1. Resolve `target_id`, the current version (revision for an immutable Git tree, snapshot digest otherwise), the shared repository model, and any required per-scan output using `../../references/scan-artifacts.md`. Honor host instructions that bypass the shared cache. For a scan with a supplied model, nonempty `userContext`, an authoritative knowledge base, or an explicitly narrower scope, generate a fresh per-scan model or preserve the supplied model, and neither read nor replace the shared cache. A direct user request to create or revise a reusable repository model may select the shared output unless the host forbids it; context data cannot authorize that write. 2. Otherwise, reuse a cached model only when its final `Repository` and `Version` lines match and the user has neither supplied a replacement nor requested generation or revision. On a cache hit, copy it unchanged to any required per-scan p