Skip to content

Releases: kaiwutech-TW/flightwake

v0.11.0 — four-language install, no wrong guesses, no silent overwrites

Choose a tag to compare

@kaiwutech-TW kaiwutech-TW released this 27 Jul 04:07

The README has been in four languages since launch — the installed content was only ever two. This release closes that gap, and fixes two places where flightwake was quietly working against its users.

  • Installed content now ships in four languages: --lang=en|zh-TW|zh-CN|ja. Templates, the four skills, the CLAUDE.md snippet, the status-line gauge, and all CLI/hook output follow the language you pick. Every README's install section carries a copy-paste table, including the --force line for switching an existing install (your STATE/DECISIONS/TRAPS/records are never touched — they stay in whatever language you wrote them).
  • No language auto-detection, on purpose. A terminal's LANG and the OS locale routinely disagree — measured on a zh_TW machine reporting en_US.UTF-8 — and reading the real system locale needs a shell call on one platform only, which the zero-dependency promise rules out. A confident wrong guess is worse than a stated default, so init names the alternatives instead of guessing.
  • Overwritten local edits are named. Hand-editing an installed skill (to translate it, say) used to vanish without a word at the next update. Framework files are still framework-owned, but now each overwritten file is listed. Flagged only when the install is already at the same version and language — across a version or language change, content legitimately differs.
  • STATE staleness counts human commits only. Bot commits (dependabot[bot], renovate[bot], …) no longer push the lag counter — in both the Stop-hook/CI check and the gauge. A dependency bump never makes STATE wrong, and a bot's PR could never satisfy the gate; an unsatisfiable check just trains everyone to ignore red.
  • The gauge shows the installed version in dim text as its first field (the previously unreleased 0.10.1).
  • Repo hygiene: Dependabot groups github/codeql-action/* into one PR (the sub-actions must move in lockstep), and the project gained CONTRIBUTING, CHANGELOG, a code of conduct, and issue/PR templates.

Install: npx flightwake init --statusline · 繁中 --lang=zh-TW · 简中 --lang=zh-CN · 日本語 --lang=ja

Note: the Simplified Chinese and Japanese content was translated without a native-speaker review. Corrections are especially welcome.

v0.10.0 — cross-repo trap dual-write, green needs evidence, live demo

Choose a tag to compare

@kaiwutech-TW kaiwutech-TW released this 23 Jul 11:36

An external-evaluation-driven release: we surveyed the neighboring ecosystem (auto-capture memory, spec/task-first frameworks, markdown conventions), confirmed the retrospective × git-native × zero-dependency × hard-guard quadrant is still unoccupied, and closed the three real gaps the evaluation surfaced.

  • health=green now needs evidence. The Stop hook (and --ci) gains a second check: STATE claiming health: green while the latest record carries no test evidence (empty tests: frontmatter) gets a nag — the "tests green before done" hard guard is now wired to the health color. Detection is frontmatter-presence only, no prose judgement; in CI it's a warning, never a gate.
  • Cross-repo traps stop biting twice. fw-trap now judges a trap's scope: platform/language-layer traps (any project would step in them) are still registered in the repo's TRAPS — the registry must stay self-contained — and saved to your user-level memory so your other repos get the warning too. One copy per scope is division of labor, not duplication.
  • Honest edges of the reminder net, documented in all four README editions: the lag check counts commits, so a session that commits nothing (research, ops) or a squash/rebase flow slips under it. The net catches forgetting; it doesn't replace the session-end obligation.
  • README now opens with a live demo: a real ~30-second cold start recorded on this very repo — one command, two file reads, and a fresh session reports exactly where the last one left off.

v0.9.0 — English defaults, in-place update, gauge update hint

Choose a tag to compare

@kaiwutech-TW kaiwutech-TW released this 19 Jul 03:07

The "full i18n" release — the zh-TW caveat from the launch post is now closed.

  • English by default. npx flightwake init now installs English templates, skills, and CLI/hook output. Traditional Chinese stays fully supported: --lang=zh-TW. Existing installs (all pre-0.9 = zh-TW) are detected and keep their language on update.
  • npx flightwake update — in-place upgrade that re-detects what you installed (language, statusline, private mode) and refreshes only framework-owned files. User data (STATE/DECISIONS/TRAPS/records) is never touched.
  • The gauge now tells you when a newer version exists (→ v0.9.1 available: npx flightwake update), shown only when nothing more urgent is up. Anonymous npm-registry GET at most once per 24h, cached in the OS temp dir, always in a background process. Opt out: FLIGHTWAKE_NO_UPDATE_CHECK=1.
  • The stage-by-stage playbook (docs/workflow.md) is now English-first with a zh-TW edition.
  • Also ships the v0.8.2 → v0.9.0 fixes: statusline TTY guard (manual runs no longer hang).

v0.8.2

Choose a tag to compare

@kaiwutech-TW kaiwutech-TW released this 18 Jul 15:26

Two fixes from the first day of real-world use:

  • Status line: correct context-window size on 1M-context models. The gauge now reads context_window from Claude Code's statusline stdin (official schema) instead of assuming 200k — on Fable 5-class sessions it previously over-reported usage ~5× (e.g. showing 63% when actual was 12.7%). Falls back to the old 200k estimate on older Claude Code versions.
  • init now tells you the status line is opt-in. Plain npx flightwake init ends with a hint that the gauge isn't installed and --statusline adds it; READMEs (en/zh-TW/zh-CN/ja) note that re-running init with the flag just adds the gauge, everything else is skipped.

v0.8.1 — actionable status line

Choose a tag to compare

@kaiwutech-TW kaiwutech-TW released this 18 Jul 13:50

The status line now tells you the next command for the current state: session just started → /fw-coldstart; STATE ≥3 commits behind → /fw-record; context running hot → /fw-record → /clear → /fw-coldstart; all healthy → silence.

v0.8.0 — status line

Choose a tag to compare

@kaiwutech-TW kaiwutech-TW released this 18 Jul 13:36

New: npx flightwake init --statusline — a persistent gauge at the bottom of Claude Code: health color · STATE staleness · context usage (a hot bar = time to wrap up or hand off). Never overwrites an existing statusline. Also: GSD migration guide in all four README editions.

v0.7.2

Choose a tag to compare

@kaiwutech-TW kaiwutech-TW released this 18 Jul 13:11

First public release. ✈️

  • Open-sourced 2026-07-18: gaps 1–7 all closed (de-identification guard, superseded lifecycle, multi-platform install, --private local mode, uninstall, CI-side STATE check, monorepo policy)
  • README in four languages (EN primary · 繁中 · 简中 · 日本語)
  • Published via npm Trusted Publishing (OIDC + provenance)

Install: npx flightwake init