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
docs(wiki): correct the default port, the publishing model, and the Proposed-ADR summary
Three claims contradicted the code.
Getting Started sent the reader to http://127.0.0.1:8080. DEFAULT_ADDR is
127.0.0.1:23779, chosen from an IANA-unassigned block precisely to avoid the
8080/3000 class. The page now gives the real port, says it listens on loopback
TCP only, and names --addr.
"Publishing your changes" said BerryWiki writes to your working copy and that
committing is yours to do, with a git add -A recipe. The CLI's own USAGE says
the opposite is the default: a git working tree is served with commit-on-save,
one commit per save, sidebar included, and /changes offers fetch, fast-forward
and push, never a merge or a force. A reader following the old page would have
hand-committed on top of BerryWiki's own commits. The section is rewritten from
USAGE and now documents --no-commit and --author, and states plainly that what
is missing is resolving a conflict, not committing.
The Decisions summary asserted both Proposed ADRs wait on "the same thing" and
named ADR-0002's provisional answer as a token-through-the-environment mirror.
ADR-0002 is the authentication strategy: the token is the push credential, kept
out of the clone URL, not the read-only --github mirror. Both ADRs now state
what they actually decide and what evidence each is waiting on.
Verified: berrywiki check 0 errors / 0 warnings; berrywiki sidebar output
byte-identical to _Sidebar.md.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QMTyDv9CoJo5PfeNzyp519
docs(wiki): document backup/restore/import; correct the Proposed-ADR claim
Getting Started covered only check, sidebar and serve. Four feature areas
landed on 2026-09-03 with an ADR each and had no usage anywhere in the wiki:
backup, restore and import now have sections written from the CLI's own USAGE
text, preserving each command's refusals verbatim (backup refuses a dirty tree,
restore refuses a non-empty folder, import writes nothing without --apply and
refuses rather than overwrite).
Decisions.md claimed "nothing in the codebase assumes an answer to either"
Proposed ADR. That was mine, not the ADRs', and it is false: the code already
implements ADR-0001's `--` separator and ADR-0002's environment-token mirror.
They are provisional, not unimplemented.
Compatibility said conflicts are "detected and shown" while Roadmap listed
per-page presentation as unbuilt. Both are true and now say so: conflicts_page
renders one /conflicts view for the whole wiki, not a per-page one.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QMTyDv9CoJo5PfeNzyp519
docs: real wiki, authored in BerryWiki's own format
Replaces the one-line default stub with eight pages covering getting started,
the page format, editing, architecture, limits and the roadmap.
The wiki dogfoods the tool: every page carries a BerryWiki metadata block,
the hierarchy comes from parent ids rather than filenames, and _Sidebar.md
was generated by 'berrywiki sidebar --write'. 'berrywiki check' reports 8
pages, 0 errors, 0 warnings.
Compatibility-and-Limits states plainly that no GitHub Wiki behaviour the
design relies on has been verified against a live wiki.