Why
Board packs are the portable career truth (CareerOps_board_pack.json). Migrators live in code (migrateV1toV2 … migrateV4toV5), but there is no human-readable changelog. Contributors and self-hosters need to know what each bump added before writing importers/plugins.
Size
S — new short doc + one README link.
Task
- Add
docs/BOARD_PACK.md with a table/changelog for schema versions 1 → 5:
- what fields appeared
- what never travels (API keys / secrets)
- pointer to
buildBoardPack / importBoardPack in web/lib/board-pack.mjs
- Link it from
docs/README.md and the Export/import section of web/README.md.
- Keep doctrine explicit: keys never export/import; no invented experience.
Acceptance
Out of scope
Rewriting the pack format or bumping to v6.
Why
Board packs are the portable career truth (
CareerOps_board_pack.json). Migrators live in code (migrateV1toV2…migrateV4toV5), but there is no human-readable changelog. Contributors and self-hosters need to know what each bump added before writing importers/plugins.Size
S — new short doc + one README link.
Task
docs/BOARD_PACK.mdwith a table/changelog for schema versions 1 → 5:buildBoardPack/importBoardPackinweb/lib/board-pack.mjsdocs/README.mdand the Export/import section ofweb/README.md.Acceptance
docs/BOARD_PACK.mdexists and matches migrators in code (cite functions/line themes, not vibes)Out of scope
Rewriting the pack format or bumping to v6.