654 Commits

• 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
• fix(learning): add project registry maintenance
  Affaan Mustafa · 2026-05-19 12:51:18 -04:00
  bc519e5b8e
• test(install-targets): add positive rules assertion to claude-project foreign-path test

  Addresses CodeRabbit review: the negative-only assertions could have
  passed on an empty plan. Add a positive assertion that the non-foreign
  'rules' path is still planned under .claude/rules/ecc so regression to
  zero ops would fail loudly.

  Mhd Ghaith Al Abtah · 2026-05-19 12:14:27 -04:00
  b2c2616ab4
• 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
• Fix release supply-chain evidence gate
  Affaan Mustafa · 2026-05-19 11:59:42 -04:00
  27e4036075
• 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
• docs: define ECC 2.0 hypergrowth release lane

  Refresh the active 2.0 release surface for the affaan-m/ECC repo identity, update package/plugin/workflow launch metadata, and add an operator command center for release video, partner, sponsor, consulting, and social launch execution.

  Affaan Mustafa · 2026-05-19 05:42:38 -04:00
  9ee1e15564
• 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
• test(lib): make concurrent-write test actually concurrent + use regex matcher for assert.throws

  Two round-1 review findings in `tests/lib/session-bridge.test.js`,
  both about test correctness rather than the underlying fix:
  
  1. **greptile P1 + coderabbitai Major + cubic P2 (all three): concurrent-write test ran sequentially.**
  
     The test spawned two child processes with two consecutive
     `spawnSync` calls. Because `spawnSync` blocks until the child
     exits, the second writer started *after* the first finished —
     the two writers never overlapped, so the rename race the fix
     targets was never actually exercised. The test would have passed
     with the old broken `${target}.tmp` suffix.
  
     Fix: introduce a one-off "race runner" helper that runs inside
     its own subprocess and uses async `spawn` to start both writers
     simultaneously. The runner waits for both to exit (the event
     loop is local to the runner subprocess, so this stays compatible
     with the synchronous test harness used elsewhere in this file)
     and reports both exit codes plus stderrs on stdout. The test
     then calls the runner via `spawnSync` and parses the result.
     Both writer children now overlap for the duration of their 200
     `writeBridgeAtomic` calls each, which is enough wall time to
     reliably trigger the rename race against the pre-fix code.
  
     Verified: with the fixed `${target}.${pid}.${nonce}.tmp` suffix,
     the test passes; with the old fixed `${target}.tmp` suffix
     reintroduced, it fails as expected (one writer hits ENOENT on
     roughly half its rename calls).
  
  2. **greptile P2 + cubic P3: `assert.throws` used a string as the second argument.**
  
     Node deprecated passing a string as the second argument to
     `assert.throws` years ago: the string is silently treated as
     the assertion failure message (what to print when the function
     does *not* throw) rather than as an error matcher. The check
     passed for any thrown error, not just the rename failure.
  
     Fix: pass a regex matcher as the second arg and keep the
     explanatory text as the third. The regex matches `EISDIR`,
     `EPERM`, `ENOTDIR`, or `ENOENT` because `renameSync` of a
     regular tmp file onto an existing directory raises different
     codes on Linux / macOS / BSD — making the matcher portable
     across CI runners.
  
  Test count unchanged at 14; `npm test` green; `npm run lint` clean.
  
  The two helper files (`tests/__tmp_bridge_writer.js`,
  `tests/__tmp_bridge_race_runner.js`) are written and unlinked
  inside the test's try/finally so they never persist beyond the
  test run.

  Jamkris · 2026-05-19 04:57:10 -04:00
  d904edc615
