everything-claude-code

docs(i18n): add German (de-DE) localization scout

Adds the German locale per maintainer guidance in issue #1980.

- docs/de-DE/README.md: full translation of the English root README
- docs/de-DE/GLOSSARY.md: German terminology decisions (which ECC
  terms stay English vs. German)
- manifests: docs-de-de module + locale:de-de component, modelled on
  the existing docs-zh-tw / locale:zh-tw entries
- scripts/lib/install-manifests.js: de-DE in SUPPORTED_LOCALES, plus
  de-DE and de aliases so `--locale de` and `--locale de-DE` resolve
- tests/lib/locale-install.test.js: focused de-DE coverage
- Deutsch added to the language selector tables in all 10 existing
  READMEs (root + 9 localized)

Refs #1980

Martin Klein · 2026-05-21 00:50:39 +02:00

ef0c55c40f

docs: sync live native payments gate evidence

Affaan Mustafa · 2026-05-19 23:25:38 -04:00

1e8c7e7994

Sync billing gate env-file evidence (#2021 )

Affaan Mustafa · 2026-05-19 22:43:19 -04:00

6e25458dbc

docs: sync selected-target announcement gate (#2020 )

Affaan Mustafa · 2026-05-19 22:09:45 -04:00

c2471fe5c5

Sync Marketplace Pro readback release gate (#2019 )

* docs: sync marketplace pro readback gate

* docs: refresh operator dashboard after readback sync

* docs: sanitize marketplace readback summary

* docs: refresh operator dashboard after marketplace readback

Affaan Mustafa · 2026-05-19 21:39:03 -04:00

30f60710d4

docs: sync late May 19 release roadmap state

Affaan Mustafa · 2026-05-19 19:02:43 -04:00

b3c015c744

Add release approval gate

Affaan Mustafa · 2026-05-19 18:18:54 -04:00

9819626459

fix(gateguard): preserve quoted git introspection args

luyua9 · 2026-05-19 13:24:17 -04:00

14d88e517b

docs(release): refresh hypergrowth evidence

Affaan Mustafa · 2026-05-19 13:17:23 -04:00

8bf4de56b2

feat(install-targets): add claude-project (per-project Claude Code) adapter

Completes the install-target matrix for Claude Code. Until now, ECC's
Claude support was home-scope only (~/.claude/) via the `claude` target.
This adds a project-scope counterpart (./.claude/) via a new
`claude-project` target so teams can install ECC per-repo without
contaminating ~/.claude/ — matching the existing project-scope adapters
for Cursor, Antigravity, Gemini, CodeBuddy, Joycode, and Zed.

Symmetric with `claude`:
- Same namespace under rules/ecc and skills/ecc
- Same docs/<locale> handling for --locale
- Same hooks placeholder substitution for hooks.json
- Reuses claude-home's destination-mapping logic 1:1

Use cases:
- Monorepos with multiple Flow-managed projects
- Teams that want ECC scoped per-project without touching ~/.claude/
- Per-project skill/rule isolation when global install isn't desirable

No breaking change: existing --target claude continues to route to
claude-home (user-scope) unchanged. New target is opt-in.

Tests
-----
- 4 new tests in tests/lib/install-targets.test.js
  (root resolution, lookup-by-id, plan parity with claude, foreign-path filtering)
- All install-target regression guards (schema enum / SUPPORTED_INSTALL_TARGETS)
  still pass
- End-to-end smoke: `--target claude-project --profile minimal --dry-run`
  emits 359 ops with destinations rooted at <projectRoot>/.claude/ (parity
  with --target claude which emits 359 ops rooted at ~/.claude/)

Mhd Ghaith Al Abtah · 2026-05-19 12:14:27 -04:00

7004a66243

docs: sync may 19 linear readiness evidence

Affaan Mustafa · 2026-05-19 11:06:56 -04:00

ac7434ea8f

Track owner approval packet in dashboard

Affaan Mustafa · 2026-05-19 10:40:31 -04:00

c7d662c3c6

chore: add release owner approval packet (#2001 )

Affaan Mustafa · 2026-05-19 10:18:22 -04:00

8148340ad1

chore: refresh suite count evidence (#2000 )

Affaan Mustafa · 2026-05-19 09:58:53 -04:00

e7a7b2aaa3

chore: refresh video dashboard evidence (#1999 )

Affaan Mustafa · 2026-05-19 09:39:10 -04:00

3304848beb

chore: add release video visual qa

Affaan Mustafa · 2026-05-19 09:16:35 -04:00

b62f80750d

chore: gate release video publish candidates

Affaan Mustafa · 2026-05-19 08:54:50 -04:00

855e8c8336

chore: add release video self-eval gate

Affaan Mustafa · 2026-05-19 08:35:02 -04:00

f3cd006252

docs: refresh May 19 operator dashboard

Affaan Mustafa · 2026-05-19 08:13:26 -04:00

d135e03da0

docs: refresh May 19 publication evidence

Affaan Mustafa · 2026-05-19 07:53:51 -04:00

c07276a347

docs: add ECC 2 growth outreach pack (#1993 )

Affaan Mustafa · 2026-05-19 07:33:41 -04:00

7a0645ed47

chore: gate ECC release video suite (#1992 )

Affaan Mustafa · 2026-05-19 07:13:52 -04:00

e209afc8c1

chore: gate canonical ECC release identity (#1991 )

Affaan Mustafa · 2026-05-19 06:42:17 -04:00

8141f6904f

feat: extend harness audit integration scoring (#1990 )

Salvages the useful harness-audit scoring work from #1989 while preserving the current hook registry and newer plugin install detection. Adds GitHub integration checks, conditional deploy-provider categories, dynamic applicable category metadata, and CODEOWNERS coverage.

Affaan Mustafa · 2026-05-19 06:20:54 -04:00

af9b2c1c4c

fix(hooks): avoid escaped quotes in plugin bootstrap

Generate the inline hook root resolver with single-quoted JavaScript literals so Windows Git Bash does not choke on nested escaped double quotes before Node starts. Refresh hooks.json and add regression coverage for parsed hook commands and installed hook manifests.

Affaan Mustafa · 2026-05-19 05:15:42 -04:00

6cb194a3c6

fix(hooks): use shared renameWithRetry in writeWarnState (ecc-context-monitor)

Mirror the previous commit's Windows-EPERM retry on the companion
`writeWarnState` in `scripts/hooks/ecc-context-monitor.js`. Same
race: two PostToolUse subprocesses writing concurrent debounce
state racing on `MoveFileExW`, target-in-use throwing EPERM on
Windows even though each writer's tmp path is now unique.

Implementation: import `renameWithRetry` from `scripts/lib/session-bridge.js`
(exported in the previous commit) instead of duplicating the helper.
The retry policy, backoff schedule, and main-thread `Atomics.wait`
strategy stay identical to `writeBridgeAtomic`.

Three writers in the repo now share the same atomic-write contract:
- `writeBridgeAtomic` (scripts/lib/session-bridge.js) — round 1 +
  this round's retry
- `writeWarnState` (this file) — round 1 + this round's retry via shared helper
- `writeCostWarningIfChanged` (scripts/hooks/ecc-metrics-bridge.js) —
  out of scope for this PR (already uses unique tmp suffix; a future
  consolidation could move it to the shared helper too).

Local: `yarn test` green, `yarn lint` clean. The companion test
suite for `ecc-context-monitor.js` does not currently exercise
concurrent `writeWarnState` writes, but the helper it now uses is
covered by the `tests/lib/session-bridge.test.js` concurrent-write
regression added in round 1's last commit.

Jamkris · 2026-05-19 04:57:10 -04:00

f93e8f6869

fix(lib): retry rename on Windows EPERM/EACCES/EBUSY in writeBridgeAtomic

PR #1983 round 1 introduced unique-suffix tmp paths so two concurrent
writers no longer share a single `.tmp` file. That fix is correct
under POSIX semantics — `rename(2)` is atomic between source and
destination, so each writer renames onto the same target without
conflict.

Windows `MoveFileExW` is not the same. It fails with
EPERM / EACCES / EBUSY when the target is currently being renamed
by *another* process — a short race window that fires reliably under
this hook's PostToolUse + statusline concurrency. Round 1's CI run
made this visible:

  Test (windows-latest, Node 18.x, npm) — FAILURE
  Error: EPERM: operation not permitted, rename
    'C:\…\ecc-metrics-test-bridge-race-….json.9504.4aef575a.tmp' ->
    'C:\…\ecc-metrics-test-bridge-race-….json'
      at writeBridgeAtomic (scripts/lib/session-bridge.js:79:8)

All nine Windows matrix cells (Node 18 / 20 / 22 × npm / pnpm / yarn)
hit the same path. POSIX matrices (Linux + macOS) passed unchanged.

Fix: extract a `renameWithRetry(tmp, target)` helper that retries
`fs.renameSync` up to 5 times on EPERM / EACCES / EBUSY with
exponential backoff (20 ms → 320 ms total). Other error codes
(ENOENT, ENOSPC, EROFS, …) re-throw on the first attempt — they are
not transient. POSIX runs hit the first try and exit immediately.

The backoff uses `Atomics.wait` on a throwaway `SharedArrayBuffer`
so the retry path does not busy-spin the CPU; verified on Node ≥ 17
that this works on the main thread. There is a `try/catch` fallback
to a brief busy-wait for older runtimes where `Atomics.wait` is
restricted to workers.

`writeBridgeAtomic` calls the helper instead of `fs.renameSync` and
keeps its existing best-effort tmp cleanup on terminal failure.

`renameWithRetry` is added to `module.exports` so the companion
`writeWarnState` in `scripts/hooks/ecc-context-monitor.js` can
adopt the same retry policy without duplicating the helper. That
adoption lands in the next commit.

Local: `node tests/lib/session-bridge.test.js` 14/14, `yarn test`
green, `yarn lint` clean. The round-1 test (two concurrent child
writers, 200 iterations each) now passes on macOS without retrying
at all (POSIX path) and is expected to pass on Windows via the new
retry loop.

Jamkris · 2026-05-19 04:57:10 -04:00

116e61d8cb

fix(hooks): use unique tmp suffix in writeWarnState (ecc-context-monitor)

Mirror the previous commit's `writeBridgeAtomic` fix on the
companion `writeWarnState` in `ecc-context-monitor.js`. Same shape:
fixed `${target}.tmp` → `${target}.${process.pid}.${randomNonce}.tmp`,
plus best-effort cleanup of the tmp file on `renameSync` failure
(throws original error after cleanup).

`writeWarnState` debounces the context-monitor's threshold alarms
(`COST_NOTICE_USD`, `COST_WARNING_USD`, `COST_CRITICAL_USD`, plus the
context-remaining and loop-detection ones). Without unique suffixes,
two PostToolUse subprocesses racing on the warn-state file produce
either a corrupted JSON debounce-state on disk or an ENOENT throw
that the hook catches and swallows — either way the next warn-state
read returns the default `{callsSinceWarn: 0, lastSeverity: null}`
and the threshold alarms re-fire or stop firing erratically. Users
see warning messages flicker or vanish; debounce no longer works.

Three call sites in this repo now share the same atomic-write
contract:
- `writeBridgeAtomic` (scripts/lib/session-bridge.js) — primary
- `writeCostWarningIfChanged` (scripts/hooks/ecc-metrics-bridge.js) — cost cache
- `writeWarnState` (this file) — debounce state

`yarn lint` clean. Regression test covering both `writeBridgeAtomic`
and `writeWarnState` under concurrent load lands in the next commit.

Jamkris · 2026-05-19 04:57:10 -04:00

7c2f71315b

fix(lib): use unique tmp suffix in writeBridgeAtomic to eliminate ENOENT race

`writeBridgeAtomic` wrote to a fixed `${target}.tmp` path before
calling `renameSync`. When two processes write to the same session
bridge concurrently (e.g. PostToolUse `ecc-metrics-bridge` + the
background `ecc-statusline`, both calling `writeBridgeAtomic(sessionId, ...)`),
the canonical atomic-rename race fires:

  1. Process A: writeFileSync(target.tmp, JSON_A) — tmp file exists.
  2. Process B: writeFileSync(target.tmp, JSON_B) — tmp file overwritten.
  3. Process A: renameSync(target.tmp, target) — succeeds; target = JSON_B
     (A's payload silently corrupted en-route).
  4. Process B: renameSync(target.tmp, target) — throws ENOENT (the
     rename consumed the file).

Every caller in the repo wraps `writeBridgeAtomic` in `try {} catch {}`,
so the ENOENT exception is swallowed and the user-visible symptom is
just "the bridge file occasionally contains the wrong process's
payload" with no diagnostic.

Reproduced before this commit:

  $ # two concurrent writers, each calling writeBridgeAtomic 500 times
  $ # against the same session ID
  [A] errors=244   # 244 ENOENT exceptions swallowed
  [B] errors=248   # ditto

After this commit the same workload reports 0 errors in both
subprocesses: tmp paths no longer collide.

Fix: change `${target}.tmp` to
`${target}.${process.pid}.${crypto.randomBytes(4).toString('hex')}.tmp`,
matching the pattern already used by `writeCostWarningIfChanged` in
`scripts/hooks/ecc-metrics-bridge.js` (commit 9b1d8918). The pid +
4-byte nonce gives each writer process a distinct tmp path, so step 2
above no longer overwrites step 1's payload and step 4 no longer
races step 3.

Also added: on `renameSync` failure, attempt `fs.unlinkSync(tmp)` so
a writer that fails (disk full, permission, parent dir gone) does
not leak its tmp file. The cleanup is best-effort and the original
error is still re-thrown.

**Scope clarification.** This commit closes the atomic-rename
primitive's race only. The *read-modify-write* race in callers —
two writers each read the same bridge state, increment, and write
back, the second clobbering the first — is a separate concern that
needs locking or per-writer logs, and is intentionally out of scope
for this PR. The cost-tracker / metrics-bridge callers tolerate
last-writer-wins on their cumulative aggregates today and this
commit does not change that contract.

The companion `writeWarnState` in `ecc-context-monitor.js` has the
same fixed-suffix pattern and the same race; that fix lands in the
next commit so each can be reviewed against its own diff.

Jamkris · 2026-05-19 04:57:10 -04:00

28548f67ba

fix(ci): cover other widely-cited invisible code points in check-unicode-safety

Extend `isDangerousInvisibleCodePoint` with five additional code
points / ranges that are routinely cited in invisible-character
smuggling references but were not in the previous denylist:

- **U+180E** MONGOLIAN VOWEL SEPARATOR. Formerly classified as a
  space separator (Zs) until Unicode 6.3 reclassified it as Cf
  (Format control). Renders as zero-width; widely abused for
  homograph attacks and prompt smuggling.

- **U+115F** HANGUL CHOSEONG FILLER and **U+1160** HANGUL JUNGSEONG
  FILLER. Zero-width fillers used in Korean text shaping. Both are
  cited as common LLM-injection vectors in Korean / multilingual
  threat models.

- **U+2061–U+2064** invisible math operators (FUNCTION APPLICATION,
  INVISIBLE TIMES, INVISIBLE SEPARATOR, INVISIBLE PLUS). Zero-width
  and only meaningful inside math typesetting. No legitimate
  Markdown or source code uses them.

- **U+3164** HANGUL FILLER. Reported in real-world Discord and
  Twitter smuggling incidents; not used in legitimate Korean text.

Reproduced before this commit: a file containing any one of these
code points passed `check-unicode-safety.js` silently.

After this commit each one is reported as
`dangerous-invisible U+<HEX>` and `--write` mode strips it.

Verified by writing 8 single-character probe files
(`probe-0x180E.md`, `probe-0x115F.md`, …) and confirming exit=1 with
each violation listed.

ECC repo self-scan reports only the pre-existing `U+2605` BLACK
STAR warnings (unchanged) and exits with the same status (no new
in-repo violations introduced). Existing 5 unicode-safety tests
still pass; `yarn lint` clean.

Regression coverage for both the previous commit's Tag block fix
and this commit's additions lands in the next commit.

Jamkris · 2026-05-18 21:20:36 -04:00

b068069b9b

fix(ci): cover Unicode Tag block (U+E0000–U+E007F) in check-unicode-safety

`isDangerousInvisibleCodePoint` enumerated seven ranges of invisible/
bidi/variation-selector code points but omitted the Unicode Tag block
(U+E0000–U+E007F). Tag characters were proposed for language tagging
in Unicode 3.1 and have been deprecated since Unicode 5.1, so no
legitimate text uses them. They are the canonical vector for
"ASCII Smuggling" / "Tag Smuggling" LLM prompt injection: an attacker
hides instructions inside an ASCII-looking string, the model reads
the tag bytes, the human reviewer sees nothing. Demonstrated against
multiple LLM assistants during 2024–2025.

`check-unicode-safety.js` is the repo's last line of defence before
contributor content reaches agent context; the same script also runs
in `--write` auto-sanitize mode on `.md` / `.mdx` / `.txt`. Today it
silently passes tag-block characters through unchanged in both
detection mode and `--write` mode.

Reproduced before this commit:

  $ mkdir -p /tmp/uni-test && node -e "
      const fs = require('fs');
      const hidden = [...Array(5)].map((_,i) =>
        String.fromCodePoint(0xE0041 + i)).join('');
      fs.writeFileSync('/tmp/uni-test/innocent.md',
        '# Title\\n\\nBenign text' + hidden + ' more.\\n');"

  $ ECC_UNICODE_SCAN_ROOT=/tmp/uni-test \
      node scripts/ci/check-unicode-safety.js
  Unicode safety check passed.
  $ echo $?
  0

Expected: tag-block characters reported as `dangerous-invisible`
violations (exit 1) and stripped under `--write`.
Actual: validator passes, `--write` leaves the bytes intact.

Fix: extend the denylist with one new range
`(codePoint >= 0xE0000 && codePoint <= 0xE007F)`. The change is
purely additive; the existing seven ranges are untouched.

After this commit the same reproduction returns:

  $ ECC_UNICODE_SCAN_ROOT=/tmp/uni-test \
      node scripts/ci/check-unicode-safety.js
  Unicode safety violations detected:
  innocent.md:3:12 dangerous-invisible U+E0041
  innocent.md:3:14 dangerous-invisible U+E0042
  innocent.md:3:16 dangerous-invisible U+E0043
  innocent.md:3:18 dangerous-invisible U+E0044
  innocent.md:3:20 dangerous-invisible U+E0045
  exit=1

`--write` mode also strips the bytes (verified: file length 47 → 42
after sanitize, regex `/[\u{E0000}-\u{E007F}]/u` no longer matches).

Existing 5 unicode-safety tests still pass; `yarn lint` clean. The
ECC repo's own self-scan (`node scripts/ci/check-unicode-safety.js`
with no `ECC_UNICODE_SCAN_ROOT`) reports the same warnings as before
this commit and exits with the same status (no regressions on
in-repo content).

A handful of other widely-cited invisible code points are missing
from the denylist (`U+180E`, `U+115F`, `U+1160`, `U+2061–U+2064`,
`U+3164`); those are addressed in the next commit so each fix
remains independently reviewable. Regression coverage for both
fixes lands two commits later.

Jamkris · 2026-05-18 21:20:36 -04:00

e3483fda15

docs: narrow ecc tools billing blocker

Affaan Mustafa · 2026-05-18 16:45:31 -04:00

cb81f1b0fe

docs: refresh release blockers evidence

Affaan Mustafa · 2026-05-18 15:23:48 -04:00

0f1775e30b

security: scope release oidc publishing

Affaan Mustafa · 2026-05-18 13:41:10 -04:00

7911af4a39

fix: treat MCP HTTP 406 probes as reachable

Affaan Mustafa · 2026-05-18 12:48:52 -04:00

386326df8e

docs: refresh publication readiness gate

Affaan Mustafa · 2026-05-18 10:49:49 -04:00

b41e6fb3d0

docs: mirror agentshield fleet ticket evidence

Affaan Mustafa · 2026-05-18 10:24:21 -04:00

2ba0c62d8a

test: enforce release publication checklist in readiness gates

Affaan Mustafa · 2026-05-18 09:10:51 -04:00

680aeff0fb

docs: record owner-wide queue cleanup

Affaan Mustafa · 2026-05-18 06:16:45 -04:00

08807e7fd6

docs: refresh ecc tools billing blocker evidence

Affaan Mustafa · 2026-05-18 05:38:14 -04:00

5e8f412cb5

docs: refresh billing readback gate evidence

Affaan Mustafa · 2026-05-18 04:30:09 -04:00

ff3eaff137

docs: mirror target billing readback gate

Affaan Mustafa · 2026-05-18 03:27:42 -04:00

fb4b0c8dce

fix: ignore defensive ioc deny rules

Affaan Mustafa · 2026-05-18 02:29:59 -04:00

04d4d81938

docs: refine billing readback dashboard blocker

Affaan Mustafa · 2026-05-18 02:03:37 -04:00

e53933de1b

docs: mirror marketplace billing provenance gate

Affaan Mustafa · 2026-05-18 00:36:01 -04:00

c276639bc7

docs: mirror billing kv readback gate

Affaan Mustafa · 2026-05-18 00:00:37 -04:00

34cc0c1856

docs: add rc1 release URL ledger

Affaan Mustafa · 2026-05-17 23:08:53 -04:00

81fca2cea6

test: align dashboard fixture with May 18 evidence

Affaan Mustafa · 2026-05-17 22:29:06 -04:00

d14191bed8

test: point platform audit at May 18 evidence

Affaan Mustafa · 2026-05-17 22:22:02 -04:00

5475db4f97

docs: add May 18 readiness evidence

Affaan Mustafa · 2026-05-17 22:19:42 -04:00

ec171300c6

460 Commits