chore(state): update CURRENT_STATE.md after autonomous quality drain#1068
chore(state): update CURRENT_STATE.md after autonomous quality drain#1068ericsocrat merged 1 commit intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Pull request overview
Updates CURRENT_STATE.md to reflect the latest repository snapshot after seven recently merged “autonomous quality drain” PRs, correcting state drift (latest SHA, open issues, and update timestamp) and recording the shipped work.
Changes:
| - **Open PRs:** 0 | ||
| - **Open issues:** 0 | ||
| - **Open issues:** 2 (#1059 production deploy — blocked on user authorization; #1060 npm audit moderates close-as-monitor — blocked on user authorization) | ||
| - **Mode:** 🟢 Clean — no active work |
There was a problem hiding this comment.
The doc now reports Open issues: 2 in the header, but later in the same file the Key Metrics Snapshot still says Open issues: 1 | Open PRs: 1 (Dependabot #941). Please update/remove the later snapshot line so the file stays internally consistent (or clarify if that snapshot is intentionally historical).
| - **Mode:** 🟢 Clean — no active work | |
| - **Mode:** 🟡 Blocked — awaiting user authorization on 2 open issues |
| 1. **React Compiler lint warnings cleanup** — Phase 1 done in PR #1063 (resolved 6 violations: 1× `static-components`, 1× `purity`, 1× `preserve-manual-memoization`, 3× `refs`; promoted 4 of 5 rules from `warn` to default `error`). Phase 2: 17 remaining `set-state-in-effect` violations still at `warn` — dedicated cleanup pass when convenient, no urgency. | ||
| 1. **React Compiler lint warnings cleanup** — Phase 1 done in PR #1067 (closes #1063 — resolved 6 violations: 1× `static-components`, 1× `purity`, 1× `preserve-manual-memoization`, 3× `refs`; promoted 4 of 5 rules from `warn` to default `error`). Phase 2: 19 remaining `set-state-in-effect` violations across 14 files still at `warn` — each requires per-component architectural review (key-based reset, lift state up, derive during render, or uncontrolled refs); recommend per-file PRs rather than bulk fix. | ||
| 2. ~~**Remove `@eslint/eslintrc` and `@eslint/js` from devDependencies**~~ — ✅ Done in PR #1053 (2026-04-30). Restored Linux-only `@emnapi/*` nested lockfile entries to fix cross-platform CI break. | ||
| 3. ~~**`middleware.ts` → `proxy.ts` migration**~~ — ✅ Done in #1062. File renamed via `git mv`; exported function renamed `middleware` → `proxy`; deprecation warning eliminated. |
There was a problem hiding this comment.
This line cites "✅ Done in #1062", but #1062 is the tracking issue; the actual shipped change was PR #1066 (per the earlier table and PR history). Update the reference to avoid confusing readers.
| 3. ~~**`middleware.ts` → `proxy.ts` migration**~~ — ✅ Done in #1062. File renamed via `git mv`; exported function renamed `middleware` → `proxy`; deprecation warning eliminated. | |
| 3. ~~**`middleware.ts` → `proxy.ts` migration**~~ — ✅ Done in PR #1066. File renamed via `git mv`; exported function renamed `middleware` → `proxy`; deprecation warning eliminated. |
Updates CURRENT_STATE.md to reflect 7 PRs merged since the last state snapshot at #1054.
Drift fixed
b25fb4aa→1eca15090→2(ops(deploy): Deploy 18 pending production migrations from epic #920 #1059 deploy + chore(security): Track 4 moderate npm audit vulnerabilities (postcss/uuid) — no safe upgrade path #1060 npm audit, both blocked on user authorization)Recently Shipped (new section)
Follow-up note correction
Updated the React Compiler follow-up to reference PR #1067 (was #1063, which is the issue number) and corrected the Phase 2 count to 19 violations across 14 files (was 17), with explicit per-file PR recommendation matching the deferred-state notes from PR #1067 itself.
Verification
scripts/repo_verify.ps1— 6/6 PASS