chore(release): v0.7.0 — adopt first, enforce when the numbers say so

[ericlovold]

What

The v0.7.0 cut — version bump + the /truthsync drain folded in, so version and tag move together and the public story catches up to the ships. Diff is package.json + changelog + roadmap only.

The pack since v0.6.0 → surface mapping

Merge	Changelog	Roadmap
pay-per-crawl sanctionedFetch (#183)	✅ had entry	mandate-authority slice noted
@sanction/sdk publish-ready (#169)	✅ had entry	Next
Sanction Local install package (#168, #184)	✅ had entry	→ shipped phrasing
Observe mode (#187) + digest/subtree rollup (#192)	＋ new entry	＋ added to Now (shipped)
Email-lands-on-the-decision (#190)	＋ new entry	—
Demo companies (#186), consulting page (#170–188), skills (#185/#189/#191)	— infra/site/tooling, no product entry by design	—

Every claim in the new entries verified against code, not the draft: Observe grounded in the OBS-1/OBS-2 traceability rows; email entry confirmed against approveUrlFor(id) → /dashboard/approvals?review=<id>.

Isolation

Fresh branch off main; touches only the three truth-surface files. Does not touch the concurrent MCP-demo session's work — the one shared file class (changelog/roadmap) is the only collision surface, and this is a single short-lived PR to minimize it.

Verification

npm run check green — tsc + eslint + 903 tests, 0 errors.

After merge

I'll hand over the v0.7.0 release notes + a prefilled publish link (target=main), same as v0.6.0 — you publish, I verify Latest.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UEw1RdHk5bmphKxr6N5mJY

---

Generated by Claude Code

Summary by CodeRabbit

• Documentation

  • Added release notes for version 0.7.0.
  • Documented observe mode for previewing enforcement outcomes.
  • Documented approval email links that open directly to the relevant decision.
  • Updated the roadmap to reflect current, upcoming, and future priorities.
  • Expanded details about the install package, no-egress policy packs, and signed audit exports.

• Release

  • Bumped the product version to 0.7.0.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
sanction	Ready	Preview, Comment	Jul 12, 2026 9:02pm

[coderabbitai]

📝 Walkthrough

Walkthrough

The package version is bumped to 0.7.0, three changelog entries are added, and roadmap text is updated to reflect current shipped and upcoming scope, including Sanction Local installation, no-egress behavior, and signed audit evidence exports.

Changes

Release documentation

Layer / File(s)	Summary
Version and changelog entries package.json, lib/changelog.ts	The package version changes to 0.7.0, and release, observe-mode, and approval deep-link entries are prepended to CHANGELOG.
Roadmap scope and shipped details lib/roadmap.ts	The Now/Next/Later narrative and Sanction Local note are updated with current distribution, installation, no-egress, and audit evidence details.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• ericlovold/sanction#125: Updates related Sanction Local roadmap and changelog content.
• ericlovold/sanction#167: Overlaps on changelog updates and a package version bump.
• ericlovold/sanction#168: Updates related Sanction Local, no-egress, audit export, and release narrative content.

🚥 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 matches the release bump and highlights the main changelog theme for v0.7.0.
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.

✨ 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 claude/cut-v0.7.0

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@lib/roadmap.ts`:
- Around line 22-23: Remove the Markdown bold markers from the plain-text notes
in the “Adopt without flipping the switch” and “Sanction Local: from runtime to
install” roadmap entries, keeping the note wording unchanged. Do not alter the
rendering path.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c899b997-bab1-4df7-acd0-ec644742b4c9

📥 Commits

Reviewing files that changed from the base of the PR and between d5f4e10 and 229c779.

📒 Files selected for processing (3)

• lib/changelog.ts
• lib/roadmap.ts
• package.json

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Avoid Markdown syntax in plain-text roadmap notes.

app/roadmap/page.tsx renders RoadmapItem.note directly in a <p>, so **observe mode** and **no-egress** will appear with literal asterisks. Remove the markers or render the note through the shared Markdown component.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@lib/roadmap.ts` around lines 22 - 23, Remove the Markdown bold markers from
the plain-text notes in the “Adopt without flipping the switch” and “Sanction
Local: from runtime to install” roadmap entries, keeping the note wording
unchanged. Do not alter the rendering path.