Skip to content

chore: refresh the reviewed method catalog pins and review dates - #3

Merged
docxology merged 1 commit into
mainfrom
chore/refresh-catalog-pins-20261101
Nov 2, 2026
Merged

docxology merged 1 commit into
mainfrom
chore/refresh-catalog-pins-20261101

Conversation

@docxology

Copy link
Copy Markdown
Collaborator

Refreshes the reviewed method catalog to current public revisions. All ten entries were re-verified today (2026-11-01); six had moved since the 2026-10-27 review.

Pin changes

Entry Previous pin New pin Drift at review
gnn f0dfb683 8f293d9b (v5.0.3 release) +46 commits to HEAD; the old pin was 25 commits behind v5.0.3
template (docxology/template) 83dd01d2 75a91733 +63
pymdp 411a8e36 c752274e +14
ontology 02661575 0e127a5b +8
start 7797ff5a 6e89d387 +7
courses d42e4294 94dc021e +3
fundamentals, working-groups, journal, journal-utilities unchanged unchanged already at the default-branch head

The GNN entry moves to the canonical v5.0.3 release commit 8f293d9ba810e6eda5c09842d9c7ed9ffa5f92c1 rather than to the current default-branch head, so the catalog points at the released revision. Every evidence URL was checked at its new pin (HTTP 200), including the two .github/README.md paths.

reviewed_on and all checked_on values move to 2026-11-01. docs/integrations.md is regenerated from the catalog by catalog_markdown(), not hand-edited.

Validation

  • Bundled-catalog and discovery tests: 57 passed.
  • Full suite: 621 passed, 9 skipped, coverage 88.82% (gate 80%).
  • ruff check and ruff format --check: clean.
  • symposium organize site --public-dir data/public/2026 rebuilt from the verified tree; the refreshed pins appear on the rendered methods page.

Merge gate

Do not merge until #2 is resolved. The 3.2.0 release candidate's approval is bound to the exact commit 28689cf; landing this on main first would force the candidate to merge main. This PR touches neither the candidate branch nor any file it modifies (verified: no overlap in git diff --name-only origin/main...candidate/2026-program-20261101). After #2 merges, this branch can be merged as an ordinary merge commit.

Not included

.cursorrules is left untouched. It is a tracked, substantive development ruleset that TODO.md references, so removing it is not a self-contained change; it needs a decision about where those rules belong first.

Six of the ten catalog entries pinned commits that have since moved: gnn
(+46 commits, and 25 behind the v5.0.3 release), docxology/template (+63),
pymdp (+14), ontology (+8), start (+7) and courses (+3). The remaining four
(fundamentals, working-groups, journal, journal-utilities) were already at
their default-branch heads.

The GNN entry now pins the canonical v5.0.3 release commit 8f293d9b; the
others pin the verified default-branch heads. Every evidence URL was checked
at its new pin (HTTP 200) and the reviewed/checked dates move to 2026-11-01.
docs/integrations.md is regenerated from the catalog, not hand-edited.

Validation: bundled-catalog and discovery tests (57 passed); full suite
621 passed, 9 skipped, coverage 88.82% (gate 80%); ruff check and format
clean; the rendered public site was rebuilt from the verified tree and the
refreshed pins appear on the methods page.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
@docxology
docxology marked this pull request as ready for review November 2, 2026 02:20
@docxology
docxology merged commit b2facff into main Nov 2, 2026
3 checks passed
@docxology
docxology deleted the chore/refresh-catalog-pins-20261101 branch November 2, 2026 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant