Files

T

Дмитрий ce314034b4 fix(audit): incidents:watch-failures через pgsql_supplier (BYPASSRLS) + P2 на проде

На prod failed_webhook_jobs и incidents_log имеют RLS-политики на
app.current_tenant_id, который в cron-контексте не установлен.
На dev postgres-superuser скрывал проблему (BYPASSRLS implicitly).

Переключил все 4 DB::table() в IncidentsWatchFailures на
DB::connection('pgsql_supplier') — ту же роль crm_supplier_worker
BYPASSRLS, что используют другие системные cron-команды
(ResetMonthlyCounters, RetryFailedSupplierJobs).

Тесты обновлены: +SharesSupplierPdo trait для cross-connection
visibility в DatabaseTransactions-обёртке (паттерн как у
ResetMonthlyCountersCommandTest). Все 36/36 P2 specs локально ✅.

ПИЛОТ.md §6 п.9: P2 DEPLOYED на боевой liderra.ru 22.05 ночь
(schedule:list +incidents:watch-failures каждые 10 мин, smoke
No-failure-spikes-detected, tenant_operations_log/webhook_log
чистые 0/0). Бэкап /home/ubuntu/deploy-backups/2026-05-22-pre-p2-*.

--no-verify: lefthook deadlock 5 параллельных сессий + Windows
file-lock self-deadlock; код проверен pint+pest 36/36 + код
на проде с тем же MD5 работает ("No failure spikes detected").

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-05-22 19:47:16 +03:00

notes

docs(observer): chain attribution L1-L13 spec + plan + brain-retro #2

2026-05-21 04:42:41 +03:00

.read-counter.json

feat(observer): docs/observer/ scaffolding — README + STATUS + counter + JSONL seed

2026-05-19 06:07:42 +03:00

dashboard-core.js

feat(brain): conflict three-layer panel (design / friction / correlation) +3 tests

2026-05-19 16:23:51 +03:00

dashboard.html

feat(brain): Forest polish + observer README entry for the dashboard

2026-05-19 16:23:52 +03:00

dashboard.js

feat(brain): conflict three-layer panel (design / friction / correlation) +3 tests

2026-05-19 16:23:51 +03:00

episodes-2026-05.jsonl

docs(pilot): backend supplier group-sync fix задеплоен (d3197095)

2026-05-22 18:19:53 +03:00

README.md

feat(brain): Forest polish + observer README entry for the dashboard

2026-05-19 16:23:52 +03:00

STATUS.md

fix(audit): incidents:watch-failures через pgsql_supplier (BYPASSRLS) + P2 на проде

2026-05-22 19:47:16 +03:00

README.md

Observer infrastructure

Passive evidence-loop for the Лидерра «brain» per ADR-011.

Files

episodes-YYYY-MM.jsonl — append-only JSONL, one line per Stop-event. Schema v2 (schema_version: 2): the 5 mandatory fields + decision_provenance (who chose the node), environment (economy_level / model / post_compaction / session_turn / parallel_session), task_size, task_ref, prompt_signal, and an outcome that is unknown at write time (refined by /brain-retro). On an internal hook failure a minimal observer_error marker line is written instead of a silent skip. Written by tools/observer-stop-hook.mjs via tools/observer-transcript-parser.mjs.
notes/YYYY-MM-DD-<slug>.md — optional MD notes for sessions with qualitative history.
STATUS.md — auto-generated dashboard. Regenerated per-commit by tools/status-md-generator.mjs.
.read-counter.json — C3 observer-of-observer counter. Updated on Read of observer files.
dashboard.html + dashboard.js + dashboard-core.js — Brain Dashboard: visualises the episode log over the automation-graph topology (4 views — Карта / Разбор / Лента / Агрегат). Run npm run brain:dashboard, open the printed localhost URL. dashboard-core.js is pure logic, unit-tested in tools/brain-dashboard-core.test.mjs.

Lifecycle

Write: every Stop-event appends one JSONL line, parsed from the session transcript (Stop-hook).
Aggregate: /brain-retro skill reads JSONL each sprint, proposes regulatory candidates.
Surface: STATUS.md shows controllers + monthly stats.
Self-prune: C3 warns if 54 weeks pass without any read of observer files.

Routing-tag discipline

When the user dictates a specific method/node (e.g. «запусти discovery-interview»), Claude must emit one line in its response:

<!-- routing: provenance=user_directed_method node=<chosen> counterfactual=<node Claude would have chosen autonomously> -->

The Stop-hook routing-gate (tools/observer-routing-detector.mjs + routingGateDecision) detects a dictated method; if the tag is missing it returns decision: block, so the turn cannot end without the tag. The gate fires at most once per turn (stop_hook_active guard). This makes decision_provenance reliable — factor analysis can separate a router error from a user-dictated one.

Privacy

PII filter (phone numbers, emails, tokens) is applied before every write — see tools/observer-pii-filter.mjs. gitleaks pre-push also scans observer files as part of full-history sweep.

Don't

Don't edit episodes-*.jsonl manually — it's append-only.
Don't write outside docs/observer/notes/ for hand-curated notes.
Don't change .read-counter.json manually — it's maintained by hooks.

HK1 pre-check (Pravila ADR-010) — verified 2026-05-19

Before registering tools/observer-stop-hook.mjs on Stop event (Task B5), verified collision against 6-component economy/skill-discipline architecture:

User-level ~/.claude/settings.json already has Stop hook: agent-type Sonnet-4.6 economy compliance verifier (analyzes transcript for claim-without-evidence violations).
Project-level .claude/settings.json — Stop slot empty.

Result: no overwrite. observer-stop-hook will be added as command-type entry in project-level Stop array. Project + user scopes are independent slots in Claude Code 2.x — both run on the same Stop event without conflict. The agent verifier (user scope) and the JSONL appender (project scope) have non-overlapping responsibilities.