A target taught in one lecture can name a later lecture that builds on
it, and every page printed whatever named the lecture, so L4.2 opened
with five objectives from L3.2, L3.5, and L4.1. A lecture's objectives,
readings, and page now show an entry only when the lecture lists its
objective in teaches, or when no earlier lecture covers it. The
lectures: link is unchanged, so assembly, coverage, and the reports'
review lists still read it.
Reading prose that cites an objective or target from another lecture
now renders as its number on that lecture's page (L3.5's T 1) rather
than the target's full text. The trailing (T ...) list stays this
page's own.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A guide page for the four registries: where entries live, how targets
point at them, the other new fields, the brace-reference table, what
students never see, the lecture and glossary pages, every new error and
lint rule, and the migration from terms.yaml and values.yaml. The setup
guide points at it.
The README covers glossary.yaml, the nine schemas, the 2.1 checks, the
glossary lint family and the note severity, the new lecture commands and
report sections, migrate glossary, and schema version 2.1. Module docs
and the changelog follow.
docs/design/2.1/CODES.md maps the specification's E, W, and I codes to
coursebank's messages and lint codes, each with its test, and REPORT.md
records what changed, the two remaining schema differences, every choice
made where the specification left room, and suggested changes to it. A
new test covers the validation messages the specification does not
number.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add the term, equation, value, and misconception registries
(src/model/course/glossary.rs) and the new optional fields on objectives,
targets, lectures, readings, bank options, and policy. Load registry
entries from objective files, glossary.yaml, and course.yaml, with one
definition site per id as for every other registry. Port every edit in
docs/design/2.1/build_schemas.py into the hand-written schema builders,
add glossary.schema.json, and test the generated schemas against the
targets; the only differences are two 2.0 spellings the code already had.
The 2.0 example fragments load and validate unchanged. The 2.1 example
bank gains `status: draft`, which every coursebank item requires.
tests/docs.rs skips docs/design/, which holds design records rather than
guide pages.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>