jlxq0/jmap-mcp
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases 1 Packages 1 Wiki Activity Actions

docs: use documentation-range addresses in the deployment notes #34

Merged
jlxq0 merged 1 commit from docs/documentation-range-addresses into main 2026-09-01 15:34:38 +00:00
Conversation 0 Commits 1 Files changed 2 +13 -10
jlxq0 commented 2026-09-01 15:31:44 +00:00
Owner
Copy link

Doc comments and AGENTS.md only. No code, no behaviour, no test values.

Substituted addresses are from RFC 5737 documentation range and are the same width as what they replace, so the port table stays aligned. They do not collide with the X-Forwarded-For fixtures already in src/last_used.rs and src/config.rs tests.

The house LAN address is described rather than substituted. The stale local filesystem path in AGENTS.md is replaced by the repository name and the path within it.

Every measurement, timing and conclusion is unchanged: the port table, the BGP-versus-L2 explanation, and why a laptop on the wifi has no route. Each argues which address is reachable from where, which a documentation address carries identically. One line was added saying the two are stand-ins, so a reader does not try to reach them.

Correcting forward. No history rewrite.

Gate

On 1.93.0 read from ci.yml, through build-slot.sh: fmt rc=0, clippy -D warnings rc=0, test rc=0, 187 passed.

Doc comments and `AGENTS.md` only. No code, no behaviour, no test values. Substituted addresses are from RFC 5737 documentation range and are the same width as what they replace, so the port table stays aligned. They do not collide with the `X-Forwarded-For` fixtures already in `src/last_used.rs` and `src/config.rs` tests. The house LAN address is described rather than substituted. The stale local filesystem path in `AGENTS.md` is replaced by the repository name and the path within it. Every measurement, timing and conclusion is unchanged: the port table, the BGP-versus-L2 explanation, and why a laptop on the wifi has no route. Each argues which address is reachable from where, which a documentation address carries identically. One line was added saying the two are stand-ins, so a reader does not try to reach them. Correcting forward. No history rewrite. ## Gate On `1.93.0` read from `ci.yml`, through `build-slot.sh`: `fmt` rc=0, `clippy -D warnings` rc=0, `test` rc=0, 187 passed.
docs: use documentation-range addresses in the deployment notes
Some checks failed
CI / tag-ancestry (pull_request) Successful in 3s
Details
CI / cargo (pull_request) Successful in 1m54s
Details
CI / docker (pull_request) Failing after 2m23s
Details
9e34fb2d1c
 
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
jlxq0 merged commit 7ad8954216 into main 2026-09-01 15:34:38 +00:00
jlxq0 deleted branch docs/documentation-range-addresses 2026-09-01 15:34:38 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
waiting-on-julian
Blocked on Julian. The ask is in the issue.

No labels
waiting-on-julian
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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
jlxq0/jmap-mcp!34
No description provided.