Skip to content

chore(catalog): scheduled auto-regenerate (long-lived PR) - #19289

Merged
myia-ai-01 merged 1 commit into
mainfrom
chore/catalog-refresh-pending
Oct 6, 2026
Merged

myia-ai-01 merged 1 commit into
mainfrom
chore/catalog-refresh-pending

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

Purpose

Long-lived PR refreshed daily by catalog-cron.yml (schedule cron 03:37 UTC) to keep
COURSE_CATALOG.generated.{json,md} + CATALOG-STATUS markers + the curriculum (docs/curriculum/*.md)
and health dashboard (docs/archive/reference/HEALTH_DASHBOARD.md) canonical on main.

Maintainer review only — no direct push to main (issue #10136). The bot opens
or updates this PR; merging it refreshes main through the normal PR gate.

What to review

  • Catalog totals (notebook_count, per-family counts) drift only if new notebooks landed on main since the last merge.
  • README <!-- CATALOG-STATUS:START -->…:END --> markers reflect the freshly-regenerated catalog.
  • Curriculum pages under docs/curriculum/ and docs/archive/reference/HEALTH_DASHBOARD.md stay consistent.

Close policy

When the catalog stops drifting (the workflow runs ::notice title=Catalog::main catalog already canonical -- no change.),
this PR will be auto-closed by catalog-pr-close.yml to keep the queue clean. Subsequent
drift reopens it under the same branch.

See .claude/rules/catalog-pr-hygiene.md and #2433, #10136.

Grain: MED/refactor -- lane myia-ai-01:CoursIA

@github-actions github-actions Bot added automation catalog-refresh markdown-table-syntax Table syntax defect in changed files (CODE_SPAN_PIPE, NO_SEP, ...). Advisory. See #10097. labels Oct 5, 2026

@clusterManager-Myia clusterManager-Myia left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Hermes] — audit mécanique du drift catalogue, head 8e85c396.

Vérifié programmatiquement (1390 entrées comparées main↔head, arbre git récursif des deux côtés) :

  • 9 entrées ajoutées au catalogue (Lean-13d-CHSH-Indeterminisme-Native, FT-01/02/03-*_en, PT_18_laya_ablation_distillation, QC-Py-28c-Factor-Preprocessing, Semantic-fleet-MultiConnector-Routing, ICT-42b-InoculationBifurcation) : 9/9 existent dans l'arbre main — le catalogue mergé était en retard sur main, la régénération rattrape un vrai retard.
  • 3 entrées retirées (Search-09d-Lean-Discrepancy-Komlos, GameTheory-18d-Humour-Banc-Dur, ICT-45-InoculationBifurcation) : 3/3 renvoient 404 sur main (renommés/supprimés) — retraits corrects.
  • 66 entrées communes avec drift limité aux champs de suivi (last_success_sha, executed_at, resource_cost, issue_pr_associee, last_validation) — cohérent avec les re-validations récentes, pas de fabrication.
  • Aucune entrée du catalogue head ne pointe vers un notebook absent de main (0 dangling).

Checks : le seul rouge est PR gate = DWELL (minuteur anti-merge 120 min, reste ~105 min, se lève seul au balayage) — documenté non-bloquant, rien à corriger.

Drift authentique, régénération fidèle. RAS pour le merge une fois le plancher levé.

[Hermes hermes-pr-review, cycle :11 05/10, host f6be46d1b7a3, sig=52625fe4]

@github-actions

github-actions Bot commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor Author

Path-collision (organ #13359/#13615)

Cette PR #19289 (chore(catalog): scheduled auto-regenerate (long-lived PR)) touche au moins un chemin de fichier aussi modifie par d'autres PRs ouvertes. Risque de double-livraison (meme fichier livre deux fois, 2x le travail et 2x les runs CI). Advisory : parfois legitime (tranches coordonnees, partition paths: explicite, PRs empilees exclues) -- l'organe rend visible, il ne bloque pas.

Le verdict terminal (#15578) signale qu'un cote de la paire est deja sur main. L'organe mesure un recouvrement de chemins ; il ne compare pas le contenu des deux livraisons, donc il ne conclut PAS a une redondance (#15768) : deux PRs peuvent toucher le meme fichier pour des raisons disjointes. L'arbitrage reste a la lane ou au coordinateur.

Refresh COURSE_CATALOG.generated.{json,md} + CATALOG-STATUS markers.

Catalog is owned by automation; agents must not regenerate it on feature branches (see .claude/rules/catalog-pr-hygiene.md, #2433, #10136).
@github-actions
github-actions Bot force-pushed the chore/catalog-refresh-pending branch from 8e85c39 to 826e1af Compare October 6, 2026 11:26
@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor Author

New commit pushed on chore/catalog-refresh-pending by catalog-cron (run 37451645045).
Last commit SHA: 8b77e4e0f349.
Catalog drift detected; the bot has nothing else to do here. Maintainer: please review + merge when convenient.

@jsboige

jsboige commented Oct 6, 2026

Copy link
Copy Markdown
Owner

[ADJOINT PREFLIGHT]
schema: 1
lane: myia-po-2026:CoursIA-3
pr: 19289
head: 826e1af
complete: true
body: read
comments-reviewed: 2
reviews-reviewed: 1
threads-reviewed: 0
threads-unresolved: 0
surfaces-sha256: 79d39dc6ff2e3736657edd1035cdcfa8486778bcd66dda454e8224eff8c4fea8
diff-files: 23
diff-additions: 3385
diff-deletions: 2588
checks: latest-wins-green
b0: clear
scope: pass
domain: not-applicable
verdict: READY
organ: check_adjoint_prevalidation.py
organ-command: python scripts/check_adjoint_prevalidation.py --derive-verdict 19289
organ-rc: 0
[/ADJOINT PREFLIGHT]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automation catalog-refresh markdown-table-syntax Table syntax defect in changed files (CODE_SPAN_PIPE, NO_SEP, ...). Advisory. See #10097. paragraph-length Paragraph > 2000 chars (wall-of-text, #15405). Resorb before merge.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants