dev_kitlisted

# dev_kit — read the fork development contract The fork owns `.subfloor/dev-kit.json`. Subfloor validates the declaration, selects the invoking checkout and host/container seat, runs exact hook argv, and retains readiness evidence under `.sc-state/local/dev-kit/`. The engine does not infer project policy from manifests or install privileged host tools. ## Hook inventory The supported hook names are `deps`, `test`, `lint`, and `typecheck`: ```bash sc deps [args...] sc test [args...] sc lint [args...] sc typecheck [args...] ``` Read the declaration and its executable before running a hook. A configured hook reports the selected checkout, cwd, seat, executable, and child status. An absent hook is `unavailable`; do not reconstruct one from package metadata. ## Canonical states | State | Meaning | Supported recovery | |---|---|---| | `absent` | No declaration exists; engine-baseline tools remain mechanisms, not project policy. | Add a tracked declaration only when the fork needs one. | | `declared` | The declaration is valid; hook configuration is known, but execution/receipt evidence decides readiness. | Run the exact configured hook. | | `invalid` | Declaration, path, mount, image, or invocation validation failed. | Correct the named tracked input and retry. | | `ready` | The hook can execute on the active seat or the exact Docker receipt is current. | Continue. | | `failed` | A declared hook or provisioning attempt ran and failed. | Inspect retained logs/evidence; retry