Skip to content

dev: STATE.md — v0.29.3 released; page re-verified 2026-09-23 - #330

Merged
mmcky merged 1 commit into
mainfrom
dev/state-v0293-released
Sep 23, 2026
Merged

mmcky merged 1 commit into
mainfrom
dev/state-v0293-released

Conversation

@mmcky

@mmcky mmcky commented Sep 23, 2026

Copy link
Copy Markdown
Contributor

Post-release STATE refresh after v0.29.3, with the page re-verified against live state so verified: can honestly move to 2026-09-23 (it had stayed at 2026-09-21 through #319 and #329).

Every top-level bullet was checked against GitHub (issue/PR states, tags, releases, the #257 tracker, npm test, npm audit) before editing. What changed:

.dev/ only, no code. It will conflict with #314 (.dev/ → .qe/dev/) — whichever merges second needs a rebase.

🤖 Generated with Claude Code

Every bullet checked against live state: shipped releases (v0.26.0–v0.29.3)
moved from In flight to Recently landed or folded into Older releases; the
#276 moratorium line corrected to the 2026-08-20 ruling; Next resumes at
today's fr engine queue (#324–#327); tests 1,590/67; prod advisories 2.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Copilot AI lite review requested due to automatic review settings September 23, 2026 09:35

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟢 Approval recommended

Documentation-only refresh of .dev/STATE.md with consistent formatting (including the required verified: first line) and no issues found in the updated content.

Review effort: Lite
Findings: None

What changed in this PR

This PR refreshes .dev/STATE.md after the v0.29.3 release, updating the “verified” freshness marker and rewriting the current status snapshot to reflect live in-flight work, recent releases, and updated health metrics.

Changes:

  • Updated verified: to 2026-09-23 and pruned/moved older “In flight” material so it only reflects active work.
  • Added/updated in-flight bullets for the new French typography issues (#324–#327), whole-document-path defects (#326/#203), and clarified current W1/#169 status.
  • Refreshed “Recently landed”, “Next”, and “Health & context” with v0.29.3 release details and current test/advisory counts.
File Description
.dev/​STATE.md Post-release re-verification and updated project-status snapshot (in-flight items, recent releases, next steps, and health metrics).

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@mmcky
mmcky merged commit 4507daa into main Sep 23, 2026
1 check passed
@mmcky
mmcky deleted the dev/state-v0293-released branch September 23, 2026 09:44
mmcky added a commit that referenced this pull request Sep 23, 2026
Directory-rename detection moved the six .dev/ files main added since the
branch point (two decision records, three log entries, the #319 arm
references) into .qe/dev/. Conflicts resolved:

- .qe/dev/STATE.md: main's re-verified page (#330), with its one .dev/
  path mention updated and the #314 In-flight bullet replaced by a
  Recently-landed entry for the move itself.
- src/language-config.ts: main's ml rules (#315/#317) with the four
  decision-record path comments pointed at .qe/dev/decisions/.
- dist-action/index.js: rebuilt; differs from main only by those comments.

Also carried through: rate-check.sh (#323, merged after this branch) wrote
its logs to .dev/scratch/rate-check/, which would recreate an in-tree
scratch folder that is no longer git-ignored. Logs now go to
${TMPDIR:-/tmp}/action-translation-rate-check/<stamp>/ per
D-2026-09-21-no-scratch-in-tree; its README line updated to match.

npm test 1590/1590, lint and format:check clean, check-dev-refs: 168 .qe/
references resolve.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants