v0.0.5
Read-only commands are now position-independent.
check, status and phase-check resolved conductor state relative to the working directory, so they only worked from the conductor root - from inside a shard they threw no manifest at shards/<name>/.sharding/manifest.yaml instead of returning the CLI's JSON contract. They now find the workspace from wherever the session is.
- Inside a shard, the shard boundary takes precedence over the ancestor search, so a shard holding its own
.sharding/cannot redefine which graph it is measured against. checkwith no argument checks the shard the session is inside; an explicit name still wins over it.- Outside a shard with no name,
checkreportschecked: falsewith a reason rather than throwing. /shard-ackno longer has to warn shard sessions away from/shard-check- a shard can confirm it is structurally clean before acknowledging.
This changes where a command may run, not what a shard may do: these paths are read-only, and writes remain governed by the isolation hook.
87 tests (was 75).