docs(wiki): move subtree-move and conflict classification to Built
Both packages are *DONE* in docs/execution/work-packages.adoc (P2-move,
P3-conflict, both 2026-09-02) but this page still listed them under "Next",
understating the project to anyone reading the published wiki.
- Subtree move and conflict classification move to Built, each described by
what actually landed rather than by what the package was called.
- The accessibility gate is added to Built: fourteen structural rules over
every rendered route. It was built on 2026-09-03 and had never appeared here.
- "Never merges two authored sides" is restated as a deliberate limit rather
than a gap, which is what the package's own stop-rule says.
- Zim import is promoted from Later to Next, matching the tracker.
- The unrun accessibility walkthrough is stated explicitly under Next, so no
screen-reader claim is implied anywhere on this wiki.
Verified with `berrywiki check` (9 pages, 0 errors, 0 warnings) and the
generated sidebar is byte-identical, so _Sidebar.md needs no regeneration.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016CVTLf6maUsJSiNDCgWdFu
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
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.