Skip to content

chore: pin ct-conventions v0.5.0 - #989

Merged
ocots merged 1 commit into
mainfrom
chore/pin-ct-conventions
Oct 15, 2026
Merged

ocots merged 1 commit into
mainfrom
chore/pin-ct-conventions

Conversation

@ocots

@ocots ocots commented Oct 15, 2026

Copy link
Copy Markdown
Member

Summary

Moves the package from the former Handbook to ct-conventions v0.5.0, as CTBase, CTModels and CTSolvers already did.

  • AGENTS.md
    • pins ct-conventions v0.5.0: a git-ignored clone in .conventions/, with the clone command;
    • points to the reading order (rules/general.md, README.md, method.md, plan-template.md), ct-agents, and CTActions docs/WORKFLOWS.md;
    • cites the rules by identifier in "Key Conventions" (MOD3, TST3, DIM1, …), keeping what is specific to this package.
  • CLAUDE.md only redirects to AGENTS.md.
  • References to the Handbook in code comments, tests and docs become rule identifiers. Historical changelog entries are left as written.
  • .markdownlint.json (GEN2); the changelog loses its markdownlint-disable MD024 comment (CHG2).
  • Housekeeping:
    • .gitignore ignores .conventions/, and _typos.toml excludes it where it exists;
    • CONTRIBUTING.md says where the conventions are and how to bump them.

Comments and documentation only: no code changes.

Test plan

  • Modified Julia files parse
  • markdownlint-cli2 on AGENTS.md, CLAUDE.md and CHANGELOG.md: clean. CONTRIBUTING.md keeps its existing warnings, from the shared org text.
  • CI

🤖 Generated with Claude Code

- AGENTS.md pins ct-conventions v0.5.0 (read from a git-ignored clone in
  .conventions/) and cites rules by identifier; CLAUDE.md redirects to it.
- References to the former Handbook become rule identifiers.
- One .markdownlint.json (GEN2); CONTRIBUTING.md says where the
  conventions are and how to bump them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ocots
ocots merged commit 3a6eaea into main Oct 15, 2026
3 checks passed
@ocots
ocots deleted the chore/pin-ct-conventions branch October 15, 2026 16:42
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