Skip to content

docs: scrub stale v0/v1 markers from shipping comments#123

Open
UnsignedChad wants to merge 1 commit into
mainfrom
chore/v0-comment-scrub
Open

docs: scrub stale v0/v1 markers from shipping comments#123
UnsignedChad wants to merge 1 commit into
mainfrom
chore/v0-comment-scrub

Conversation

@UnsignedChad

Copy link
Copy Markdown
Owner

Audit fix 7 of 8. ~30 comments through sikit + emikit labelled current behaviour as v0 or v1 with no roadmap behind the label. Either dropped the marker or substituted with default / current / baseline. Kept:

  • Touchstone v1/v2 references (real spec version)
  • mpkit docs/mpkit_DESIGN.md v1 (legitimate roadmap doc)
  • sikit/tests/fft_test.cpp v0/v1 variable names

Also fixed one user-visible AmiLoadError message (was not implemented in v0, now not implemented) and a handful of en-dashes the user dislikes that snuck in via copy-paste from old docs.

717 tests still pass.

@UnsignedChad UnsignedChad enabled auto-merge (squash) May 27, 2026 17:36
@UnsignedChad UnsignedChad force-pushed the chore/v0-comment-scrub branch 3 times, most recently from 87ba0bf to 600d410 Compare May 27, 2026 18:25
dozens of comments labelled current behaviour as v0 or v1 with no
roadmap signposting what v2 would change. dropped the label or
substituted with default / current / baseline. Touchstone keeps
v1/v2 (real spec versions), mpkit DESIGN keeps roadmap labels,
fft_test keeps the v0/v1 variable names.
@UnsignedChad UnsignedChad force-pushed the chore/v0-comment-scrub branch from 600d410 to 2753f43 Compare May 27, 2026 18:51
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