chore: finalize Lock the Hashes milestone

[flyingrobots]

This PR finalizes the 'Lock the Hashes' milestone following the merge of PR #265. It updates the roadmap to reflect 'Verified' status with the correct merge timestamp and evidence links.

[coderabbitai]

Warning

Rate limit exceeded

@flyingrobots has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 8 minutes and 9 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Walkthrough

Documentation updates to the Lock the Hashes roadmap tracking completion of domain-separated hash contexts and benchmarks pipeline cleanup. Status fields transitioned from In Progress/Pending Review to Completed/Verified with updated evidence references linking PRs and audit timestamps.

Changes

Cohort / File(s)	Summary
Roadmap Documentation Updates docs/ROADMAP/lock-the-hashes/README.md, docs/ROADMAP/lock-the-hashes/benchmarks-cleanup.md	Status transitions from pending/in-progress to completed/verified; evidence references updated with PR links and verification timestamps (2026-02-13); Definition of Done marked as resolved with merged state indicators.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore: update CHANGELOG and finalize Lock the Hashes milestone #265: Directly modifies the same Lock the Hashes roadmap files with milestone/status updates and evidence linking.

Suggested labels

tooling

Poem

✅ The hashes locked tight, the work complete,
📋 Benchmarks verified in orderly sheet,
🔐 Domain-separated and documented with care,
⏰ 2026-02-13, marked everywhere!

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: finalizing the Lock the Hashes milestone by updating roadmap documentation.
Description check	✅ Passed	The description is directly related to the changeset, explaining the purpose of updating roadmap files to reflect verified status and merge information.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

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

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/domain-separation

---

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.}

[coderabbitai]

Actionable comments posted: 3

🤖 Fix all issues with AI agents

In `@docs/ROADMAP/lock-the-hashes/benchmarks-cleanup.md`:
- Line 34: The roadmap entry incorrectly marks the milestone closure as merged
inside PR `#266`; update the checklist in
docs/ROADMAP/lock-the-hashes/benchmarks-cleanup.md so the audit trail is
accurate by either leaving the DoD checkbox unchecked until PR `#266` is merged or
by adding a second checklist line that records PR `#266` as pending (e.g., keep
the existing "- [x] Code reviewed and merged (PR `#265`, merged
2026-02-13T05:45:06Z)" and add a "- [ ] Milestone documentation finalized (PR
`#266`, pending merge)" line) so PR `#265` and PR `#266` statuses are both
represented.

In `@docs/ROADMAP/lock-the-hashes/README.md`:
- Around line 23-26: The roadmap README uses both "Verified" and "Completed"
inconsistently (e.g., the milestone row shows "Verified" while feature rows like
domain-separated-hashes.md and benchmarks-cleanup.md show "Completed"); pick a
single taxonomy and apply it consistently (either change the milestone status to
"Completed" or change feature statuses to "Verified") and add a
STATUS_DEFINITIONS.md (or GLOSSARY.md) that defines the states (e.g., In
Progress → Completed → Verified → Archived) so future readers know the
hierarchy; update README.md table entries and any referenced feature files
(domain-separated-hashes.md, benchmarks-cleanup.md) to match the chosen
terminology.
- Line 9: Update the tense on the sentence referencing Hasher::new() so it
matches the milestone status "Verified" and the "Completed" feature flags:
change "currently use bare `Hasher::new()` without domain-separation prefixes"
to a past/historical phrasing (e.g., "used bare `Hasher::new()` without
domain-separation prefixes") or explicitly state it was the prior state and has
been fixed; ensure the line mentions the same identifiers (`state_root`,
`patch_digest`, `commit_id`, and the RenderGraph canonical bytes hash) so
readers can correlate the change with the resolved work.