docs(docs): prune dangling refs to retired docs/testing/mutation.md (PR #054c)#2072
Conversation
Markdown link checker CI на PR #2066 валив на 3 broken internal links до `docs/testing/mutation.md` — файл був видалений у PR #052b (commit `a97b8cc8` — 'chore(web): retire cloudSync Stryker mutation infra') разом з cloudSync v1 Stryker infra, але caller-doc-и не оновили. Це той самий клас Hard Rule #15 violation, що цей PR системно фіксить — додаю ці 3 refs до scope-у. - `docs/testing/README.md`: знесена row "mutation.md" з таблиці Документи; додана note про deletion + actual current testing layers (vitest + Playwright + Argos) у Тестові-шари таблиці нижче. - `docs/audits/2026-05-03-web-deep-dive/round-13-burndown-sprint.md`: 3 inline mention-и (lines 12, 35, 193) переведено у backtick-без-лінка форму з historical context. Audit doc сам помічений як 'Superseded — для історії', тож для нього такий refactoring найкоректніший. Verify: `pnpm lint:governance-sync` все ще 0 errors. Co-Authored-By: dmytro.s.stakhov <dmytro.s.stakhov@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Rate limit exceeded
To continue reviewing without waiting, purchase usage credits in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughDocumentation updates remove outdated mutation testing references following the removal of mutation.md, update round-13 KPI closure dates, and clarify current testing strategies (Vitest, Playwright, Argos). ChangesDocumentation Updates & Mutation Testing Cleanup
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested labels
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
⏱️ CI Pipeline Duration ReportBased on the last 50 successful runs on the default branch. Overall Pipeline
Trend (last 20 runs): Per-Job Breakdown
|
Summary
Stage 7 (cleanup) of SQLite storage migration — sub-PR #054c.
PR #2066 (
#054b,merged як
997ad6e2+ac2cc5c8) фіксив 12 dangling cloudSync v1source refs та bidirectional ADR-0004 ↔ ADR-0047 supersede edge.
Markdown link checker вже валив на трьох інших dangling refs до
docs/testing/mutation.md— файл був видалений у PR #052b разом зcloudSync v1 Stryker mutation infra (commit
a97b8cc8—chore(web): retire cloudSync Stryker mutation infra), але caller-doc-ине оновили. Це той самий клас Hard Rule #15 violation, тому додаю його
у Stage 7 cleanup chain окремим focused PR-ом.
Що саме змінено
docs/testing/README.md:замінено row
[mutation.md](./mutation.md)у Документи-таблиці наісторичну note про deletion в #052b — Stryker mutation infra
retired разом з cloudSync v1; current scope обмежено vitest unit +
Playwright E2E + Argos visual layers (див. таблицю Тестові-шари
нижче).
docs/audits/2026-05-03-web-deep-dive/round-13-burndown-sprint.md:3 inline mention-и
mutation.md(lines 12, 35, 193) переведеноу backtick-без-лінка форму з PR #052b context. Audit doc сам
помічений як «Superseded — для історії», тож для нього такий
refactoring найкоректніший.
Чому окремим PR-ом, а не у #2066
PR #2066 був landed (merge to main) до того, як я встиг push цей
3-line fix після того, як CI на ньому показав markdown-link-check
failure. Замість force-push у вже merge-нутий PR — окремий focused
follow-up.
Governing Skill
.devin/skills/storage-roadmap-stage-7-cleanup— Stage 7 sub-PRsequencing rules (один PR = один semantic chunk, governance-sync
зелений до merge, ADR graph bidirectional, no
--no-verify).Playbook
.devin/playbooks/sqlite-migration-stage-7— Stage 7 cleanup playbook(burndown allowlist + prune dangling refs).
Verification
Локально:
pnpm lint:governance-sync→ 0 errors (199 pre-existingwarnings, не у scope-і Stage 7).
заміни читаються природно у контексті.
CI на commit
9b4a58f3:Migration lint, Playbook trigger index, Secret scan, Workflow lint,
check-freshness, freeze-warn, size, tsconfig strict guard, Pipeline
duration p95, Vercel Preview Comments — 17/28 PASS.
19777fc3має ADR-0049 файл (docs/adr/0049-auth-vendor-risk.md,landed у
edd482ed) без відповідного row уdocs/adr/README.md.Fix-forward у окремому PR
#2073 — після
його merge ADR graph CI на цьому PR теж стане зеленим (rebase від
main).
https://instatus.com/(404) уdocs/launch/business/04-launch-readiness.md:313. Не в scope-іstorage migration (status-page benchmark reference). Owner: Dev
(per file context).
regression (Argos),
checkaggregate — pre-existing failuresна main
19777fc3, не введені doc-only diff цим PR.Docs and Governance
Risk and Rollout
Risk: very low — pure docs prune. Single rollout step: merge →
main pulls latest doc snapshot. Rollback:
git revert <sha>.No DB / no schema / no API impact.
Suggested merge order:
Hard Rule #15
docs/testing/mutation.mdreflected у doc references)🤖 Generated with Devin
Co-Authored-By: Devin <devin-ai-integration[bot]@users.noreply.github.com>