41b0a99ed2
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>
7 lines
535 B
Markdown
7 lines
535 B
Markdown
# Cross-day lesson — Riverfront Steel, 2026-04-28
|
||
|
||
_Generated by `gpt-oss:20b` in 6.8s. Based on 3 events + 1 mid-day checkpoints._
|
||
|
||
**
|
||
Before scheduling a Packer in Toledo, confirm the tool calibration and verify the location accuracy to mitigate drift risk. Update the pool status immediately after baseline and recurring fills so the Packer has accurate data. Schedule the Packer only after the pool is refreshed to avoid misplacement failures. Double‑check the Packer’s tool settings in the system before the shift starts.
|