feat: show what the model flagged on the Changes tab

[HarryRandall]

Summary

Follows #134. Review is the only check on a model-owned sync, but the model's own notes were produced on every sync and then thrown away: nothing stored them and nothing showed them.

• Stored. A new catalogue_version_flags table holds each source version's flags, sealed with the version like its provenance. Only catalogue reviewers can read it (can_read_catalogue_drafts), and it is not part of the content hash, so notes never create a review on their own.

• Shown. The Changes tab opens with What to check:

  • parts that could not be read and were left empty (errors);
  • wording to compare with the ANU page (warnings);
  • the fields the model was least sure of, below 80% confidence, weakest first, with the page wording behind each.

  Field names read as an administrator knows them: requisites.prerequisiteRule becomes "Prerequisite rule" and requirements.rule.children.3 becomes "Requirements, branch 4". The section is absent when nothing was flagged.

Verification

• Format, lint, types and 537 unit and component tests (pnpm verify was not rerun on this branch)
• Browser smoke test: not run. Docker Desktop was off and the local stack is shared.
• Supabase migration and generated types: not run locally. apps/web/types/database.ts is committed from the Database gate's own generator output, so that gate is the check.

Deployment notes

• Migration 011_catalogue_version_flags.sql creates the table, its seal trigger, row-level security, a reviewer read policy and grants. A pgTAP test covers the access boundary.
• Flags are stored for source versions created after this deploys. Existing versions have none.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
coursemap	Ready	Preview	Sep 23, 2026 7:51am UTC