docs(wiki): 3.6.3 Errata — the 404 from the library, and configs that reset themselves
Both symptoms were seen live today. The library links were built from names whose first character the scanner had cut (content is a symlink in the documented layout), so every link 404ed while the viewer was fine; and a config unreadable for the pool user was replaced with defaults on the next request. Troubleshooting now names both, with the two commands that tell them apart.
docs(wiki): 3.6.0 Signet — provable releases
Home: version and a New in 3.6.0 block (artifact verification, atomic deploy with rollback, fingerprints, the browser gate). Changelog: the 3.6.0 entry. Development: baseline 3.6.0. Getting started: the 3.6.0 archive name. Footer and sidebar: version.
Updates: apply now installs the archive's own manifest (and why that is not bookkeeping); the 'after an update' section is corrected against measurement — opcache keys a script by the request path, not the symlink target, so a graceful reload does not clear it, and php -r opcache_reset() clears nothing the web pool sees; a panel-versus-mdscribe-deploy table and the release-directory layout. Troubleshooting: the same symptom with the four commands that tell disk from bytecode.
docs(wiki): publish the MD.Scribe 3.4.3 guide
Twelve pages plus sidebar and footer: getting started, installation (layouts,
web-server snippets, permissions, verified hosts), configuration generated from
config/defaults.php, Markdown features, search and tags, admin guide, HTTP API,
updates, troubleshooting, development and changelog.
Facts come from the code and from a live installation on PHP 8.5.12: the config
keys and defaults are read out of config/defaults.php, the API surfaces from
docs/http-api.md and routes, the test count and checker baseline from an actual
run.