v0.1.6

Full Changelog: v0.1.5...v0.1.6

Shall 0.1.5

• shall status says, per open criterion, whether the plan still holds a work item that can judge it. Every criterion row carries aims — pending while a work item aiming at it is not yet done or evidence on it awaits a verdict, spent when every work item aiming at it is done and it is still open, none when nothing aims at it — and a spent aim carries its own sentence under the row, naming the finished work items: evidence is filed only under a work log addressing a work item that targets the criterion, so nothing left in the plan can reach a verdict on it. The Vitals page and the report say the same word beside each open criterion. shall check and shall board are unchanged: a spent aim is no red, and the board stays two lists.
• An aim is a promise of a verdict. /shall:plan now aims a work item only at criteria whose evaluation process can be run, whole, once its definition of done holds — on what the item and its waits supply — and cuts the acceptance pass in stage 1 when only the assembled whole can run a process, instead of aiming module work at criteria it can never judge; a definition of done may name what another item builds only when the item waits on it. /shall:work reads the targeted processes at the look back and says what supplies each thing they name, reports the spent aims the status found as a fifth reading of the survey, and writes a spent aim up as one finding rather than a paragraph per turn.

Shall 0.1.4

• shall works from inside Codex's sandbox without anybody editing a config. shall init --agent codex writes network_access = true and a writable_roots naming Shall's home into the project's own .codex/config.toml — merged into what is there, never over a line a person set. And the CLI no longer mistakes a daemon it may not signal for a dead one: from inside a sandbox it adopts the running daemon when it answers, and otherwise says which process it is and why it cannot be reached, instead of trying to stop it and failing on rm ~/.shall/daemon.json with a sentence about nothing.

Shall 0.1.3

• The board keeps a work item off the Implement list while its report is judged. A completion report puts the item in_review until a person closes it or refuses the report; a work log alone leaves it ready, so a turn that stopped part-way is carried on rather than begun again. shall status and the Spec plane wear the new word.
• shall context --work-item <id> — the look back before a turn: the files to open, computed by the daemon — the module's siblings and their logs, the reports, findings and every decision whose lines reach them, the criteria with their closure, the newest turns in the feed's order, and what finishing the item would let start. /shall:work reads it before stop 1, holds the code to the module's contracts and re-runs the closed criteria on the way back, and routes a person's rejection of a spec node to the process that owns its band.
• A guard hook before the tool runs. guard-paths.mjs joins the compile hook in every kit: a write under .shall/ledger/, or the removal of a file under .shall/spec/ — named outright, in a patch, or in a shell line — is refused with one sentence before it happens. Claude keeps its deny rule as well; Codex gets its first mechanical wall. shall init says when a project's AGENTS.md is past the 32 KiB Codex reads by default.

v0.1.2

Full Changelog: v0.1.1...v0.1.2

v0.1.1

• shall report, and a Generate report button on the spec plane: the whole spec assembled into static HTML under the project's own shall/report/, for a reader who never opens Shall. Seven chapters of tables built from the graph and the ledgers, a page per node carrying its relations and its body verbatim, and a progress chapter of four bars — scenarios, requirements, criteria, work items — each leading to its full listing. Status is said in plain words (Approved, Awaiting review, Met, Blocked…), the figures are the Vitals' own, links work from disk with no server, and every page prints. The folder ignores itself in git; regeneration replaces it whole; nothing is ever written into .shall/.
• The help screen says shall [--host] on one line — one command, one line.
• SHALL_HOME relocates Shall's home folder. Nothing an installed Shall runs sets it; the checkout's dev scripts do, which keeps developing Shall entirely off the installed Shall's ~/.shall.

Full Changelog: v0.1.0...v0.1.1

v0.1.0

Full Changelog: https://github.com/Nove-Lab/Shall/commits/v0.1.0