Spec для фикса root-cause обнаруженной 26.05.2026 при разборе скриншота
админки поставщика: 11 из первых 12 наших проектов в crm.bp-gr.ru имеют
name без префикса B1_/B2_/B3_, в то время как старые ручные — с префиксом.
Корень в SupplierPortalClient::toPayload() строка 468: name=uniqueKey
без префикса. Допущение портал префиксует сам автоматически (комментарий
2026-05-19, recon Playwright) не подтверждено живым listProjects.
Решения брейншторма (заказчик подтвердил):
- toPayload префиксует name через helper prefixedName():
"B<n>_<uniqueKey>" если platforms содержит ровно 1 элемент,
иначе throw LogicException (инвариант 1 POST = 1 платформа).
- saveProjectMultiFlag реструктуризируется: один POST со всеми
srcrt+srcbl+srcmt -> N последовательных POST'ов, по одному на платформу,
external_id из ответа rt-project-save напрямую.
- updateProject без изменений сигнатуры -- уже вызывается per-platform,
через тот же toPayload автоматически реализует нормализацию на лету
для 11 legacy без префикса.
- partial-failure не откатываем: Laravel job retry создаст возможные
дубли, чистим вручную (флоу отработан 26.05).
- К1 учебник вебмастера НЕ правим в этом скоупе.
- AjaxProjectChannel read-side не трогаем -- 26.05 фикс DIRECT для
legacy продолжает работать естественно.
Tests: unit для toPayload, feature для saveProjectMultiFlag с моком HTTP,
live smoke на боевом через UI Лидерры + tinker listProjects.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Brain-retro #5 candidate C, hole 8: ~/.claude/runtime/override-usage.jsonl
logged every override-vocab use but no surface analyzed frequency. 18x
recovery in lifetime was hidden until manual inspection.
New module tools/enforce-override-monitor.mjs computes per-phrase totals
plus today's count; warns (warning) at >=5/day per phrase (configurable).
Wired into tools/status-md-generator.mjs as a new '## Использование
override-фраз' block.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Brain-retro #5 surfaced a correlation: long sessions (≥50 turns) correlate
with discipline drift. Reviewer pass showed regulated rate dropped 19% →
4.5% during a long session.
This commit adds:
• computeSessionLengthBlock(episodes, opts?) — pure function that
groups today's (UTC) episodes by task_id, finds the MAX session_turn
per session, and surfaces sessions with ≥threshold turns (default 50)
in a markdown block.
• Wire-up in renderStatus + main CLI: new "## Длинные сессии" section
inserted between disciplineBlock/activeProjects and costBlock.
• 7 new unit tests (36/36 total green).
Behavior:
• No sessions today → ✅ "Ни одной сессии с >50 ходов".
• One+ flagged → ⚠️ table { session_id, max turn, regulated %, last episode ts }.
• Custom threshold via opts.threshold.
Per memory project_enforce_hard_rules.md: this is an indicator, not a hook;
no blocking, just observability. Owner can decide whether to restart when
regulated % drops in a long session.
Found via TDD that supplier_leads has its own platform CHECK constraint
(chk_supplier_leads_platform) and that the seed migration was missing
NOT NULL columns (accepts_types, channel). Migration now:
- widens supplier_projects/project_supplier_links/supplier_leads.platform
VARCHAR(4) → VARCHAR(8) (DIRECT is 6 chars)
- extends three CHECK constraints to include 'DIRECT'
Seed migration uses raw SQL INSERT to properly serialize PG ARRAY type
for accepts_types column. channel='sites' (valid per suppliers_channel_check).
db/schema.sql synced — 3 platform columns and 3 CHECK constraints updated.
CHANGELOG_schema.md entry pending Task 9.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
LedgerService::resolveSupplierId returns suppliers.code='direct' row for
DIRECT-platform supplier_projects (and for parsed-from-payload non-B
projects). CsvReconcileJob::extractPlatform now classifies most non-empty,
non-junk project strings as DIRECT (instead of dumping them into
unparseable_count) — this allows CSV recovery to also create DIRECT
supplier_leads, mirroring the webhook path.
CsvReconcileJobTest junk-rows fixtures updated: previously used callback
phone-number-as-project (79135551234) and URL-like strings as 'junk', but
those are now valid DIRECT identifiers. Replaced with truly junk strings
matching only outside-whitelist symbols (e.g. '???', '!@#').
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
parseProjectField() returns ('DIRECT', signal_type, identifier) when project
has no B-prefix; identifier-detection (call/site/sms regex) runs on full
project string. LeadRouter::matchEligibleProjects has a DIRECT fast-path
that matches Liderra projects by (signal_type, signal_identifier) directly
without requiring project_supplier_links pivot — because DIRECT
supplier_projects are auto-created on first webhook and don't have manual
psl links.
B1/B2/B3 path unchanged (psl-based via project_supplier_links).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Drops regex /^B[123]_.+$/ from project field validation; parsePlatform()
returns 'DIRECT' for projects without B-prefix (instead of silent fallback
to 'B1'). SupplierProjectResolver ALLOWED_PLATFORMS extended to include
DIRECT.
Closes ~67 of 82 lost leads/day for tenant client1 (observed 2026-05-25):
mostly client.carmoney.ru (55), B2_Caranga (7), cabinet.caranga.ru (3),
cashmotor.ru (2), numeric callback IDs (~10).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
TDD found that 'DIRECT' (6 chars) does not fit in VARCHAR(4). Three columns
need widening: supplier_projects.platform, project_supplier_links.platform,
supplier_leads.platform. supplier_manual_sync_queue.platform was already
VARCHAR(8). Done in the same migration as CHECK extension — single
atomic deploy.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
LedgerService::resolveSupplierId will look up suppliers WHERE code='direct'
for DIRECT-platform supplier_projects (Phase 3). cost_rub matches B1 (same
supplier company, different lead-routing channel).
Spec: docs/superpowers/specs/2026-05-25-supplier-webhook-reliability-design.md
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Adds early merge check in RouteSupplierLeadJob::createDealCopyForProject:
when lead.vid IS NOT NULL and an existing deal with NULL source_crm_id
exists for (tenant, phone, project_id) within last 24h, UPDATE that
deal's source_crm_id instead of creating a second Deal. INSERT into
supplier_lead_deliveries links the new supplier_lead.id to the existing
deal.id. LedgerService::chargeForDelivery is NOT called — the original
charge happened when the csv-recovery created the deal.
Closes 37 duplicate deals observed on prod for tenant client1 25.05.2026.
Spec B Phase 1 (commit ccfecd5e) removed DuplicateDetector — this fix
restores idempotency for the specific webhook-after-csv-recovered case
WITHOUT re-blocking intentional supplier repeats with different vids.
Guard: only merges where source_crm_id IS NULL (the CSV-recovered marker).
Two webhooks with different vids on same phone+project still create two
deals — by-design per Spec B.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Adds withExceptions render callback for ValidationException that forces
JSON 422 response when request matches api/webhook/supplier/* — regardless
of Accept header. Default Laravel behavior is 302 redirect for non-JSON
clients, which strips POST body.
Observed on prod 2026-05-25: 76 of 234 supplier webhook hits got 302 (Location: /),
mostly for non-B-prefix projects (client.carmoney.ru, cabinet.caranga.ru,
cashmotor.ru). Supplier doesn't follow 302 redirects on POST, so the
lead body is lost. This fix ensures supplier always sees a meaningful
422 with errors[] instead of a redirect.
Other routes unaffected (render returns null for non-webhook URLs).
Investigation 2026-05-25: for tenant client1 (tenant_id=2) on prod liderra.ru:
- 205 leads at supplier (info@lkomega.ru, visit=rt) vs 160 deals on portal
- 82 leads lost (76 via 302-redirect from ValidationException, mostly
non-B-prefix projects: client.carmoney.ru, cashmotor.ru, etc.)
- 37 duplicate deals (CSV-recovered SupplierLead vid=null + later
webhook with real vid "create two Deals because supplier_lead_deliveries
locks on supplier_lead_id, not phone+project)
Three independent fixes, three plans, three deploys:
Phase 1 (low risk): Always JSON 422 for webhook ValidationException
Phase 2 (med risk, billing): merge webhook-after-CSV-recovered into
existing deal, no double-charge
Phase 3 (high risk, migration): accept non-B projects as platform=DIRECT
end-to-end (controller + 4 services + migration)
Phase 3 includes new LeadRouter fallback path: DIRECT-supplier_projects
match Liderra projects via signal_type+signal_identifier directly
(no project_supplier_links pivot required, since psl rows don't exist
for auto-created DIRECT supplier_projects).
Refs: docs/superpowers/specs/2026-05-25-supplier-webhook-reliability-design.md
Append-only journal capture during the factor-analysis bug-surface session.
Episodes contain live tests of the LLM classifier retry logic (10/10 LLM
success rate post-retry) and the prefilter Layer 1 gate on short prompts.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Sync шапок и changelog'ов 3 нормативных файлов под Pravila v1.42
(коммит a2d6feb7 §17.7 «Coverage announcement»). Только cross-refs,
без контентных правок § тел.
- CLAUDE.md: §0 row Pravila v1.41→v1.42; §9 +entry «cross-ref update».
- docs/Tooling_v8_3.md: header cross-ref Pravila v1.41+→v1.42+;
§13 footnote «Прил. Н v2.23 от 25.05.2026 cross-ref update».
- docs/Plugin_stack_rules_v1.md: §0 changelog Pravila v1.39+→v1.42+;
История версий +entry v3.22 (cross-ref update).
Tooling канон счётчиков #1-#83 не тронут (Phase 3 deferred — не
плагины, не агенты). Записи v1.34-v1.41 в §10 Pravila таблице
по-прежнему не дотянуты (известный дрейф предыдущих сессий, вне
этого scope).
Через subagent normative-sync (#84) per Pravila §2.4. Гейт
cross-ref-checker (C2): 0 drift.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Closes Phase 3 deferred follow-up #1 from project_brain_overhaul.md.
Адресует «дыру»: enforcement (§17.4) ловит факт нарушения, но без
явной coverage-пометки в ответе невозможно отличить осознанный
выбор канала от молчаливого среза угла.
- §17.7 (new): «coverage: <channel>:<id>» обязательна на non-conversation
задачах. 6 каналов: skill / node / chain / hook / agent / direct.
Observability layer (не enforcement) — фиксирует НАМЕРЕНИЕ.
- Граница с routing-тегом §16.7: routing-тег только для
user_directed_method, coverage-пометка — всегда для non-conversation.
- C5 controller surface отсутствующих пометок в STATUS.md.
- Cross-ref: registry/nodes.yaml, routing-off-phase.md, парсер
schema v4.4+ (deferred #2).
Header bump v1.41 → v1.42 + §10 changelog row v1.42. Записи v1.34-v1.41
в §10 не дотянуты (известный дрейф предыдущих сессий) — шапка
«Что изменилось в v1.NN» авторитетна для этого периода. Нормативный
синк CLAUDE.md/Tooling/PSR_v1 — следующим шагом через normative-sync.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Phase 2 Task 8 of LLM-first router overhaul.
- tools/router-config.mjs: 4 constants (CLASSIFIER_MODEL='claude-sonnet-4-6',
REVIEWER_MODEL='claude-opus-4-7', INHERITANCE_MAX_AGE_MIN=30,
REVIEWER_MAX_NEIGHBOR_EPISODES=10). Sonnet 4.6 ID resolved via ProxyAPI
/v1/models 2026-05-25 — only alias 'claude-sonnet-4-6' is exposed (no dated
YYYYMMDD form on this reseller); alias is canonical here.
- docs/registry/nodes.yaml: capabilities: line added to all 85 nodes
(1-2 sentences describing what each node DOES, not when to choose it —
classifier infers selection from capabilities + user prompt). Generated
by Sonnet subagent from CLAUDE.md §3.x + Tooling §4.X attribute blocks
+ spec §18.3 format. Spot-checked + verified no forbidden 'use when' framing.
- docs/registry/schema.json: +capabilities top-level node property
(type:string minLength:1). G12 'permissive' note in plan was stale —
schema had additionalProperties:false; explicit extension is the
cleanest compliant path.
Verify (plan Step 2): nodes=85 caps=85, exit 0.
Tests: tools/router-config.test.mjs 4/4 PASS + tools/registry-load.test.mjs
11/11 PASS (Ajv schema-validate on amended schema GREEN).
Phase 1 Task 6 of LLM-first router overhaul. Minimal-scope execution after
reality check (C1/C2 controllers don't track section refs, only version
drift; plan steps about §3.3/R15 archiving are out of scope for cross-ref
update).
Changes:
- CLAUDE.md §0 'Источник истины' row for Pravila: **v1.40 от 24.05.2026**
-> **v1.41 от 25.05.2026** + narrative bump (§12 archived in Task 4,
§17 added in Task 5 via ADR-016).
- docs/Tooling_v8_3.md line 4 cross-ref:
cross-ref Pravila v1.39+ -> v1.41+ (+ CLAUDE.md v2.27+ -> v2.28+).
Deferred (TASKLOG.md Task 6 section for full reasoning):
- §12 textual occurrences in PSR_v1 (39) and historical Tooling/CLAUDE.md
changelog blocks remain as honest historical pointers to the archived
§12 (docs/archive/llm-bootstrap-2026-05/pravila-12/...).
- CLAUDE.md §3.3 archive + nodes.yaml pin — out of scope, requires
structural restructure beyond cross-ref work.
- Tooling §4.X 'когда брать' archive — out of scope.
- PSR_v1 R15 — already removed in v2.0 (motion-runtime removal,
12.05.2026); current R15 is 'Off-phase routing', unrelated to §12.
Verification:
- tools/l1-watcher.mjs: OK — 0 drift.
- tools/cross-ref-checker.mjs: OK — 0 drift in 4 files (was FAILing on
Pravila v1.40 / v1.39 references after Task 5 bump to v1.41).
- npx vitest run tools/: 539 passed (unchanged from Task 4 baseline).
Plan: docs/superpowers/plans/2026-05-25-llm-first-router-overhaul.md Task 6.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Phase 1 Task 2 of LLM-first router overhaul.
Live user-level changes (NOT in git, see TASKLOG.md for full diff manifest):
- ~/.claude/settings.json — removed 2 PreToolUse blocks:
- matcher 'Skill' -> skill-marker.py (§12 trigger marker)
- matcher 'Edit|Write|MultiEdit' -> skill-check.py (§12 enforcement on Edit)
- Remaining PreToolUse: 1 block (economy-state-guard, pure economy)
- ~/.claude/hooks/economy-mode.py — trailer text:
'§12 hard rule из Pravila НЕ override-ится' -> '§17 universal skill-coverage НЕ override-ится'
- ~/.claude/hooks/economy-state-guard.py — NO-OP (no §12 logic; pure economy)
Economy system (0%/5%/25%/50%/75%/100%) remains fully active. Stop-hook
subagent verifier (model: claude-sonnet-4-6) remains. PostCompact, SessionStart
hooks unchanged.
skill-marker.py and skill-check.py files remain on disk in ~/.claude/hooks/
(snapshot already in docs/archive/.../user-hooks/ from Task 1). They are
unwired from PreToolUse — no longer invoked. Task 4 moves them into the
archive proper.
permissions.ask still references skill-marker.py/skill-check.py (4 entries
Edit/Write each) — these gate direct file edits and are harmless. Cleaned
up alongside Task 4 archive.
Verification:
- ~/.claude/settings.json parses as valid JSON (1 PreToolUse block).
- All 4 economy hooks (economy-mode, economy-state-guard, economy-postcompact,
economy-self-check) still run with exit 0.
- Live economy-mode.py with prompt 'тест экономия 5%' returns valid hook
JSON with FIRST LINE '=== ECONOMY MODE: 5%' and trailer mentioning §17.
Rollback: 'node tools/test-rollback.mjs --execute' restores both files
from snapshot (verified e2e in Task 1).
Plan: docs/superpowers/plans/2026-05-25-llm-first-router-overhaul.md Task 2.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Establishes a proven rollback mechanism for the LLM-first router overhaul before
any destructive step. Without this, Phase 1-3 work would be irreversible.
What this commit adds:
- Git tag 'brain-pre-llm-bootstrap' on origin/main 9d4a30c3 (pre-overhaul state).
- docs/archive/llm-bootstrap-2026-05/ archive structure with:
- settings-snapshot/ — pre-overhaul ~/.claude/settings.json + project settings
- user-hooks/ — all 14 ~/.claude/hooks/*.py pre-overhaul (incl. §12 ones)
- runtime-flags-snapshot/ — pre-overhaul ~/.claude/runtime/*-mode.json
- nodes-yaml-archive/ — pre-overhaul docs/registry/nodes.yaml
- tools/test-rollback.mjs — rollback planner + executor (--dry-run / --execute)
- tools/test-rollback.test.mjs — TDD: 3 tests for planRollback() contract
- ROLLBACK.md — operator runbook with from->to manifest
E2E smoke proof was run BEFORE this commit (Task 1 step 9):
1. Created TEMP marker commit on top of tag with a dummy file + runtime flag.
2. Ran 'test-rollback.mjs --dry-run' (OK) then '--execute' (user state restored).
3. Reverted git-tracked state and verified marker + flag gone.
4. Verified Task 1 untracked files survived the rollback.
Smoke discovered a bug in the plan's procedure ('git checkout tag -- .' +
'git reset --soft tag' does NOT delete files committed-after-tag — they stay
staged). ROLLBACK.md uses 'git reset --hard <tag>' instead, which correctly
removes overhaul-added tracked files while preserving untracked artefacts
(episodes-*.jsonl, observer notes).
TDD: 3/3 green on test-rollback.test.mjs. Full vitest tools/: 546 passed (was
543 baseline, +3 from this commit), 4 pre-existing 'No test suite' failures
on tools/ruflo-* and tools/subagent-prompt-prefix.test.mjs (out of scope).
Plan: docs/superpowers/plans/2026-05-25-llm-first-router-overhaul.md Task 1.
Spec: docs/superpowers/specs/2026-05-24-llm-first-router-overhaul-design.md.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
EnsureSaasAdmin fail-closed 503 вне dev/testing → вся админка на боевом
liderra.ru недоступна (все /api/admin/* падали). Настоящий saas-admin SSO
(Yandex 360) ещё не готов (Б-1 + DO-4), но держать зону наглухо закрытой
нельзя — заказчику нужна админка.
Стопгэп (выбор заказчика): защита /admin + /api/admin/* переносится на
nginx (отдельный HTTP Basic Auth, /etc/nginx/.htpasswd-admin), middleware
зону больше не закрывает. Тест production-кейса переведён с 503 на 200.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
v2.0 → v2.1 — 3 группы изменений (16 пунктов суммарно):
Группа 1 — решения принятые после v2.0, не внесённые:
- 1.1 Памятка classifier (4 паттерна: brainstorming / discovery-interview /
writing-plans / systematic-debugging). +flag prompt-enrichment-mode.
- 1.2 Reviewer как полноценный Claude Code subagent (tools=[Read,Grep,Glob,
Skill], model=opus). Новый файл .claude/agents/reviewer-agent.md.
+стоимость $240-1200/мес vs $40-80 direct API. Crash fallback на direct
API. Context bloat cap 10 соседних эпизодов.
- 1.3 Inheritance + 3 группы коротких prompt'ов (continuation/acknowledgment/
cancellation) + 30-минутный таймаут. +flag inheritance-mode. Новые поля
в schema v4.1: inherited_from_task_id, inheritance_age_minutes,
previous_direction_rejected, previous_task_id_rejected.
Группа 2 — edge cases:
- 2.1 Reviewer model явно opus в agent file.
- 2.2 Reviewer subagent crash → fallback direct API call.
- 2.3 Reviewer context bloat: max 10 episodes в agent system prompt.
- 2.4 Manual override приоритет №1 в prefilter (раньше inheritance).
- 2.5 Cancellation clears state + previous_task_id_rejected marker.
Группа 3 — мелкие упущения:
- 3.1 brain-retro SKILL.md description: раз в 1-2 недели (не sprint).
- 3.2 recommended_chain_id nullable для custom chains.
- 3.3 Embedding только для non-prefilter эпизодов.
- 3.4 PII filter wraps sanity-check comments.
- 3.5 requested_node fuzzy matching fallback.
- 3.6 Anchor word list inline initial.
- 3.7 Self-retrospect counter init в фазе 3 step 3.3.
- 3.8 Sanity-check answer file schema_version=1.
Cost rewrite: 720-1380 USD (v2.0) -> 1940-8200 USD (v2.1) на 6 месяцев
из-за reviewer subagent. Granular rollback через reviewer-mode=direct-api
возвращает к v2.0 ценам.
§21 новый — changelog v2.0 → v2.1 со всеми 16 пунктами и где правка.
Реализация — после закрытия Биллинга v2 Спек C.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
readRouterState(sessionId, {baseDir}) -- pure read state-файла сторожа.
extractRouterFields(state) -- pure извлечение 4 полей для primary_rationale.
Используется парсером эпизодов на следующем шаге (Task 3).
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
3-task TDD-ish plan to create two new project agents:
- Task 1: .claude/agents/normative-sync.md (full Sonnet 4.6 system prompt)
- Task 2: .claude/agents/prod-deploy-validator.md (8 SSH checks + quirks 104-108)
- Task 3: First dry-run smoke test for both + capture lessons in memory
Spec: docs/superpowers/specs/2026-05-24-controller-offload-agents-design.md (71a5dd6).
Also: +2 cspell-words (маппинге, dogfooded).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Дмитрий