[PR #6368] [MERGED] docs(limits): describe how to design admission recovery #7314

Closed
opened 2026-11-01 21:46:57 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6368
Author: @morluto
Created: 10/22/2026
Status: ✅ Merged
Merged: 10/22/2026
Merged by: @morluto

Base: main ← Head: cursor/limits-recovery-docs-fcfc


📝 Commits (7)

  • d98f604 fix(reconstruction): dedupe residual unknown ids with uniqueSorted
  • d32e73d docs(limits): describe how to design admission recovery
  • bad9421 fix(hopper): pass distribution readers into install-host tests
  • ec7c42b docs(limits): name the parser doctor shares with startup
  • 94caf0d test: align pcap, storage, and regex fixtures with current contracts
  • 7e48678 chore: merge current main into admission recovery docs
  • d2761c8 docs: link repository experiments outside the built site

📊 Changes

14 files changed (+179 additions, -14 deletions)

View changed files

📝 .agents/skills/reverse-engineer-anything/SKILL.md (+3 -2)
📝 .agents/skills/reverse-engineer-anything/references/connection-and-recovery.md (+31 -0)
📝 CONTRIBUTING.md (+2 -0)
📝 docs/.vitepress/config.ts (+4 -0)
📝 docs/apktool-resource-analysis.md (+1 -1)
➕ docs/design/limits-and-recovery.md (+124 -0)
📝 docs/go-binaries.md (+1 -1)
📝 docs/index.md (+2 -1)
📝 docs/jeb-analysis.md (+1 -1)
📝 docs/testing.md (+1 -1)
📝 docs/tool-design.md (+3 -1)
📝 docs/verification/electron-cancellation-2026-10-16.md (+1 -1)
📝 docs/verification/javascript-retained-facts-2026-10-15.md (+2 -2)
📝 docs/verification/javascript-window-options-2026-10-16.md (+3 -3)

📄 Description

Summary

Part of #6176; related to #5910. Add a contributor guide for admission ceilings, configurable headroom and recovery, with examples from regex deadlines and MCP response budgets. Link it from the contribution guide, docs index, tool-design guide and sidebar. Mirror the recovery ladder into the authored investigation skill.

Merged main 42e1a17d6. Earlier compilation and fixture repairs in this branch are now on main through #4642 and #6375; conflict resolution retains main's current tests, including structured deadline diagnostics and exact search recovery. The PR diff contains documentation and authored-skill changes only. Repository experiment links in seven existing pages now point to their GitHub files at pinned commit 42e1a17d6, including three script links affected by the same site-root mismatch. All ten targets were verified at that commit. No production behavior or target authority changes; a maintainer scope decision is not applicable.

Validation

On Node 24.18.0, recovery-message tests passed (3 tests), npm run docs:check passed (including 9 README consistency tests), and npm run check:ci:fast passed all five tasks, including formatting, typecheck and built lint.

After correcting the repository artifact links, npm run docs:build passes, including page rendering and its dead-link check. npm run docs:check and formatting of all seven corrected pages also pass. Hosted checks are pending; real-provider workflows and the separate website link audit were not run.

Author readiness

Human owner: @morluto

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/6368 **Author:** [@morluto](https://github.com/morluto) **Created:** 10/22/2026 **Status:** ✅ Merged **Merged:** 10/22/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `cursor/limits-recovery-docs-fcfc` --- ### 📝 Commits (7) - [`d98f604`](https://github.com/morluto/rea/commit/d98f6042221b524ff4af48641ca6f44a2afc5f99) fix(reconstruction): dedupe residual unknown ids with uniqueSorted - [`d32e73d`](https://github.com/morluto/rea/commit/d32e73dc505414ac5f80a20b1b108eb8075e1ffb) docs(limits): describe how to design admission recovery - [`bad9421`](https://github.com/morluto/rea/commit/bad942172e4117ad2363f3f7afbca35646c9c5ee) fix(hopper): pass distribution readers into install-host tests - [`ec7c42b`](https://github.com/morluto/rea/commit/ec7c42b0b83f463b6a2eb65bca2a09c2f86b5617) docs(limits): name the parser doctor shares with startup - [`94caf0d`](https://github.com/morluto/rea/commit/94caf0d31e8a1f46a2c13d188d5d2d6eb0e8354c) test: align pcap, storage, and regex fixtures with current contracts - [`7e48678`](https://github.com/morluto/rea/commit/7e48678ce20030a7448a2b27a0aa333e23e9cc3f) chore: merge current main into admission recovery docs - [`d2761c8`](https://github.com/morluto/rea/commit/d2761c850e8fd385558a377ad46f4d8164fe2e0f) docs: link repository experiments outside the built site ### 📊 Changes **14 files changed** (+179 additions, -14 deletions) <details> <summary>View changed files</summary> 📝 `.agents/skills/reverse-engineer-anything/SKILL.md` (+3 -2) 📝 `.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md` (+31 -0) 📝 `CONTRIBUTING.md` (+2 -0) 📝 `docs/.vitepress/config.ts` (+4 -0) 📝 `docs/apktool-resource-analysis.md` (+1 -1) ➕ `docs/design/limits-and-recovery.md` (+124 -0) 📝 `docs/go-binaries.md` (+1 -1) 📝 `docs/index.md` (+2 -1) 📝 `docs/jeb-analysis.md` (+1 -1) 📝 `docs/testing.md` (+1 -1) 📝 `docs/tool-design.md` (+3 -1) 📝 `docs/verification/electron-cancellation-2026-10-16.md` (+1 -1) 📝 `docs/verification/javascript-retained-facts-2026-10-15.md` (+2 -2) 📝 `docs/verification/javascript-window-options-2026-10-16.md` (+3 -3) </details> ### 📄 Description ## Summary Part of #6176; related to #5910. Add a contributor guide for admission ceilings, configurable headroom and recovery, with examples from regex deadlines and MCP response budgets. Link it from the contribution guide, docs index, tool-design guide and sidebar. Mirror the recovery ladder into the authored investigation skill. Merged main `42e1a17d6`. Earlier compilation and fixture repairs in this branch are now on main through #4642 and #6375; conflict resolution retains main's current tests, including structured deadline diagnostics and exact search recovery. The PR diff contains documentation and authored-skill changes only. Repository experiment links in seven existing pages now point to their GitHub files at pinned commit `42e1a17d6`, including three script links affected by the same site-root mismatch. All ten targets were verified at that commit. No production behavior or target authority changes; a maintainer scope decision is not applicable. ## Validation On Node 24.18.0, recovery-message tests passed (3 tests), `npm run docs:check` passed (including 9 README consistency tests), and `npm run check:ci:fast` passed all five tasks, including formatting, typecheck and built lint. After correcting the repository artifact links, `npm run docs:build` passes, including page rendering and its dead-link check. `npm run docs:check` and formatting of all seven corrected pages also pass. Hosted checks are pending; real-provider workflows and the separate website link audit were not run. ## Author readiness Human owner: @morluto - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:46:57 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#7314
No description provided.