6000x-authority-closeout — Section A · Baseline verify

Verdict: PASS — all baseline invariants match 6000x close.

Repo

• HEAD: 4fb380ec463aba410d7fb527168a2e4eaa690434
• Branch: main
• Working tree: clean
• Last commit: 6000x author-mode Nuxt PR + ops cron package + auto-refresh prod pilot

Tests

pytest -q tests/ → 1163 passed in 0.70s

Healthcheck (7 surfaces)

overall_ok=true

• three_axis_cache OK — in_sync
• directus_collection OK — 163 rows / 1 read-permission
• qdrant_collection OK — iu_core_iu_chunks (61 indexed)
• auto_refresh_trigger OK — gate=false fires_24h=4
• vector_boundary OK — 61 pts / 60 unique
• write_gates OK — all 6 inert
• operator_runtime OK — open_runs=0 failed_24h=0 active_leases=0

PG facts

• envelope_rows: 163
• refresh_log_total: 6 rows
• refresh_log_id18: actor=iu_lifecycle_trigger, outcome=skipped_in_sync, view_pre=163, table_pre=163, table_post=163, started_at=2026-05-23 14:20:20Z
• trigger_errors_24h: 0
• retention policies: 3 (refresh_log keep_days=30, error_log keep_days=90, command_run keep_days=90)
• auto_refresh_gate: false
• retention_enabled: false

SSH/VPS reachability

ssh contabo reaches vmi3080463 as root; docker exec postgres works.

Conclusion

No drift since 6000x. No backup needed — no production DB mutation planned.