Record Verus and Stateright phase-1 boundary (4.1.3)

[leynos]

Summary

• Implements roadmap item (4.1.3) by recording the phase-1 Verus and Stateright scope boundary.
• Updates docs/formal-verification-methods-in-netsuke.md to define Verus as optional and proof-kernel-only, with no phase-1 Cargo, Make, or CI surface.
• Updates docs/developers-guide.md with the contributor-facing support boundary: Kani is supported and gated, Verus is optional, and Stateright is deferred.
• Marks docs/roadmap.md item 4.1.3 and its subitems done.
• Keeps the implementation record in docs/execplans/4-1-3-record-phase-1-scope-boundary-for-verus-and-stateright.md.

Review Walkthrough

Start with docs/execplans/4-1-3-record-phase-1-scope-boundary-for-verus-and-stateright.md for the approved plan, implementation decisions, validation record, and scope notes. Then review docs/formal-verification-methods-in-netsuke.md for the normative phase-1 boundary and docs/developers-guide.md for contributor workflow guidance.

Validation

• make check-fmt
• make lint
• make test
• make markdownlint
• make nixie
• coderabbit review --agent completed twice during implementation with zero findings.

Notes

• This is documentation-only. No Rust code, Cargo manifests, Make targets, CI workflows, OrthoConfig surfaces, locale files, Verus files, or Stateright files were added.
• docs/users-guide.md remains unchanged because no user-facing behaviour changed.
• make fmt was attempted, but mdformat-all tried to rewrite unrelated Markdown files and then failed on pre-existing line-length findings outside this task. The formatter churn was restored, and all checking gates passed afterwards.

References

• Lody session: https://lody.ai/leynos/sessions/693be2b0-950d-4b69-a7cb-a1ca0a269025

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: a5f190ab-cbd5-4b3e-ae0c-588eb80e0415

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 4-1-3-record-phase-1-scope-boundary-for-verus-and-stateright

---

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

[sourcery-ai]

Reviewer's Guide

Adds a detailed, approval-gated ExecPlan document for roadmap item 4.1.3 that defines how to document and enforce the phase-1 boundary for Verus and Stateright, keeping them out of the mandatory tooling surface while preserving Kani as the only phase-1 formal verification gate.

File-Level Changes

Change	Details	Files
Introduce an approval-gated, documentation-first ExecPlan describing how to record the phase-1 Verus/Stateright boundary and its impact on tooling, scope, and workflow.	Create a new ExecPlan Markdown document outlining constraints, tolerances, risks, and validation strategy for roadmap item 4.1.3. Specify that implementation is documentation-only and must not introduce Verus/Stateright code, dependencies, or CI integration without explicit approval. Define the intended documentation updates for the formal-verification design doc, developers’ guide, and roadmap to capture Kani as the supported gate, Verus as optional proof-kernel-only, and Stateright as deferred with concrete re-entry criteria. Document a staged implementation sequence, including required validation commands, CodeRabbit review usage, and commit/pull-request conventions for the eventual implementation. Record current project state, discoveries about existing tooling and docs, and decisions justifying the plan’s scope and boundaries.	docs/execplans/4-1-3-record-phase-1-scope-boundary-for-verus-and-stateright.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.