root 41b0a99ed2 chore: add real content that was sitting untracked

Surfaced by today's untracked-files audit. None of these are accidents —
multiple are referenced by name in CLAUDE.md and memory files but were
never added.

Categories:
- docs/PHASE_AUDIT_GUIDE.md (106 LOC) — Claude Code phase audit guidance
- ops/systemd/lakehouse-langfuse-bridge.service — Langfuse bridge unit
- package.json — top-level npm manifest
- scripts/e2e_pipeline_check.sh + production_smoke.sh — real test scripts
- reports/kimi/audit-last-week*.md — the "Two reports live" CLAUDE.md cites
- tests/multi-agent/scenarios/ — 44 staffing scenarios (cutover decision A)
- tests/multi-agent/playbooks/ — 102 playbook records
- tests/battery/, tests/agent_test/PRD.md, tests/real-world/* — real tests
- sidecar/sidecar/{lab_ui,pipeline_lab}.py — 888 LOC dev-only UIs that
  remain in service post-sidecar-drop (commit ba928b1 explicitly kept them)

Sensitivity check: scenarios use synthetic company names ("Heritage Foods",
"Cornerstone Fabrication"); audit reports describe code findings only;
no PII or secrets surfaced.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-02 22:22:10 -05:00

1.8 KiB

Raw Blame History

Scenario retrospective — Parallel Machining, 2026-04-30

Executor: qwen3.5:latest Reviewer: qwen3:latest Draft: qwen2.5:latest Overview(T3): gpt-oss:20b Prior lessons loaded into executor context: 1 (from 2026-04-27)

Events

At	Kind	Role / Count	Pool	Fills	Dur(s)	Gaps
16:00	baseline_fill	Loader × 3	-	✗ 0	26.8	1
09:30	recurring	Warehouse Associate × 2	-	✗ 0	59.4	1
12:30	emergency	Packer × 3	-	✗ 0	18.2	1

Final roster

Worker	Booked	Role	City, ST	Status

Gap signals

drift_or_tool

16:00 — aborted — 3 consecutive drift flags
09:30 — aborted — 3 consecutive drift flags
12:30 — aborted — 3 consecutive drift flags

write_through_audit

post-run — playbook_memory has 1539 entries (ran 3 events, expected ≥ 0 new entries from this run)

Workers touched across the week

0 distinct workers made it through to a decision. Every one is accounted for below — no-shows flagged, rebookings noted, everyone visible.

Worker ID	Name	Events	Outcome

Discovered patterns (meta-index)

What the system identified across semantically-similar past fills as each event ran:

16:00 baseline_fill (Loader): —
09:30 recurring (Warehouse Associate): —
12:30 emergency (Packer): —

Narrative

0/3 events reached consensus.
Final roster: 0 bookings across 0 distinct workers.
Workers touched (booked, failed, or otherwise decided): 0.
Playbook citations across the day: 0 (proof the feedback loop fired across events).
Dropped events: 16:00 baseline_fill, 09:30 recurring, 12:30 emergency.

1.8 KiB Raw Blame History Unescape Escape