docs: correct the filename-mapping claim — GitHub double-spaces the title
The previous commit overstated one of the three results. `Editing--Attachments`
does not render as a nested title on github.com; GitHub substitutes each `-`
with a space, giving the literal double-spaced title "Editing Attachments".
Control: `Getting-Started` titles as "Getting Started".
The hierarchy is real but comes only from the generated _Sidebar.md. ADR-0001's
premise (the native UI cannot show directory hierarchy) survives; what it never
recorded is the cosmetic cost of the scheme in that same UI.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QMTyDv9CoJo5PfeNzyp519
docs: record the first live GitHub wiki observations
Publishing this wiki and reading the rendered HTML back retired three of the
four GitHub-behaviour assumptions the project has carried untested since
inception: HTML comments are stripped, _Sidebar.md renders on every page, and
the flat `--` filename scheme maps to nested titles as designed.
The fourth — token-authenticated clone and push of <repo>.wiki.git, ADR-0002 —
is NOT confirmed. This wiki is pushed over SSH.
Compatibility-and-Limits.md and Verification.md are updated together, because
a limits page left asserting the negation is the exact drift this wiki was
just audited for.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QMTyDv9CoJo5PfeNzyp519
docs(wiki): correct three stale pages against the code and add four
Commit 7fbc401 moved subtree-move and conflict classification to Built on
Roadmap.md but left the pages that advertise *limits* asserting the negation.
A reader landing on Editing or Compatibility was told BerryWiki cannot do
things it does.
Corrections, each verified against origin/main at 0cf0066:
- Getting-Started: Rust 1.85 -> 1.89. Cargo.toml declares
rust-version = "1.89" and CI carries a 1.89.0 matrix leg. (The stale figure
almost certainly came from berrywiki-serve's own crate description, which
still says 1.85 and is a separate defect in the main repo.)
- Editing: drop "Moving a page ... is not implemented" (move_page is
implemented) and "Committing and pushing. Use git." (commit-on-save is the
default and /changes does fetch/ff/push). Keep the --github read-only entry,
and add the honest residual: body and metadata conflicts are not merged for
you.
- Compatibility and Limits: drop the subtree-move row; rewrite the conflict
row, which said conflicts are "not yet classified or presented per page"
when ConflictKind has seven variants and they are shown three-way per page.
New pages, each documenting something no existing page did:
- Editing--Attachments: the nine-entry allowlist, the 1 MiB cap, the
assets/<page-id>/ layout, why SVG/HTML/JS are refused, and 404-not-403.
- Syncing-and-Conflicts: fetch/fast-forward/push with no fourth operation,
why conflicts are read from the git index rather than the marker-laced
worktree, all seven ConflictKind variants, and why only Sidebar is settled
automatically.
- Diagnostics: the eleven dotted codes split by severity, and the 0/1/2 exit
codes (only graph.duplicate-id and graph.cycle are errors).
- Verification: what is checked automatically, the fourteen a11y structural
rules, and what has never been verified at all - no live GitHub wiki, MSRV
declared but never built, no screen-reader test, no proofs, ADR-0001 and
ADR-0002 still Proposed. Points at docs/AFFIRMATION.adoc.
_Sidebar.md is regenerated by `berrywiki sidebar --write`, not hand-edited, so
Home's claim that BerryWiki generates it stays true. `berrywiki check` reports
13 pages, 0 errors, 0 warnings.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QMTyDv9CoJo5PfeNzyp519