Run 26566803068 created project_routing_snapshots successfully on prod (CREATE TABLE
+ partitions + RLS + GRANTs all committed). Marker INSERT into migrations table
failed: "there is no unique or exclusion constraint matching the ON CONFLICT specification"
because Laravel's migrations table has no UNIQUE on `migration` column.
Replaced with INSERT...SELECT WHERE NOT EXISTS for idempotency.
Table is now LIVE on prod — next workflow run will skip the CREATE block (TABLE_EXISTS
check passes) and go straight to the now-fixed marker INSERT.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Workflow run 26564909645 failed: migration 2026_05_27_120000_create_project_routing_snapshots_table
hit 'SET ROLE crm_migrator' failure (pgsql conn = crm_app_user, not member of crm_migrator).
Failed SET ROLE poisoned transaction → subsequent CREATE TABLE failed SQLSTATE[25P02].
Fix in deploy.yml:
New step 'Pre-apply partitioned migrations via postgres superuser' runs CREATE TABLE
+ indexes + RLS + GRANTs + partitions + system_settings insert via sudo -u postgres psql,
then marks migration as ran in migrations table. Idempotent (checks both migrations
table AND information_schema). Established prod pattern (memory: paused_at migration 26.05).
Side fix in tools/enforce-override-limit.test.mjs:
CLI e2e tests used 'node tools/enforce-override-limit.mjs' without cwd, failed when
vitest ran from app/. Added cwd: projectRoot via fileURLToPath(import.meta.url).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Workflow run 26564332893 failed at 14s — most likely npm ci hit Histoire/Vite
peerDep conflict (quirk #74 in feedback_environment.md). --legacy-peer-deps
mirrors local install pattern. Also bumped to Node 22 (Node 20 actions deprecated).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Pure regex/JSON, 0 LLM calls. 4 Vitest tests GREEN. Per ADR-011 + spec §6.1.
Smoke run surfaces REAL drift (DONE_WITH_CONCERNS — plan B5 said «that's
a real signal, document, don't fix here»): 9 plugins in
~/.claude/settings.json enabledPlugins NOT formalized by exact
«name@source» string in Tooling Прил. Н:
- frontend-design@claude-plugins-official (informally as #30
«Frontend Design plugin»)
- 8× ToB plugins @trailofbits (differential-review, audit-context-
building, supply-chain-risk-auditor, insecure-defaults, sharp-
edges, static-analysis, variant-analysis, agentic-actions-auditor)
informally as #39 «Trail of Bits Skills»
This is naming-vocabulary mismatch (Tooling uses human-readable
names; settings.json uses machine names). Not architectural drift.
Resolution options for follow-up:
- Add machine names as «external_id» attribute to Tooling Прил. Н rows.
- Add tools/.l1-watcher-aliases.txt with accepted machine→human map.
Until resolved: C1 will FAIL on lefthook (C5 wiring) — addressed in
C5 by adding alias mechanism OR temporarily downgrade to WARN.
Also fixed CLI guard bug in observer-stop-hook.mjs (B3) and l1-watcher
— old guard `import.meta.url === \`file://\${argv[1]}\`` did not match
on Windows (file:/// triple-slash vs file:// double-slash + relative
argv[1]). New guard: argv[1].endsWith('/<filename>.mjs').
Weekly GH Actions cron (Mon 09:00 MSK) opens issue on drift.
Vitest config extended to ../tools/*.test.mjs with exclude for ruflo-*
and subagent-prompt-prefix tests (pre-existing, not part of brain
governance).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Дмитрий