Legacy codebase workflows

Use the workflow that serves the request. Investigation is the default; documentation, startup repair, tests and modernization are optional. A broken build does not turn an investigation into a repair task.

Start with direct search for a known path or symbol; no setup or saved map is needed. For an unfamiliar subsystem, use one native scoped map and original source. For several modules or repeated difficult questions, follow scale and intake: lazy catalogs, one task map and evidence-based optional pilots. Large size alone does not require retrieval. The bundled tools are bounded and have not been validated on a hundreds-of-megabytes production corpus.

First use: setup and saved reports

Use the native Rust mapper legacy-repo-map for repository maps by default. A normal skill installation includes its setup script, pinned policy, source, queries and notices, not executables. Verify local readiness first; downloading a prebuilt program needs no Rust compiler or Python parser packages. Read binary delivery only for platform limits or publishing details.

Native setup contract: tool-distribution.json pins legacy-tools-v0.3.0 from EdukeyTeam/agent-toolbox and names the Windows x86-64, Linux x86-64 and macOS ARM64 archives. WSL uses the Linux archive. First run:

python /path/to/skill/scripts/setup_native.py status

If it returns ready, use the returned program path. For needs-setup, follow next_action: install and run python /path/to/skill/scripts/setup_native.py install; this local cache result does not imply the pinned release is unavailable. The installer selects and verifies the pinned prebuilt platform release without a Rust compiler, including when an older policy has publication or consumer-verification labels. If status reports an invalid cached package, inspect the reason and use explicit --replace. If the pinned release is unavailable, follow the explicit reviewed CI/local-package route in native setup. Do not search “latest,” build Rust implicitly, or substitute an old 0.1.0 artifact. Use the Python fallback only when native installation/execution is unavailable, the OS is unsupported or policy blocks it, or exact reference behavior is required.

Do not write machine-specific "ready" or "to do" state into this installed SKILL.md. The setup script revalidates the machine-local receipt, package hashes and binary version before reporting readiness. Native remains experimental: grammar/query coverage and consumer execution limits still apply; see native tooling when comparing behavior.