workspace-fitlisted

# Workspace Fit Audit only the repository evidence available locally. Do not treat the audit as permission to install, start, migrate, build, or modify anything. ## Safety boundary - Keep the audit read-only. Do not create, edit, delete, stage, or commit files. - Do not run setup scripts, package managers, builds, tests, migrations, containers, databases, servers, watchers, or other project commands. - Do not make network requests or invoke external services. - Do not read secret values, `.env` files, credential stores, key files, or untracked private data. It is enough to note that a documented secret or service dependency exists. - Prefer repository search and file reads. If shell inspection is necessary, use only read-only commands such as `pwd`, `git status --short`, `git ls-files`, `find`, `ls`, `file`, `sed`, `rg`, and `git grep`. - Report uncertainty instead of inferring facts that the repository does not support. ## Audit workflow 1. Read the repository orientation and development instructions first, including `CLAUDE.md`, `README`, contribution guidance, and nested agent instructions when present. 2. Inspect tracked manifests, lockfiles, development scripts, container configuration, CI workflows, and documentation. Do not inspect dependency trees or generated build output. 3. Collect evidence for each decision factor: - Can a clean clone restore dependencies from committed manifests and lockfiles? - Are required tools and setup steps explicit