v3.33.2
Patch release: knowledge-freshness provenance fix + knowledge-base refresh.
Fixed
- Knowledge-freshness provenance — in the audit-apply strict path (production), a source's
retrieveddate now advances to the audit run date when its hash is recomputed deterministically, instead of echoing the model-claimedretrieved_at. Previously a freshly-changed hash could pair with a stale retrieval date. Corrected the affectedretrieveddates onbackend-auth-patternsandbackend-fintech-compliance.
Changed
- Knowledge base refresh — the freshness engine processed four backend entries.
backend-fintech-data-modelingandbackend-fintech-ledgergot their first review stamp;backend-auth-patternsandbackend-fintech-compliancehad drift fingerprints refreshed (per the superseded-source policy,last-reviewedis intentionally left unadvanced so they stay queued for human re-review). Guidance content unchanged. KBVERSION→ 0.1.5.
See CHANGELOG.md for details.