Final cleanup after constants migration #187

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Overview

With #182–#186 landed, the package should stop shipping le_utils/resources/, and the README should describe the spec workflow instead of keeping Python and JSON in sync by hand.

Complexity: Low
Target branch: main

Context

• pyproject.toml ships resources/*.json through [tool.setuptools.package-data].
• The README's Constants section says a new constant means editing the Python file and the JSON file; its file formats and format presets sections link to formatlookup.json (on a personal fork) and presetlookup.json.

The Change

• The README should say that a constant is added by editing its spec/ file and running make build.

Acceptance Criteria

• The built le-utils wheel contains no resources/ files.
• le_utils/resources/ contains only the languagelookup.json symlink.
• README links to le_utils/resources/ point to the matching spec/ files instead, except the languagelookup.json link.

AI usage

I made the decisions recorded on #181 and #182; Claude Code applied them to this cleanup against the current code and drafted the issue.