h-status

<!-- haft-contract-source: kernel_interface_catalog source_digest=sha256:26e174fdd87993d53721c925be9727239d77e8a425b7c52d28fd9f833b6d1153 --> # h-status — Read-only project memory Use the native Pi tool `haft_query` rather than shelling out manually. Contract truth: typed neighborhood and recall are **V9 CONTRACT** capabilities. Source, schema, skill, or local-test presence is not installed-runtime proof and does not establish Pi host parity. A readiness claim requires current **EXACT-CANDIDATE EVIDENCE** from P14 tied to one exact candidate; RC or release status additionally requires release authority. Pi support is experimental, and contract inclusion or evidence alone does not establish **CURRENT PRODUCT** status. If the operator's current question is not about project status, resumption, coverage, or reliance on recorded project state, return without calling this skill. Do not run status after completing unrelated work merely to backfill a governance-looking report. Start with: ```json { "action": "status", "full": false } ``` If status reports several canonical project scopes, retry the same read-only call with one exact `scope_id` from the reported available values: ```json { "action": "status", "full": false, "scope_id": "<exact emitted ScopeID>" } ``` Choose the scope from the operator's current object or question. Never select the first value, sort the values into a winner, or collapse mixed scopes. If the current use does not identify one scope, r...