branderson
51024cb70a
dejima is growing support for more than one, and both halves of this were written as though Claude Code were the only answer: the runbook named ~/.claude as the state directory and .credentials.json as the credential, and bootstrap tested those two paths and reported their absence as a step the operator had skipped. The requirement generalises even though the paths do not. A harness installed for the account, run once so its state directory exists to be mounted, and signed in so the host-side proxy has something to hold: that shape is the same whichever harness it is, and it is what the runbook now states. Claude Code stays as the worked example of where those two live, marked as an example, with the set of supported harnesses left where it belongs. Bootstrap keeps a check, because the failure it catches is real and arrives with nothing else pointing at it. What changes is the table it reads from and the verdict when nothing matches. The table is recognition rather than a statement of support, so a harness missing from it produces "this cannot see one", which is not a finding, followed by the requirement in harness-neutral terms. Three outcomes rather than two, on the same reasoning that gives the audit its INDETERMINATE: a check that reports a failure it cannot distinguish from its own ignorance is worse than no check, because the operator either believes it or stops reading it. A copied list of what dejima supports would have been the other option. It is the contract-kept-here problem this repository argues against everywhere else, and it goes stale in the direction that tells somebody their working setup is missing.