Two ledger sections, the README paragraphs for the banner, and the 0.1.13 version row. 「升级提示跨启动存活」records the constraint that is invisible in the code: the probe is throttled to one a day, so a notice held only in memory is visible on the morning a release is found and invisible on every launch after — including the launch right after an update installs. It also records why a restored notice is re-judged rather than trusted, since remembering a claim is how you end up advertising the version the user is already running. 「所有图标共用一份几何」records that the consistency the request asked for is geometric, not chromatic: the tray mark must be flat and alpha-only because the shell tints it, and the app mark must be coloured because nothing tints a dock tile. What made the old icon read as another product was the gradient, the shine, the shadow and six pastel wedge tints — not the presence of colour. Co-Authored-By: Codex <noreply@openai.com> |
||
|---|---|---|
| .. | ||
| ARCHITECTURE.md | ||
| BUILD_WINDOWS.md | ||
| ENGINEERING-NOTES.md | ||
| MOBILE.md | ||
| README.md | ||
| RELEASE.md | ||
| ROADMAP.md | ||
| SECURITY.md | ||
| SPECIFICATION.md | ||
README.md
Shift documentation
Start with the user guide, then choose the engineering document that matches the work.
| Document | Audience | Contents |
|---|---|---|
../README.md / ../README.zh-CN.md |
Users | Features, formats, shortcuts, privacy, known limitations |
ARCHITECTURE.md |
Contributors | Process/window model, module ownership, events, data flows |
SPECIFICATION.md |
Product and QA | Observable behaviour, naming, limits, acceptance criteria |
SECURITY.md |
Security reviewers and maintainers | Trust boundaries, update and LAN risk, residual gaps |
ENGINEERING-NOTES.md |
Contributors | Regression ledger and non-negotiable implementation constraints |
RELEASE.md |
Release maintainers | Channel layout, signing, update handoff and verification |
BUILD_WINDOWS.md |
Builders | Windows prerequisites, cross-build and installer notes |
ROADMAP.md |
Contributors | Completed milestones and next desktop work |
MOBILE.md |
Product planning | Mobile feasibility and architecture plan |
../CONTRIBUTING.md |
Contributors | Setup, checks, change rules and manual matrix |
Source of truth
- Current code and tests define implemented behavior.
- The conversion/tool tables in
READMEdescribe the user-visible catalogue; the runtime catalogue lives insrc/lib/conversionFormats.tsandsrc/lib/radialOrder.ts. - Platform/runtime limitations must be stated as unverified when no real hardware run exists.
- Do not claim a CI run without linking its log.