docs: README language switcher + Powered by EMRG + concise current-state docs (rants 2026-08-22T07:46:46/07:49:58/07:51:36) - #119
Merged
Conversation
…ate docs (rants 2026-08-22T07:46:46/07:49:58/07:51:36)
7 tasks
argszero
added a commit
that referenced
this pull request
Sep 13, 2026
Two rendered strings in `ui/js/i18n.js` point at material that the 2026-08-22 docs flattening deleted: - `wallet.raise.sub` / `admin.raise.sub` carry the requirement id `US-20`. Commit 6d87213 (#119) rewrote docs/user-stories.md into a current-state doc and dropped every `US-<n>` id, so `US-20` resolves nowhere: `grep -rn 'US-[0-9]' docs/ README.md README.en.md` is empty at HEAD. Every other `US-` id in the repo lives in a code comment or in ui/README.md; these were the only ones shown to users. - `mk.detail.routeVal` cites 「架构 v0.2 路由策略」. The same commit deleted the `4.2.1 路由与故障转移策略（v0.2）` section from docs/architecture.md, and that file has no version stamp left. One root cause, two pointer shapes: #179 fixed the `§N` references the flattening broke and #216 the `file:line` ones, but the `name + stamp` shape (`US-20`, `v0.2`) was never audited. The pack values are now plain prose (both sentences were already self-contained), each edited static fallback in ui/index.html is kept byte-equal to its pack value, and the three ui/README.md lines that cited the deleted section are re-pointed at the section that carries the content today (docs/architecture.md §3, the `router.rs` row), in the style of #179. `ui/` text only: no Rust change, no i18n key added or removed (786/786 before and after), no new T() call sites or data-i18n attributes. i18n.js content changed, so its cache-bust is bumped (20260912-5 -> 20260914-4). Co-authored-by: argszero <argszero@argszerodeMac-mini.local>
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.
Summary
Documentation refresh wave (3 rants, all docs):
[English](README.en.md) | [简体中文](README.md)links added at the top of both READMEs so GitHub renders the language switcher on the repo pagedocs/architecture.md(158→90 lines): removed version-history header; now current tech stack (Rust + axum + SQLite + native JS frontend), modules, data flow, real DB tables, API list, and a roadmap section with clearly-marked not-implemented items (PostgreSQL/Redis/React/Tauri)docs/plan-api-matrix.md(135→35 lines): condensed from research notes to protocol-support status (3 endpoints + SSE, client setup, upstream providers, model catalog)docs/user-stories.md(389→52 lines): condensed from interview-style stories to roles, core flows, and capability checklistCONTRIBUTING.md: verified current; added a short rant-driven development flow sectionRelated Rants
Tests
Acceptance