assertledger 1.2.0 → 1.3.1

package/docs/reference.md

@@ -14,6 +14,9 @@ For a first run, use `assertledger doctor .` and the [Git qualification guide](g
 ```sh
 assertledger init . --dry-run --json
 assertledger init . --json
+assertledger setup . --client codex --dry-run --json
+assertledger setup . --client codex --write --json
+assertledger demo --allow-unsafe-execution --json
 assertledger audit . --json
 assertledger analyze . --json
 assertledger schema verification-request --json

package/docs/repository-init.md

@@ -11,6 +11,20 @@ assertledger init . --json
 assertledger audit . --json
 ```
 
+To initialize and install a project-local read-only agent connection through one preflight, use:
+
+```sh
+assertledger setup . --client codex --dry-run --json
+assertledger setup . --client codex --write --json
+```
+
+`setup` previews by default. It composes the existing `init` and `connect` checks and refuses the
+whole operation before its first managed-file write if either side is blocked or conflicting. Use
+`--client claude-code` for Claude Code. It does not authorize execution, reload a client, or prove
+repository behavior. If a new connection conflict appears after init, rollback removes only regular
+init files created by this setup call whose bytes still equal the plan. A regenerated or changed
+file is preserved and reported under `PARTIAL_FAILURE` with exit code 5.
+
 The dry run emits the exact canonical bytes and SHA-256 digests that a subsequent write plans to
 use. Writes use a same-directory temporary file followed by an atomic rename. A second run returns
 `UNCHANGED` without rewriting matching files. A missing lock or a stale, structurally valid lock
@@ -43,6 +57,14 @@ replaces the configured one, so a different declaration never silently widens or
 inventory: it fails closed, for example with `CONFIG_CONFLICT`, or with
 `UNSUPPORTED_REPOSITORY_SYMLINK` when a narrower list exposes a link again. Links outside the declared names stay fail-closed.
 
+When `analyze` refuses a link, the stable `UNSUPPORTED_REPOSITORY_SYMLINK` line stays first and the
+exit code stays 4. The CLI then prints `Link detail: "<path>"`, the first link found, followed by
+the catalogue guidance; the MCP `assertledger_analyze` error carries the same lines. The path is a
+quoted JSON string with every character outside printable ASCII escaped and long names truncated,
+because a file name is repository content. Only the first link is named, so declare its entry and
+run again to meet the next one. `analyze` itself takes no `--exclude`: the declaration goes through
+`init`, which needs a detected package manager.
+
 The configured list governs only these static diagnostics and the evidence digests of
 `assertledger.lock.json`; it produces no campaign evidence. `audit`, a campaign's repository copy and
 its manifest `repositoryDigest` keep their own exclusions: the defaults, plus the verification

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "assertledger",
-  "version": "1.2.0",
+  "version": "1.3.1",
   "description": "Verify that regression tests detect a declared bug, with deterministic verdicts and replayable evidence.",
   "type": "module",
   "private": false,