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: correct the wiki against the code, and index the decisions
The wiki was last written on 2026-08-07; the repository has moved since, and
in three places the wiki now told readers something that is no longer true.
Every correction below was checked against the code or the ADR it cites, not
inferred.
Architecture
Eleven crates -> thirteen. berrywiki-a11y and berrywiki-import (both added
2026-09-03) were missing entirely; both are described from their own doc
comments, including the parts that are limitations: the a11y crate audits
structure only and BerryWiki has still never been tested with a screen
reader, and the importer refuses .ctb/.ctz/.ctx by name rather than
half-handling them.
ADR-0007 was ruled, and the wiki still said it was open
Architecture and Roadmap both described generated client script as an
unruled question. It was accepted on 2026-09-03 (generated-only, under a
provenance manifest). Stated as ruled *and* as not yet acted on: nothing
shipped changed that day, the no-<script> test is unchanged byte-for-byte,
and the manifest gate must exist before it may be relaxed. The parked UX
work stays parked.
The writer lock exists, and three pages denied it
Compatibility said "no lock between processes", Editing--Drafts said two
serve instances are unsafe, and Roadmap still listed the lock as missing.
ADR-0008's OS advisory lock is implemented and taken by serve and by CLI
mutations. Corrected without overclaiming: the lock does not cover writers
that are not BerryWiki, which is what the stale-write fingerprint still
guards.
Also moved to Built, having been verified in the source: attachments, tags,
per-page history, backup/restore, CherryTree .ctd import, and in-app
commit/fetch/fast-forward/push. In-app conflict *resolution* genuinely does
not exist and is left stated as absent.
New Decisions page indexing all sixteen ADRs with real statuses (0001 and
0002 are still Proposed; the rest accepted), plus why ADR-0003+0007, 0008 and
0015 explain the shape of the code.
_Sidebar.md was regenerated with `berrywiki sidebar --write` rather than
edited by hand, since it is a generated file. `berrywiki check` reports
9 pages, 0 errors, 0 warnings, and every internal link resolves. The new
page's id continues the hand-minted 0197a1c0-…-00000000000N series of its
siblings.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QMTyDv9CoJo5PfeNzyp519