nex_shift/docs
mula.liu 706ff6fb26 fix(icons): orange ground and white mark, as the product has always been
Reported: "你改的标注应用图标不对啊,我之前是橙底、白线的风格(参考 squid 的
图标)."

The previous commit inverted the figure/ground relationship. Chasing
consistency with the alpha-only tray mark, the app tile went to espresso
with a warm mark — technically consistent geometry, and it passed every
contrast check I ran, but those checks were pointed at the wrong axis.
Consistency has two of them here, geometry and light/dark, and the one a
returning user actually recognises is "orange tile".

Now the app icon is literally the tray mark with a colour turned on:
`#FF6B35` ground, which is the orange this project's own master already
carried, and `#FFF4EA` mark, the cream the app's panels are drawn on. The
plus stays a punched hole showing the ground rather than a third colour,
so both icons are one drawing on two different grounds. Two colours also
removes the failure mode the last version needed a rule to defend.

Tray PNG is byte-identical again; the .ico ladder (16/24/32/48/64/256) and
.icns entry set are unchanged, and every tracked PNG still matches its
committed dimensions.

Co-Authored-By: Codex <noreply@openai.com>
2026-11-19 21:49:05 +08:00
..
ARCHITECTURE.md docs: 收录 2026-11 全面评审的修复与约束 2026-11-07 12:42:35 +08:00
BUILD_WINDOWS.md release: prepare Shift 0.1.8 2026-10-27 18:45:32 +08:00
ENGINEERING-NOTES.md fix(icons): orange ground and white mark, as the product has always been 2026-11-19 21:49:05 +08:00
MOBILE.md docs: 收录 2026-11 全面评审的修复与约束 2026-11-07 12:42:35 +08:00
README.md docs: 收录 2026-11 全面评审的修复与约束 2026-11-07 12:42:35 +08:00
RELEASE.md release: prepare Shift 0.1.13 2026-11-19 21:29:30 +08:00
ROADMAP.md docs: 收录 2026-11 全面评审的修复与约束 2026-11-07 12:42:35 +08:00
SECURITY.md docs: 收录 2026-11 全面评审的修复与约束 2026-11-07 12:42:35 +08:00
SPECIFICATION.md docs: 收录 2026-11 全面评审的修复与约束 2026-11-07 12:42:35 +08:00

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 README describe the user-visible catalogue; the runtime catalogue lives in src/lib/conversionFormats.ts and src/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.