openehr-specs: class tables from the repo's BMM, scaffold revision 2, no-ticket amendments

[sebastian-iancu]

Summary

Fixes found while running the openehr-specs workflow end to end on specifications-TERM.

• class-generation and regen-classes now generate from the repo's own BMM (fix). They passed bundled schema ids, so bmm-publisher rendered its own copy of the BMM, which lags the repos. A run with the documented command exited 0 but did not show a fix just made to specifications-TERM's BMM. The suggested mount over /app/resources hid the bundled dependencies and exited 1. Both skills now mount the component's computable/BMM/<id>.bmm.json and its sibling dependencies under /in/ and pass paths. regen-classes stops when a file is missing instead of falling back to an id. Ids remain documented for reproducing published output.
• scaffold template set revision 2 (feat):
  • The AGENTS.md build region no longer says "No build tooling lives in this repo", which is wrong for TERM's PHP generator. New repos get a TODO(scaffold) marker asking them to describe their own tooling.
  • The class-table command loads the sibling BASE BMM with -d, through a new variable base_bmm_schema_id. It is inferred from the specifications-BASE clone, highest version first, and is empty for BASE itself. Without it, links to BASE types come out as /classes/String.
  • .claude/CLAUDE.md and the skill's rules say that repo guidance, such as /init's, goes into AGENTS.md outside the regions.
  • first_release is confirmed only when manifest.json is created.
  • migrations/0002.json carries a note for existing repos, which do not get the new marker. A dry-run plan upgrades BASE's build region (without -d) and leaves TERM's pinned one alone.
• amendment-record covers changes without a ticket (docs). No invented or placeholder key, an offer to raise a ticket, otherwise an entry without a reference (266 of the 974 existing entries have none), and no entry when the author says none is needed.
• The manifest-spec-entry.md example shows the current ITS-BMM-RM url expression and ITS-BMM-BASE dependency, copied from specifications-RM/manifest.json, instead of MagicDraw uml expressions (docs).

Five upgrade tests hard-coded revision numbers that assumed the shipped set is revision 1. They now follow the latest revision, so the next revision will not break them.

Checklist

• python3 scripts/validate.py and python3 -m unittest discover -s scripts -p 'test_*.py' pass, on each of the four commits (117 tests; scaffold.py check clean)
• Skill triggering tested locally in Claude Code: not done; descriptions and frontmatter are unchanged
• Cursor install tested locally: not done; no plugin or manifest metadata changed
• Both marketplaces updated when plugin metadata changed: not applicable, no metadata changed
• CHANGELOG.md updated under Unreleased; no version bump
• Content grounded: the class-table behaviour was reproduced against bmm-publisher 0.11.0, the manifest example is RM's actual manifest, and the no-ticket count comes from a survey of the local specifications-* clones

🤖 Generated with Claude Code