False config-load rejection captured as typed errata

A stale hook binary falsely rejected `.tsqoba/tsqoba.toml`, and the incident was recorded as typed errata and fixed instead of being left as unexplained tool noise.

Last checked 2026-03-26Musha, runtime/config, TsqDocHOOK-RUST-CHECK-CONFIG-LOAD-001

Summary

A stale hook binary rejected valid repo config, and the false block was turned into recorded errata instead of unexplained tool noise.

Trigger

An outdated hook binary read repo config through an old model and treated the [audit] section in .tsqoba/tsqoba.toml as invalid.

System response

The captured block surface emitted BLOCK with HOOK-RUST-CHECK-CONFIG-LOAD-001, reported a TOML parse failure, and named unknown field 'audit'. The follow-up errata record then stated the actual cause directly: stale hook tooling rather than bad repo config.

Outcome

The incident did not remain an unexplained block. It moved into typed errata with status fixed, and the remediation note tied the false rejection to rebuilding the stale hook binary.

Why it mattered

Dogfooding only helps if bad rejections are recorded and fixed. Here the false block did not turn into private suspicion about tool drift.

Current note

The repo config is valid. This page records a stale tool rejecting it and the errata follow-up that fixed the drift.