Release v1.1.1: dorian init starter is load-bearing (golden path now blocks)

[ajaysurya1221]

Summary

Follow-up to v1.1.0. Makes the dorian init starter claim load-bearing, so the golden path demonstrates the gate it advertises. No breaking changes — a single scaffold default; warrant format, checker grammar, exit codes, and trust semantics are unchanged.

Why

The v1.1.0 public-install smoke test (install from PyPI → init → verify → break → revalidate) revealed the starter claim was load_bearing: false, so a broken starter promise folded to DEGRADED (exit 3) — which the scaffolded fail_on: revoked Action does not block on. So a first-time user's first broken promise silently shipped — the opposite of the headline. Now the starter is load-bearing in both branches (config-value and the path: fallback): a break folds to REVOKED (exit 4) and the default Action blocks the PR. This also matches the scaffolded note, which already said "load-bearing facts."

Changes

• src/dorian/init.py — starter claim load_bearing: true in both _starter branches.
• tests/test_init.py — +2 tests: starter is load-bearing (both branches), and end-to-end break → REVOKED → exit 4.
• Version 1.1.0 → 1.1.1 (pyproject, __init__, README latest: + action refs, action/README.md, BENCHMARK_CURRENT stamp).
• Corrected a residual overclaim in BENCHMARK_CURRENT.md (the … 2.py dups were untracked local artifacts — never tracked or shipped, not "accidentally-packaged").
• README init section now states the blocking behavior; new CHANGELOG entry + docs/releases/v1.1.1.md.

What dorian is / is not

Verifies explicit, checkable claims with deterministic, token-free checks; re-checks across PRs. Not a runtime control plane, MCP gateway, sandbox, or proof of arbitrary correctness. --deny-exec/--deny-shell and checker_trust: base are fail-closed policies, not sandboxes. One documented real catch (encode/httpx) — not broad validation.

Tests & verification

• uv run pytest — 885 passed
• uv run ruff check + ruff format --check — clean
• uv build + twine check — wheel + sdist PASS, no … 2.py, 33 modules
• Adversarial review of the diff — caught a real incomplete-fix bug (only one of the two load_bearing branches had flipped); fixed + covered before this PR.

Security

No change to the security boundary. dorian init still writes files only (no execution, repo-confined, atomic, --force/--dry-run/--json); the starter remains a read-only C3 checker. Already-sealed warrants are unaffected.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Changed

  • dorian init starter claims are now load-bearing; breaking sealed claims results in exit code 4 (REVOKED) and blocks PRs via default GitHub Actions settings.

• Documentation

  • Updated getting started guide and action examples to reflect load-bearing claim behavior; version references bumped to v1.1.1.

• Tests

  • Added tests verifying starter claim load-bearing status and end-to-end validation of golden-path PR blocking.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 24bc916f-a4c9-4f96-a8b4-66558edd79fb

📥 Commits

Reviewing files that changed from the base of the PR and between a27b540 and af7c95f.

📒 Files selected for processing (9)

• CHANGELOG.md
• README.md
• action/README.md
• docs/BENCHMARK_CURRENT.md
• docs/releases/v1.1.1.md
• pyproject.toml
• src/dorian/__init__.py
• src/dorian/init.py
• tests/test_init.py

---

📝 Walkthrough

Walkthrough

Version bump to 1.1.1. The _starter() function in dorian init changes load_bearing from False to True for both claim branches, so a broken sealed fact now folds to REVOKED (exit 4) instead of DEGRADED (exit 3). Two new tests and one integration test validate this contract. All version references and documentation are updated accordingly.

Changes

v1.1.1 Golden-path polish

Layer / File(s)	Summary
Load-bearing starter claim change and tests src/dorian/init.py, tests/test_init.py	_starter() sets load_bearing=True in both the pyproject-derived and path-existence claim branches. The test suite adds a load_bearing assertion to the existing path-fallback test, a new unit test confirming the seeded-repo starter claim is load-bearing, and an end-to-end integration test that seals a warrant, breaks the claim by renaming the package, and asserts dorian revalidate exits with code 4 and REVOKED output.
Version bump and documentation updates pyproject.toml, src/dorian/__init__.py, CHANGELOG.md, docs/releases/v1.1.1.md, README.md, action/README.md, docs/BENCHMARK_CURRENT.md	Package version incremented from 1.1.0 to 1.1.1 in pyproject.toml and __init__.py. CHANGELOG adds the v1.1.1 entry. Release notes, README Getting Started, benchmark stamp, and all three action/README example snippets are updated to reference v1.1.1 and describe the load-bearing/REVOKED blocking behavior.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• ajaysurya1221/dorian#15: Introduced src/dorian/init.py and the dorian init golden-path scaffolding that this PR directly modifies by setting load_bearing=True in _starter().

Poem

🐇 A claim once soft now stands its ground,
With load_bearing: True the gate is sound!
Break the seal and exit four you'll see,
REVOKED the warrant — no PR goes free.
The rabbit stamps v1.1.1 with cheer,
The golden path is blocking, crystal clear! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: it identifies the specific modification (dorian init starter is load-bearing) and its primary consequence (golden path now blocks), matching the core purpose of the release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v1.1.1-golden-path-blocks

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}