Schedule data loop (#54): reusable base — renderer + packaged validator, distributed via remote_theme + pre-commit

[WestonVoglesonger]

Implements the #54 flat-data schedule loop as the reusable base in the shared theme repo: a clinic edits one YAML file per cohort, a validator gates it, and a fixed Liquid include renders it. A bad data edit fails validation instead of silently rendering wrong, because no Liquid lives in the edited file.

Distribution: Path A (remote_theme + pre-commit)

Rendering and validation are two independent channels, both served from this repo. A Jekyll theme distributes _includes/_layouts/_sass/assets only, so it carries the renderer but not the Python validator, and not _data. That split is a feature, not a limitation: it forces schedule data and people records to be clinic-owned.

Concern	Mechanism	Clinic adds
Render schedule.html	Jekyll remote_theme	remote_theme: ICI3D/ICI3D.github.io + jekyll-remote-theme
Validate schedule data	distributed pre-commit hook	a .pre-commit-config.yaml entry

No submodule needed on either channel.

What's here (all clinic-agnostic)

• _includes/schedule.html — shared renderer (Week to Day to Session). Resolves instructor keys against site.data.team, drops shadow: rows in the participant view.
• ici3d_schedule/ — installable package: the validator (validate.py), the Tier-0 JSON Schema, and the role vocabulary, all as package data. Exposes a validate-schedule console script.
• .pre-commit-hooks.yaml — the distributed hook clinics pin. Installs the package (schema + roles bundled) and validates the clinic's _data/schedule/*.yml against the shared, versioned schema without vendoring it.
• .pre-commit-config.yaml + .github/workflows/schedule-validate.yml — this repo runs that same hook locally (pre-commit install) and in CI (pre-commit/action), so local and CI validation are one source of truth.
• tools/import_schedule.py — wall .md to cohort YAML. tools/validate_schedule.py — thin backward-compat shim over the package.
• _data/schedule/example/sample.yml — a synthetic example cohort (not a real schedule); documents the format and exercises the validator + renderer in CI.

Verified locally

• In-repo hook: pre-commit run validate-schedule --all-files passes on the example; fails with clear errors on a broken schedule (bad kind, missing required fields, unresolvable instructor); correctly skips roles.yml.
• Distributed hook path: built a wheel, installed into a clean venv, ran validate-schedule from a separate clinic-like directory with its own _data/team and no vendored schema/roles — passes on a valid schedule, fails on a broken instructor reference. Schema + roles resolve from bundled package data; instructors resolve from the clinic's own _data/team.
• Earlier: a real Jekyll build renders the example (1 week / 2 days / 8 visible sessions of 9); a person key resolves to a linked name, role tokens render as labels, the one shadow: row is dropped (0 leaks).

Clinic-owned data (the #56 topology)

Both the renderer (site.data.team) and the validator (--people-dir) read _data/team from the consuming repo, so each clinic owns its schedule data and its faculty records. This settles the data-location question structurally: _data cannot travel via remote_theme, so clinic data lives in the clinic repo by construction.

The .github/actions/validate-schedule/ composite action is left in place transitionally, until clinic repos move to the distributed pre-commit hook.

Part of #54 / epic #58.

[WestonVoglesonger]

@pearsonca #54 base loop is up as #59: shared renderer + validator packaged as a composite action clinics pull in, plus a synthetic example. Verified locally (validator 0/0; real Jekyll render, instructors resolve, shadow rows dropped).

Two asks: it is a fork PR so the validate check needs an Approve-and-run, and master needs your review to merge.

Scope: base only, no clinic data in the theme (MMED's lives in MMED#26). The last mile (a clinic rendering its own data) waits on your #56 call.

[WestonVoglesonger]

@pearsonca reshaped this to Path A: ICI3D.github.io is the shared source for both channels, no submodule needed.

• Rendering: _includes/schedule.html via Jekyll remote_theme.
• Validation: the validator + schema + roles are now a small installable package (ici3d_schedule) exposed as a pre-commit hook, run the same locally (pre-commit install) and in CI, schema bundled so nothing is vendored.

Since a theme carries _includes but not _data, schedule data and _data/team are clinic-owned by construction, which settles the #56 data-location question.

Tested: in-repo hook passes/fails correctly, and a wheel installed into a clean venv validates a separate clinic-style dir. MMED#26 is the consumer preview. An approve-and-run on CI here unblocks it.