Skip to content

Split doc/media into per-document folders (v2.2.4 / v2.3 draft) - #76

Closed
M0LTE wants to merge 1 commit into
rename-v23-draftfrom
split-media
Closed

M0LTE wants to merge 1 commit into
rename-v23-draftfrom
split-media

Conversation

@M0LTE

@M0LTE M0LTE commented Jul 16, 2026

Copy link
Copy Markdown
Collaborator

Summary

Stacked on #75 (targets the rename-v23-draft branch; GitHub will retarget to main automatically when #75 merges and its branch is deleted).

  • doc/media/* → doc/media/ax.25.2.2.4_Oct_25/ via git mv (all 46 files, 100% renames — history follows).
  • Identical duplicate set created at doc/media/ax.25.2.3-draft/.
  • Both documents' 46 image references rewritten to point at their own folder; verified every reference resolves and no reference crosses folders. The draft's CRLF line endings are preserved.

Why duplicate

The duplication is deliberate and temporary: it disambiguates figure ownership so later v2.3 draft iterations can migrate away from embedded PNGs (per the PNG → GraphML → YAML pipeline) without touching the published v2.2.4 figure set. Git stores identical blobs once, so the repo doesn't grow — only the tree gains entries.

Verified

  • All 46 files were referenced by both AX.25 documents and by nothing else in the repo (KISS/IL2P/FBB docs and spec-sdl reference no doc/media paths).
  • The _media/packet: URLs in the Previous Versions links are untouched (external wiki links).
  • Post-rewrite check: 46/46 refs resolve in each document, 0 missing, 0 pointing at the other document's folder.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XodLuT1R8a4HY76RSZrqFi

doc/media/*.png|jpeg -> doc/media/ax.25.2.2.4_Oct_25/ (git mv, history
follows) with an identical copy under doc/media/ax.25.2.3-draft/, and
both documents' image references updated to their own folder. All 46
files were referenced by both AX.25 documents and by nothing else in
the repo; the other docs (KISS, IL2P, FBB) reference no media.

The duplication is deliberate and temporary: it disambiguates which
document owns which figures so later v2.3 draft iterations can migrate
away from embedded PNGs without touching the published v2.2.4 set.
Git stores identical blobs once, so the repo does not grow.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XodLuT1R8a4HY76RSZrqFi
@M0LTE
M0LTE deleted the branch rename-v23-draft July 16, 2026 22:44
@M0LTE M0LTE closed this Jul 16, 2026
M0LTE added a commit that referenced this pull request Sep 10, 2026
* docs: findings report for the fuzzing-the-figures brief

Records what was built against docs/fuzzing-the-figures.md on 10 September 2026 and what it found. Three checkers now run in packet-net/ax25sdl CI: the static totality and determinism lint (#88), the reference interpreter with its golden traces and the clean-room SREJ traces (#75, #76), and the two-station bounded explorer with its calibration suite (#89).

Headline results: the figures are total and deterministic (8051 feasible valuations, no holes, no overlaps, also true before the #40 fix, so static totality could not have found #40); the calibration score is 10 of the 11 known defects rediscovered between the explorer's invariants and the golden traces, with only #41 out of reach; and one novel hypothesis, H1, a station entering Timer Recovery with no drawn path out once the clearing acknowledgement arrives on an I frame, corroborated by an author's note in direwolf's source. The report also carries the citation coverage map (Timer Recovery has 38 of 92 arms uncited), the pinned delegated semantics, the decisions taken against the brief's suggestions, the model's limits, and the recommended next steps. Nothing is filed as an erratum; the brief's report-first contract holds.

The brief gets a one-line status pointer to the findings.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014qyx5dT8rmRTb8szT4SpEQ

* docs(findings): H1 reproduced on packet.net; runtime acknowledge-pending defect

Folds in the packet.net two-station harness reproduction (packet-net/packet.net#811): the Timer Recovery stranding happens on the real runtime in both quirk modes, a T3 expiry is dropped because figc4.5 has no arm for it, and with the figure run as drawn the retry counter ratchets to N2 across recoveries on a working link. The control case with the acknowledgement on an RR completes normally, so only the ack carrier differs. The same trace exposed a runtime-only defect, Acknowledge Pending left set after an inline retransmission, filed as packet-net/packet.net#812 and added to the next steps.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014qyx5dT8rmRTb8szT4SpEQ

---------

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant