Skip to content

docs: SPEC.md + ai.txt sync for 26.5 (idxof) - #745

Open
danieljohnmorris wants to merge 2 commits into
mainfrom
docs/26.5-sync
Open

docs: SPEC.md + ai.txt sync for 26.5 (idxof)#745
danieljohnmorris wants to merge 2 commits into
mainfrom
docs/26.5-sync

Conversation

@danieljohnmorris

Copy link
Copy Markdown
Collaborator

Post-26.5 doc sync. Closes the doc-rot caught right after the cut.

What landed

  • SPEC.md: idxof s sub > O n row in the text builtins table near ct-eq, with the ILO-39 spec (code-point index, nil on miss, empty needle = 0, Python/JS convention).
  • ai.txt: idxof added to the alias list (between hex and inv) and a token-minimal signature line near ct-eq.

Companion: site repo

ilo-lang/ilo-site already got the matching entry in builtins/text.md (commit cffe25e, direct push to main since the site has no CI).

Why not SPEC.md for ILO-T046

Diagnostic codes live in src/diagnostic/registry.rs (already updated in 26.5 PR #743). SPEC.md doesn't carry a per-code error catalogue.

Test plan

  • cargo test --test skill_md --test skill_modular clean
  • cargo build --release clean

ILO-39 / 26.5 shipped idxof but it wasn't documented in SPEC.md or
ai.txt. Adds:

- SPEC.md: idxof entry in the text builtins table near ct-eq, with the
  ILO-39 spec (O n return, code-point units, empty-needle = 0).
- ai.txt: idxof to the alias list (between hex and inv) and a token-
  minimal signature line near ct-eq.

The site repo got the matching builtins/text.md entry in a separate
commit (ilo-lang/ilo-site#cffe25e). ILO-T046 doesn't need a SPEC.md
entry — diagnostic codes live in src/diagnostic/registry.rs and that's
already updated.
@codecov

codecov Bot commented May 23, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

… fixes)

Documents the marathon release-PR experience: every failure that hit CI,
what the root cause was, what fix landed, and the one piece (ILO-447 VM
defer rewrite) deliberately deferred with #[ignore]'d tests carrying the
tracking reason. Includes the meta-lesson on why main accumulated 24h of
red CI before the cut and what to do about it next time.

Force-added because docs/ is in .gitignore; releases/ is the right home
for this kind of postmortem.
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