docs(wiki): correct what is wrong, from v4.1.1 to v5.12.0
The wiki documented a runtime from before the 5.0.0 major. Only 1 of its 26
pages mentioned 5.x at all, and its last commit pointed the footer at the v4.1.1
release. This corrects the claims that are actively wrong; the 5.x features it
has never described are a separate pass.
Embedding-API.md is the page that mattered. It documented 7 of the constructor's
27 parameters, and the 20 missing ones included all three deny-by-default
capability flags -- the single breaking change in 5.0.0 and the thing an embedder
most needs to know. Three of the seven it did document were wrong:
- the prominent warning told embedders to pass `timeout_ms=None` to avoid a
200 ms default deadline. That default was removed when EMBED-001 was fixed;
`timeout_ms` is None already, so the advice is now a no-op
- `allowed_paths` was described as "None = unrestricted". It is a jail on the
current working directory, and has been since before 5.0.0 -- backwards, and
on the axis where being backwards matters
- `max_steps` was listed as an unresolved constant rather than its value
Verified against the running code rather than from memory: all 27 parameters are
documented now, none invented, and the three headline claims were checked on a
live runtime -- allow_subprocess denied, timeout_ms None, allowed_paths a CWD
jail.
Security.md listed v4.0.x as latest and v3.0.2 as supported, on the page that
says which versions receive security fixes. It now names the 5.x line, the two
releases to skip (5.0.3 breaks nodus-sdk at construction, 5.7.0 makes
`nodus check` reject correct code), the 5.6.0 floor for anyone embedding a
capability policy, and the deny-by-default posture including `nodus serve`'s
since 5.10.0.
Front-door version claims corrected on Home, Getting-Started, Roadmap, the
footer, the sidebar, Syntax-Reference and the two agent-skill pages.
Package counts on the two *live* claims are now a link to
docs/ecosystem/README.md, which is the authority and cannot go stale here. The
counts inside the changelog and roadmap entries are left alone: those describe
what was true on the day of a release, and Roadmap now says so rather than
leaving a reader to guess which numbers are current.
docs(wiki): bring to v4.1.1; document match, break, and continue
The wiki was four releases behind at v4.0.8 and, more importantly, documented
none of the syntax added in v4.1.0. "match", "break", and "continue" appeared
NOWHERE across Control-Flow, Syntax-Reference, or Language-Overview — a reader
using the wiki as their language reference had no way to learn they exist.
Control-Flow gains full sections for both, with verified output: the loop
semantics (continue still runs a C-style for's increment), both compile-time
errors, the iterator pop on break, and match's rules — == comparison, first
match wins, _ last, value matching only, and the three arm-body forms.
Syntax-Reference gains condensed versions pointing at it.
Language-Overview's stability list now carries both surfaces as Mostly Stable,
with the reason match is not Stable (adding destructuring would extend the
surface).
Version and count claims: Home, Getting-Started, Roadmap, _Sidebar, _Footer
were all on v4.0.8; the ecosystem was described as 35 packages, which is 32.
Changelog and Roadmap gained the missing v4.1.0 and v4.1.1 entries.
Standard-Library carried the same v3-era return types the repo guide did, fixed
there earlier today:
- len() documented as returning a float — it returns an int since v4.0
- floor/ceil now noted as returning int
- type(x) listed "number" as a type name; a bare numeric literal is "float"
_Footer linked to a v4.1.1 GitHub release that does not exist — only the tag
was pushed — so it now points at the releases index rather than a 404.
Every code block added here was executed against 4.1.1 and its output pasted
verbatim. Ran all 68 nd blocks across the three edited pages: the 7 that fail
standalone are pre-existing illustrative fragments referencing undefined
context (this wiki has no doc gate and uses that style throughout). The one
fragment I introduced was made self-contained instead.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
docs(wiki): update all pages from v1.0 to v4.0
- Syntax-Reference.md: add integer literals (42i) and string interpolation (\(expr))
- Standard-Library.md: add std:tool, std:http, std:subprocess, std:time, std:hash,
std:encoding, std:secrets, std:test, std:bool; add AI-native section (std:identity,
std:effects, std:sys, std:retry, std:circuit_breaker); fix std:json map/bracket note
- Type-System.md: add integer and error types; i suffix note
- Language-Overview.md: add AI-native primitives; update stability index
- Getting-Started.md: v4.0.0 pre-release; pip install nodus-lang
- Home.md: v4.0.0; pip install nodus-lang; add AI-native primitives
- _Sidebar.md: Nodus v4.0
- Embedding-API.md: pip install nodus-lang; EMBED-001 warning; bracket notation;
set_trace_id/tool_registry; remove post-v1.0 planned language
- Workflows-and-Task-Graphs.md: bracket notation for run_workflow(); nodus workflow run
- Error-Handling.md: remove "planned for v1.0.x" finally-without-catch language
- Security.md: update supported versions to v4.0.x / v3.0.2
- Roadmap.md: full rewrite — v1.0 through v4.0 history; near-term and long-term plans
- Changelog.md: add v2.0, v2.1, v3.0, v3.0.2, v4.0.0 entries
- Contributing.md: PYTHONPATH requirement for tests; updated release process
- _Footer.md: Nodus v4.0.0 (pre-release)
- Performance-Guide.md: remove post-v1.0 planned language
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>