CLI и queue не проходят через SetTenantContext → app.current_tenant_id не выставлен → projects RLS падает 'unrecognized configuration parameter'. Зеркалим SetTenantContext: DB::transaction + SET LOCAL (PgBouncer-safe). Затрагивает initial-sweep + ночной cron @18:00 MSK.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Spec C §3.6/§6.2. Бэкенд: GET /api/billing/balance-status (frozen + capacity + required + дефицит ₽/leads), Pest 6. Фронт: BalanceFrozenBanner (в AppLayout, глобально), BalanceCapacityIndicator (в BillingView под балансом), ProjectLimitOverloadDialog (409-перехват в NewProjectDialog: save-blocked/set-zero), tenantStore + api getBalanceStatus. Vitest +18.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Task 1.9 плана 2026-05-24-billing-v2-spec-c-preflight-vtb.
Разовая artisan-команда для запуска при выкатке Spec C — прогоняет
BalancePreflightSweepJob по всем тенантам, замораживает legacy-
тенантов в минусе. Идемпотентна (sweep-job triggers только на
active↔frozen переходах, стабильное состояние не трогает).
TDD: 1 тест GREEN.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Task 1.7 плана 2026-05-24-billing-v2-spec-c-preflight-vtb.
store/update проверяют преfflight перед созданием/изменением проекта:
- если сумма daily_limit_target всех активных не-blocked проектов
превышает capacity баланса (через BalancePreflightService) и не
передан force_save_blocked=true → возврат 409 с JSON-телом:
{error, current_balance_rub, current_capacity_leads,
would_be_required_leads, deficit_leads}
- если force_save_blocked=true → проект создаётся/обновляется с
preflight_blocked_at=now() (точечная заморозка одного проекта,
не блокирует остальные).
Safe fallback: без активных pricing_tiers — преfflight skipped
(legacy-окружения без настроенного биллинга).
TDD: 4 теста GREEN (409 store / 409 update / force_save_blocked
создаёт blocked / norm pass через capacity).
Регрессия: 0 регрессий на Plan5 ProjectsStoreTest+ProjectsUpdateTest
(37/37 GREEN после safe fallback).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Task 1.6 плана 2026-05-24-billing-v2-spec-c-preflight-vtb.
BalanceFrozenReminderJob — окна 24-48ч (reminder) и 72-96ч (final).
Throttle через balance_freeze_log markers (event_type 'reminder_sent' /
'final_sent') на 5 дней — повторов в окне не будет.
Re-evaluate PreflightResult для актуального дефицита в письме
(клиент мог частично пополнить — reminder покажет обновлённое число).
Schedule @18:30 MSK (после основного sweep @18:00) — если sweep
только что заморозил тенанта, reminder в тот же день не сработает
(окно 24h+ ещё не открыто).
TDD: 4 теста GREEN (reminder/final/skip-fresh/throttle).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
liderra_testing persistent (RefreshDatabase off) — DemoSeeder тенанты
могут попасть в sweep и тоже получить BalanceFrozenMail. Без per-tenant
фильтра Mail::assertNotQueued() ловил 154 фоновых письма и валил тест.
Логика BalancePreflightSweepJob корректна — фикс только в test isolation.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Task 1.4+1.5 Спека C. BalancePreflightSweepJob (chunkById всех тенантов,
переход active->frozen / frozen->active, идемпотентность, журнал balance_freeze_log
через pgsql_supplier) + BillingPreflightSweepCommand + cron billing:preflight-sweep
@18:00 MSK (SyncSupplierProjectsJob сдвинут 18:00->18:05). 4 Mailable
(Frozen/Reminder/Final/Unfrozen) + blade. Job шлёт Frozen/Unfrozen при переходах;
Reminder/Final (T+24h/T+72h) — классы готовы, рассылка по дате — следующий шаг.
11 Phase 1 billing-тестов GREEN. Адаптации под факт схемы: contact_email (не email),
organization_name (не name), is_active+daily_limit_target (не status+daily_limit).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Hygiene commit after consolidated brain-retro #6 follow-up. Captures live
runtime state where the fixes are now visibly working:
- STATUS.md regen reflects 917-test sentinel pass.
- episodes-2026-05.jsonl: +50 lines from this session's turns, including
state with source: llm + non-empty task_cost (A1 live evidence).
- pii-counters.json: counter increments from PII filter scans during retro.
- settings.json: linter-normalized hook order (no semantic change).
- .gitleaksignore: prior staged hash entry from parallel session.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Pre-fix all three regexes in extractTestMetrics fell through when Vitest
output contained " | N skipped" between "passed" and "(TOTAL)" — so any
test suite with .skip()'ed tests produced sentinel result=fail (false
negative), blocking subsequent git commit.
Two new patterns:
- "Tests N passed | M skipped (TOTAL)"
- "Tests X failed | N passed | M skipped (TOTAL)"
Companion tests in tools/enforce-verify-record.test.mjs (new file matches
TDD-gate basename heuristic) and tools/enforce-verify-before-push.test.mjs.
Verified RED to GREEN: 38/38 tests pass after fix.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Brain-retro #6 follow-up #2 (consolidated). Eight independent fixes:
A1 — task_cost wiring (cost tracking)
- router-prehook.mjs: capture classifier LLM usage via onUsage callback,
persist to state.task_cost.classifier_input_tokens / output_tokens.
- observer-transcript-parser.mjs: merge router-state.task_cost on top of
extractTokenUsage(turn). State-file values win for classifier/
self_assessment/reviewer fields.
- New buildCostFromClassifierUsage() exported from router-prehook.
- Verified live: state file now shows real input_tokens=190 /
output_tokens=598 / cache_read=10075 (was 0 before).
A2 — self-assessment coverage
- observer-self-assessment-api.mjs: DEFAULT_TIMEOUT_MS 10s -> 30s.
- .claude/settings.json: Stop-hook timeout 15s -> 60s.
- Same Windows TLS handshake issue. Was 85% no_self_assessment in retro #6.
B3 — brain-retro SKILL.md reconciliation
- Step 5b: batch=default for N>=20, subagent for N<20.
C1 — dead-code cleanup
- Removed recommendNode import + getClassificationMap + getDormancy from
observer-transcript-parser.mjs.
G — parseClassifierResponse Pass 3 (fixLLMJsonQuirks)
- Root cause: real Sonnet output sometimes contains raw newlines inside
string values (multi-line reason_for_choice) and trailing commas, which
strict JSON.parse rejects. Result was llm_error_type=parse_null on
every other call, falling back to regex with task_type=unknown.
- Fix: after Pass 1 (clean) and Pass 2 (brace-extract) fail, try Pass 3
that escapes raw newline/tab inside string values and strips trailing
commas before final JSON.parse attempt. Pure char-walk, no JSON5 dep.
H — 'unknown' added to NON_BLOCKING_TASK_TYPES in router-tool-gate.mjs
- Until G fully proves itself, blocking Bash/Edit on unknown is too strict.
With G in place, parse_null should be rare; H gives a safety net.
Tests added: +9 across 5 test files. Regression: 913 vitest tests in tools/.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Three independent fixes from brain-retro #6 root-cause analysis:
1. **.claude/settings.json** — UserPromptSubmit `router-prehook.mjs` timeout
raised 10s→60s. First fetch on Windows triggers TLS handshake which can
take 20+ seconds; LLM classifier had perAttemptTimeoutMs=30s with 4
retries but the WRAPPING hook timeout killed the process at 10s before
first attempt completed. Result: only 1 of 325 episodes since 24.05
actually classified via Sonnet 4.6 (rest fell to regex fallback or
left state-file untouched).
2. **tools/observer-transcript-parser.mjs:937-959** — removed
`classifMapNode` silent fallback in `primary_rationale.recommended_node`.
When router-state file had no recommended_node, the parser was filling
it with `recommendNode(classifyTask(prompt), ...)` — a keyword-regex
that LOOKED like a classifier signal but wasn't. brain-retro #6
analysis showed 60-70% of «recommended_node» values were just regex
false-positives, polluting the «direct_ignored_rec» metric.
Now recommended_node is null when no real classifier signal exists.
3. **.claude/skills/brain-retro/SKILL.md** — added MANDATORY DIGITAL
ANALYSIS block at the top of Procedure. Every /brain-retro run MUST
emit 7 quantitative tables (path-type, node_chosen, recommended_node,
GAP, outcome×group, classifier presence, per-classification discipline).
Also forbids jargon in sanity questions (per memory
`feedback_plain_language.md`) — owner is non-developer.
Tests:
- tools/observer-transcript-parser.test.mjs — 2 tests updated to assert
recommended_node=null on no-state-file (was '#19'). Confirmed RED
→ fix → GREEN.
- tools/router-classifier.test.mjs — 10 new parametrised tests for
project-vocabulary anchors (webhook/queue/migration/RLS/etc).
Already GREEN with current ANCHOR_NOUNS — prefilter uses len<15
threshold which doesn't catch typical business prompts.
Regression: 899 vitest tests passed (1 file failure pre-existing in
.claude/worktrees/supplier-project-failover/ — empty file, unrelated).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Supplier Snapshot Guard — защита от убытка при удалении/смене источника проекта,
пока поставщик может прислать лиды по уже сделанному слепку.
Spec: docs/superpowers/plans/2026-05-26-supplier-snapshot-guard.md
Brain-retro #5 candidate C, hole 7: the 'ремонт инфраструктуры' phrase
suppressed ALL rule keys with no constraint. Now requires a 'ремонт: <what>'
line in the same prompt documenting the target.
enforce-override-vocab.json: added 'requires_justification: "ремонт:"' to
the entry.
enforce-hook-helpers.mjs findOverride(): honors requires_justification — when
set, the user prompt must contain '<prefix> <non-empty-text>' or the override
is rejected.
Brain-retro #5 candidate C, hole 9: enforce-rationalization-audit.mjs only
logged rationalization phrases (e.g., 'just this once', 'пока без') — never
blocked. Also vocab was sparse.
Changes:
- Expanded vocabulary by 5 phrases: 'давай разок', 'только сейчас',
'один раз без правил', 'на этот раз без', 'я знаю что не надо но'.
- Made decide() accept priorFlagCount; blocks on 3rd flag/session.
- main() reads rationalization-flags-<session>.jsonl to compute count
before calling decide().
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 candidate C, hole 4: enforce-classifier-match.mjs main()
read only state.classification.recommended_node, which is null for
prefilter/regex classifier sources. When triggers_matched[0] contained a
recommendation, the rule was bypassed.
Added fallback: if recommended_node is null, use triggers_matched[0]. decide()
already accepts null confidence on this path (only numeric < 0.7 blocks).
Brain-retro #5 candidate C, hole 2: enforce-classifier-match.mjs's
MUTATING_TOOLS set missed Task/Agent, so delegating mutations via Task()
bypassed the rule. Added Task and Agent to the set; nodeMatches already
handles Task.subagent_type matching.
Regression test asserts Task with matching subagent_type does NOT block
(keeps the existing nodeMatches Task path intact).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Brain-retro #5 candidate C, hole 1: enforce-classifier-match.mjs allowed
the agent to bypass the rule by writing 'override: <reason>' in its own
response (self-override = no enforcement). The user-vocabulary override
phrases in enforce-override-vocab.json remain the only legitimate path.
Added regression test asserting block on assistantText override when user
prompt has no override phrase.
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.
- Phase 2 FK hotfix RouteSupplierLeadJob (commit 0da72778): closed active incident,
25 stuck failed_jobs → 0 via queue:retry all. Root: deals.received_at UPDATE
broke lead_charges FK (ON UPDATE NO ACTION default).
- Dropped dormant deals_duplicate_of_id_idx (9 partition children cascaded).
- EnsureSaasAdmin rollback (25.05) разобран: tar -xzf Phase 1 Спека C overlay'нул
свежий main-only фикс старой версией с feat-ветки. Не злой актор.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Регрессия 26.05.2026 04:12-05:03 UTC: 9 RouteSupplierLeadJob упали с
SQLSTATE 23503 (FK violation) при попытке Phase 2 merge обновить
deals.received_at:
update or delete on table "deals_y2026_m05" violates foreign key
constraint "lead_charges_deal_id_deal_received_at_fkey"
on table "lead_charges"
Корневая причина: lead_charges имеет FK на (deal_id, deal_received_at)
с ON DELETE CASCADE, но ON UPDATE NO ACTION (default Postgres). Phase 2
merge (commit 8d037e1f) условно обновлял deals.received_at, если webhook
пришёл позже CSV-recovered. Любое изменение received_at ломало FK даже
в той же месячной партиции (DEFERRABLE INITIALLY DEFERRED только
откладывал проверку до COMMIT — она всё равно падала).
Фикс: убрать условное обновление received_at, оставить только
source_crm_id + updated_at. CSV-recovered timestamp сохраняется как
есть — отличие на минуты несущественно vs риск каскадного DELETE
lead_charges.
Тест: tests/Feature/Jobs/RouteSupplierLeadJobTest.php — новый
'merges webhook into csv-recovered deal even when received_at differs'
воспроизводит баг (CSV-recovered deal с lead_charge → webhook с другим
received_at → merge должен пройти без FK violation).
NB: локальный verify-RED заблокирован env-drift testing-БД
(auth_log partitions via pgsql_supplier, см. memory). Прод-смок:
реретрай застрявших failed_jobs 25489+25492..25500 → должны пройти.
Affected failed_jobs (для реретрая после деплоя):
25489, 25492, 25493, 25494, 25495, 25496, 25497, 25498, 25499, 25500
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Дмитрий