fix(catalog): exclude auto-generated docs to stop perpetual freshness drift#309
Merged
Merged
Conversation
… drift Root cause of the recurring 'Check Catalog Freshness' failures: the divergence-dashboard workflow rewrites docs/divergence/dashboard.md every 6h (and mobius-pulse-unified rewrites docs/divergence/WEEKLY_DIGEST.md weekly), both committed with [skip ci] — so the catalog is never regenerated and its stored content_hash for those files goes stale, failing every subsequent PR. These are machine output, not documentation. exportCatalog.ts now skips them, so dashboard/digest updates can no longer drift the catalog. Regenerated: docCount 961 -> 959 (only the two generated files removed). OVERVIEW.md and all real docs are retained. EPICON-INTENT: eliminate a recurring spurious CI blocker at its source rather than re-syncing the catalog by hand every six hours. Co-authored-by: Michael Judan <kaizencycle@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the recurring
Check Catalog Freshnessfailure at its root cause,instead of re-syncing the catalog by hand every few hours.
Root cause
catalog/mobius_catalog.jsonstores acontent_hashper doc underdocs/. Twodocs are machine-generated and committed with
[skip ci](which deliberatelyskips the catalog regen):
docs/divergence/dashboard.mdmobius-divergence-dashboard.ymldocs/divergence/WEEKLY_DIGEST.mdmobius-pulse-unified.ymlEach regeneration changes their content, but
[skip ci]means the catalog'sstored hash is never updated — so the catalog drifts and every subsequent PR
fails freshness through no fault of its own (this is the loop that hit #300–
#308, including this very session's PRs). Hand re-syncing the catalog only holds
until the next 6-hourly dashboard commit.
Fix
scripts/exportCatalog.tsnow skips those two generated files(
IGNORE_DOC_PATHS). They're machine output, not catalogued documentation, sotheir churn can no longer drift the catalog. Regenerated catalog:
docCount961 → 959 — only the two generated files removed;
OVERVIEW.mdand everyreal doc are retained.
Why this is safe / verified
npm run export:catalog, now producing thesame 959-doc set → freshness passes and stays passing across dashboard
updates.
catalog-checkworkflow uses: the only delta is the two removed generated files.
echo-bot(which regenerates + commits the catalog itself) is unaffectedand remains in sync.
"We heal as we walk." — Mobius Systems