docs: record jedit evidence replay audit

[flyingrobots]

Summary

• record the current jedit witness evidence/replay audit in Echo's v0.1.0 jedit slice plan
• clarify that jedit currently reports inline observation evidence plus missing_retention
• clarify that durable_replay_unavailable is honest obstruction, not release-gate success

Validation

• git diff --check
• pnpm exec markdownlint-cli2 docs/design/v0.1.0-jedit-next-ten-slices.md
• cargo xtask lint-dead-refs --file docs/design/v0.1.0-jedit-next-ten-slices.md

[coderabbitai]

Warning

Review limit reached

@flyingrobots, we couldn't start this review because you've used your available PR reviews for now.

Your plan currently allows 1 review/hour. Refill in 1 minute and 1 second.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more review capacity refills, 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 trial, open-source, and free plans. In all cases, review capacity refills continuously over time.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 254bd905-42cd-41c5-9c17-84d0cc8312f8

📥 Commits

Reviewing files that changed from the base of the PR and between 4768ddc and 21f322a.

📒 Files selected for processing (1)

• docs/design/v0.1.0-jedit-next-ten-slices.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch stack/jedit-release-gate-evidence-replay

---

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

[flyingrobots]

@codex Self-review findings from local Code Lawyer pass:

Severity	File	Lines	Issue	Recommended mitigation
None	docs/design/v0.1.0-jedit-next-ten-slices.md	94-128, 180-183	No issue found. The docs-only patch accurately records the jedit evidence/replay audit without claiming durable retained refs or replay success, and it preserves the no-app-nouns constraint.	No change recommended.

Validation observed during this pass: git diff --check, markdownlint for the touched doc, and cargo xtask lint-dead-refs --file docs/design/v0.1.0-jedit-next-ten-slices.md had already passed on this branch.

[chatgpt-codex-connector]

Summary

• Reviewed the trigger and PR context: the self-review explicitly reports no issues and recommends no change.
• Verified working tree state locally and found an unrelated dirty file (pnpm-lock.yaml), then restored it to keep the branch clean.
• No code or docs changes were required for this follow-up, so I did not create a commit and did not open a follow-up PR via make_pr (per your rule that make_pr must only be called after a real commit).

Commands run

• ✅ cd /workspace/echo && find .. -name AGENTS.md -print
• ✅ cd /workspace/echo && git status --short && git log -n 5 --oneline
• ✅ cd /workspace/echo && git diff -- pnpm-lock.yaml | sed -n '1,160p'
• ✅ cd /workspace/echo && git restore pnpm-lock.yaml && git status --short

Testing

• ✅ git status --short (clean after restore)

View task →