• test(lib): concurrent writeBridgeAtomic + tmp-cleanup regression

  Two regression tests pin down the previous two commits' atomic-rename
  fixes:
  
  1. **concurrent writes don't throw ENOENT or corrupt the file** —
     spawns two child Node processes (`tests/__tmp_bridge_writer.js`
     created in-test, cleaned up in finally) that each call
     `writeBridgeAtomic(sid, …)` 200 times against the same session
     ID with independent payloads. Asserts both subprocesses exit 0
     (the previous implementation produced ENOENT on roughly 50% of
     rename calls, all swallowed by the in-test catch) and the final
     bridge file is parseable JSON belonging to one of the two writers
     (last-writer-wins is fine; the contract is *no corruption* and
     *no rename ENOENT*, not data preservation).
  
  2. **tmp file cleanup on rename failure** — pre-creates a directory
     at the target bridge path so `renameSync(tmp, target)` fails,
     calls `writeBridgeAtomic`, asserts the call throws AND that no
     tmp file with the writer's `pid.<nonce>.tmp` prefix is left
     behind in `os.tmpdir()`. The previous code had no cleanup; the
     fix's `try/catch + unlinkSync` keeps tmpdir from accumulating
     orphan files across repeated rename failures.
  
  The first test deliberately writes independent payloads from each
  subprocess so this regression doesn't try to claim a property the
  fix doesn't actually deliver (read-modify-write race in the caller
  is a separate issue and out of scope per PR body).
  
  Test count: 12 → 14 in `tests/lib/session-bridge.test.js`;
  `npm test` green; `npm run lint` clean.

  Jamkris · 2026-05-19 04:57:10 -04:00
  5acb01a276
• test(ci): regression coverage for newly-covered invisible code points

  9 new test cases pin down the two previous commits' denylist
  extensions. Each verifies both detection (validator exit non-zero +
  the expected `dangerous-invisible U+<HEX>` line on stderr) and,
  where applicable, `--write` sanitization.
  
  Coverage:
  
  Tag block (commit 1):
  - U+E0041 TAG LATIN CAPITAL LETTER A — the range's printable ASCII
    shadow; this is the byte sequence demonstrated in published ASCII
    smuggling proofs of concept.
  - U+E007F CANCEL TAG — the range end.
  
  Other invisibles (commit 2):
  - U+180E MONGOLIAN VOWEL SEPARATOR
  - U+115F HANGUL CHOSEONG FILLER
  - U+1160 HANGUL JUNGSEONG FILLER
  - U+2061 FUNCTION APPLICATION (range start)
  - U+2064 INVISIBLE PLUS (range end)
  - U+3164 HANGUL FILLER
  
  Detection table is data-driven (one loop, one assertion per row) so
  adding the next invisible to the denylist also gets a paired
  regression test by simply appending to NEWLY_COVERED_RANGES.
  
  Plus a `--write` integration test:
  - writes a markdown file containing both Tag block (5 chars) and
    U+180E, runs `--write`, asserts both removed and surrounding text
    preserved character-for-character ('# Title\n\nBenigntext.\n').
  - re-runs the validator without `--write` and asserts exit 0,
    confirming the sanitizer's output is idempotent under the
    extended denylist.
  
  Test count: 5 → 14 in this file; full `yarn test` green; `yarn lint`
  clean.

  Jamkris · 2026-05-18 21:20:36 -04:00
  33ed494adf
• docs: refresh rc1 publication evidence
  Affaan Mustafa · 2026-05-18 16:12:37 -04:00
  4470e2e670
• docs: refresh release blockers evidence
  Affaan Mustafa · 2026-05-18 15:23:48 -04:00
  0f1775e30b
• docs: add discussion response playbook
  Affaan Mustafa · 2026-05-18 14:39:11 -04:00
  12ac22e674
• test: normalize release workflow line endings
  Affaan Mustafa · 2026-05-18 13:53:26 -04:00
  97567a91e7
• 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
• test: enforce release publication checklist in readiness gates
  Affaan Mustafa · 2026-05-18 09:10:51 -04:00
  680aeff0fb
• docs: add release plugin publication checklist
  Affaan Mustafa · 2026-05-18 08:56:17 -04:00
  6c0fbfb6c5
• docs: finish owner queue cleanup
  Affaan Mustafa · 2026-05-18 06:35:44 -04:00
  cdc92de42a
• docs: record owner-wide queue cleanup
  Affaan Mustafa · 2026-05-18 06:16:45 -04:00
  08807e7fd6
• docs: refresh billing readback gate evidence
  Affaan Mustafa · 2026-05-18 04:30:09 -04:00
  ff3eaff137
• test: stabilize repair lifecycle on Windows
  Affaan Mustafa · 2026-05-18 03:48:51 -04:00
  bf17737969
• 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
• Merge PR #1976 provider response guards
  Affaan Mustafa · 2026-05-18 01:05:37 -04:00
  80f6c27957
• fix: harden openai-compatible provider responses
  Affaan Mustafa · 2026-05-18 01:04:28 -04:00
  eb0d893948