Record approval for 4.1.3 Makefile and CI scope extension (#331)

[leynos]

Summary

Closes #331

Documentation-only change. Adds a Decision Log entry to docs/execplans/4-1-3-record-phase-1-scope-boundary-for-verus-and-stateright.md recording:

• the non-documentation changes PR Record Verus and Stateright phase-1 boundary (4.1.3) #311 introduced under the approval-gated plan (Makefile install-kani/kani-check/install-verus/verus targets with rust-prover-tools delegation, .github/workflows/ci.yml updates, deletion of scripts/install-kani.sh and scripts/check-kani-version.sh);
• why they were a necessary consequential extension (the recorded boundary names the Make targets as the supported Kani contract; the delegated install supersedes the 4.1.1 shell scripts);
• the approval decision: @leynos approved by reviewing and merging PR Record Verus and Stateright phase-1 boundary (4.1.3) #311 on 2026-06-02 — now on record per this issue;
• why no separate ExecPlan entry is warranted (the behaviour is covered by the plan's existing follow-up test decisions).

Validation

• make markdownlint — 0 errors
• make check-fmt — pass

🤖 Generated with Claude Code

Summary by Sourcery

Documentation:

• Add a decision log entry documenting rationale and formal approval for Makefile and CI scope extensions introduced by PR Record Verus and Stateright phase-1 boundary (4.1.3) #311 under the 4.1.3 plan.

[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: 16cb366c-f1ef-4f6d-a827-a5ddbb398d6d

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 issue-331-record-execplan-approval

---

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

[sourcery-ai]

Reviewer's Guide

Adds a new Decision Log entry to the 4.1.3 ExecPlan documenting and justifying previously shipped Makefile and CI scope extensions, including their approval and why no separate ExecPlan entry is needed.

File-Level Changes

Change	Details	Files
Document approval and rationale for Makefile and CI scope extension introduced by PR #311 within the 4.1.3 ExecPlan.	Add a new Decision entry describing the non-documentation changes in PR Record Verus and Stateright phase-1 boundary (4.1.3) #311 (new Makefile targets, CI workflow updates, script deletions) as part of the 4.1.3 scope boundary. Record rationale that these changes are a necessary consequential extension of the documented Kani/verus contract and replacement of prior 4.1.1 scripts. Document validation status, reviewer (leynos), approval date, and reference to issue Record explicit approval for Makefile and CI changes introduced under ExecPlan 4-1-3 #331, explicitly noting that no separate ExecPlan entry is required.	docs/execplans/4-1-3-record-phase-1-scope-boundary-for-verus-and-stateright.md

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#331	Update docs/execplans/4-1-3-record-phase-1-scope-boundary-for-verus-and-stateright.md to explicitly record that the Makefile and CI changes from PR #311 were a necessary consequential extension of the documentation work and to document who approved them and when.	✅
#331	Clarify in the ExecPlan how the Makefile/CI changes relate to existing roadmap items (e.g., 4.1.1 / 4.1.2), including how the new delegated install supersedes the prior shell scripts.	✅
#331	Decide and record whether a separate ExecPlan entry is warranted for these Makefile/CI changes, and document that decision in the ExecPlan.	✅

Possibly linked issues

• Record explicit approval for Makefile and CI changes introduced under ExecPlan 4-1-3 #331: They are the same: the PR updates the ExecPlan document to record the requested Makefile/CI approval.

---

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.