Repository navigation
docs: review Memo document evidence and project decisions - #333
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Readers reviewing project evidence can inspect the paragraphs around cited documents and understand when an agent may decide a proposal. Pin reviewed Memo0.82.0 and import five compatible prose-only permission guides from immutable merged commit a46159857442f2008324001468b440f009ea9b8c (Memo #353).
Update EN/RU/ES project review, source state and permission explanations, retain old heading anchors, and retire the facts-accept correction now fixed natively. Existing tg/MAX/Zoom/Drive reviewed pins remain intact. Page/locale inventory, behavior sources, findings and review boundaries: docs/reviews/2026-10-20-memo082-review.md.
Passed: full sync, five offline released command contracts, translation structure/fingerprints, strict docs checks (zero reference gaps/invalid examples), release-note checks, lint, typecheck, 322 unit tests, seven browser smoke cases, and a separate 24-page/24-Markdown EN/RU/ES mobile check. Existing Sidebar key warnings remain; no runtime code or test coverage gates changed. CI owns full export/link/SEO/browser validation before deployment, followed by affected production-route verification.