docs: sync remaining ASSUMPTIONS.md drift (MAX_ENDPOINTS, HEAP refs, intro)#2
Merged
Merged
Conversation
…intro) What: second ASSUMPTIONS.md doc-sync batch after HD-01 (629414e). Four edits: - MAX_ENDPOINTS row: value 32 -> 64 and ref :22 -> :35. The const is `pub const MAX_ENDPOINTS: usize = 64` at src/ipc/mod.rs:35 (bumped 32 -> 64 at A-v.d.3 in lockstep with MAX_CAPS_PER_PROCESS). Also corrected the stale ">32 endpoints" replace-trigger -> ">64" so it tracks the current cap. - HEAP_SIZE ref :175 -> :386; HEAP_PAGES ref :178 -> :389 (src/process.rs). - Intro paragraph: stale "MAX_VMAS = 64" -> "MAX_VMAS = 256" (the table row already reads 256; only the prose example lagged). Why: §8 doc-sync hygiene. ASSUMPTIONS.md is the canonical numeric-bound catalog per Convention 8; its values and source line refs must resolve and be current. Out of scope (follow-up): the "Per-endpoint message queue" row still computes "32 x 16 x 280 B" off the old endpoint count. Left out pending a check of the actual pre-allocation factor against src/ipc/mod.rs rather than assuming 64x. Verification: make check-assumptions clean (307 baseline, 0 new); confirmed src/ipc/mod.rs:35 = MAX_ENDPOINTS 64, src/process.rs:386/:389 = HEAP_SIZE/HEAP_PAGES; diff is 4 line edits in one file. Staged files: docs/ASSUMPTIONS.md Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Second ASSUMPTIONS.md doc-sync batch (after #1 / HD-01), and the first PR opened end-to-end by the
cambios-agent[bot]identity: branch -> sign -> push -> PR -> auto-merge on green, all as a non-admin App that cannot bypass the gate.What (4 edits, one file):
MAX_ENDPOINTSrow: value32 -> 64, ref:22 -> :35(const ispub const MAX_ENDPOINTS: usize = 64at src/ipc/mod.rs:35), and the stale>32replace-trigger ->>64.HEAP_SIZEref:175 -> :386;HEAP_PAGESref:178 -> :389(src/process.rs).MAX_VMAS = 64->256(the table row already read 256).Why: §8 doc-sync hygiene - ASSUMPTIONS.md is the canonical numeric-bound catalog per Convention 8; values and source line refs must resolve and be current.
Out of scope (follow-up): the "Per-endpoint message queue" row still computes
32 x 16 x 280 Boff the old endpoint count - left pending a check of the actual pre-allocation factor against src/ipc/mod.rs.Verification:
make check-assumptionsclean (307 baseline, 0 new); line targets reconfirmed against src; 4-line diff in one file.🤖 Generated with Claude Code