Secure context: the app now refuses to start and explains, plus a Troubleshooting entry
Documentation: eleven pages, each checked against the code The wiki holds what the repository cannot: walkthroughs, operating knowledge, and the reasoning behind how the pieces fit together. It deliberately does not restate the README, SECURITY.md, docs/identifiers.md or the two in-app pages, because documentation that drifts from the code is worse than none, so it links to them instead. Every page was written against the source rather than from memory, then read back by someone who had not written it and owed it nothing. That second pass caught a keyboard shortcut attributed to the wrong palette entry, three environment variables presented as governing an enricher that hard-codes its own, a build described as three steps when the fourth is the one that is not committed, and a TLP procedure that could not be performed as written because the panel it named only appears for a multiple selection. One page carries knowledge that is in no file: importing through a draft rather than a workbench. It is stated as what it is, an observation against one instance at one point in time, because that is the honest way to pass on something the code cannot confirm.