Repository navigation
docs: complete bilingual reader rollout and documentation rules - #93
Merged
Merged
Conversation
Publish the reviewed documentation and terminology changes with their hygiene, size-budget and document-group checks. Keep runtime feature implementation out of this change.
Preserve upstream documentation facts at their bilingual topic owners, complete imported companion groups, and retain source-record boundaries. Runtime implementation remains identical to main.
wefio
marked this pull request as ready for review
October 19, 2026 09:35
10 of 14 tasks
wefio
added a commit
that referenced
this pull request
Oct 20, 2026
…bilingual rollout #93 split design.md, completion-audit.md and hidden-features-registry.md into subfiles with zh-CN and terms companions, so every conflict was documentation. Resolution takes main's structure and re-homes this branch's own content: - design/progressive-retrieval: Chinese recollection questions, lexical tie resolution before the direct cap and AG budget, session-only recall cue pilot - design/incremental-storage-and-index-maintenance: access-pressure eligibility - design/product-boundary/agent-cli-and-resident-service: controlled daemon reload - completion-audit/requirement-matrix and hidden-features-registry/feature-register: event-record and controlled-reload rows - decisions 2026-10-15-session-recall-cues and 2026-10-17-board-event-records: terms companions - board-event-records plus five experiment records: zh-CN and terms companions required by the post-#93 document-group contract; the Chinese originals moved to .zh-CN.md and English text now sits on the canonical name No source file conflicted; the code from this branch is unchanged by the merge.
This was referenced Oct 20, 2026
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
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.
Change summary
What: Complete the reader-oriented bilingual documentation and terminology rollout, add continuous documentation-rule checks, and reconcile the existing documentation with current
main.Why: Keep English primary documents, Chinese companions, terminology owners and complete reading units aligned. Prevent missing companions, invalid structure and ambiguous terminology from silently returning, without replacing semantic review with green structural checks.
Changes:
docs:check, covering root README,docs/andskills/, including orphan companions and missing primary files.1534e98acbdd93f037d128b5ee0ce8720abf3234; resolve all 48 documentation conflicts at their topic owners instead of discarding upstream facts. Complete 24 imported companion gaps.Current head:
b6202e0c1527904cec3b7b21b9caedf2a960dbce. The preserved reviewed source branch is not pushed as unrelated feature history.Verification
MERGEABLE.The final commit adds only the bilingual verification note; documentation and glossary checks were rerun afterwards. Detailed dated evidence and qualifications are in the existing rollout audit.
Not verified
The complete local
verify:static/agent:verifybundle was not rerun because its subpackage step invokes dependency installation. No local dependency installation was performed; the fourteen non-installing static commands and full product/mutation suites were run separately, not represented as a complete verifier receipt. CI's static/package contracts have passed.At the final RCP observation for the current head, Static/package contracts, Product/coverage, Research characterization, Node 22 compatibility, CodeFactor and the aggregate All checks passed are all SUCCESS. Windows chaos is skipped by the event policy, not counted as executed. No deployment, live-provider workload, official benchmark rerun or end-to-end host-input acceptance is claimed. Historical limitations in retained reports remain scoped evidence, not additional unfinished items in the accepted documentation queue.
Completion checklist
Local quality checks
verify:static/agent:verifybundle — intentionally not claimed.RCP and remote confirmation
nmg-rcp forge-status --pr 93 --jsonat the current head.All checks passedis SUCCESS.PR remains draft. No merge has been performed.