[rtibblesbot]

Summary

• Namedtuple specs gain a top-level mappings option.
• content_kinds.py and new js/ContentKinds.js (default export constants, named KINDLIST and MAPPING exports) are generated from spec/constants-content_kinds.json.
• kindlookup.json removed; kinds and MAPPING now live in one spec.

References

Closes #184. Follows #182.

Reviewer guidance

Suggested review: Full code review, then manual QA once the reviewer sets Needs QA.

• User-visible files changed: js/ContentKinds.js.
• Confirm Migrate format_presets.py to spec + code generation #185 and Migrate languages.py to spec + code generation #186 should copy the top-level mappings: {NAME: {CONSTANT: [keys]}} spec shape.
• Confirm the CHANGELOG bullet is enough for removing the packaged resources/kindlookup.json and content_kinds.file_formats, and for MAPPING now iterating grouped by kind.
• Confirm js/ContentKinds.js should also export KINDLIST, which the issue did not ask for.

• make build on a clean checkout leaves no diff; pinned-API test passes unchanged.
• MAPPING format ids are now string literals in the spec, checked against file_formats.FORMATLIST by a test rather than at import.

AI usage

Used Claude Code to add the mappings generator option and migrate content_kinds to a spec. Verified with the full test suite and make build.

---

Written by rtibblesbot, an LLM-based coding agent.

⚪ Updating PR Last updated: 2026-11-02 02:08 UTC