[Deicyde]

Fixes #777.

Premise

• User: an agent or lead reading autoform claim list, or a refusal from claim acquire or claim release, on a board that holds refs Autoform didn't write.
• Problem: a claim ref whose lease is a JSON object with a schema other than autoform-claim/v1 is reported as claim 'K' has an invalid lease schema, the message a damaged autoform-claim/v1 lease also gets. claim list shows it as schema: "unreadable". Nothing names the schema it found, so the run in Agent feedback from a Formalize run: autoform claim list --worker-id <worker> reports `has an invalid lease schema… #777 had to read the ref's commit message to learn that its refs were deliberate markers.
• Replaces: that message, for this case only, with claim 'K' has unsupported lease schema 'X', where X is the repr of the value found.
• Deletes: nothing.

Line delta: +28 in total.

• code: +3 (autoform_cli/claims.py);
• docs: +5 (CHANGELOG.md);
• tests: +20 (tests/test_claims.py).

What changes

• Messages. _parse_lease raises the new message when the lease is a JSON object with a schema key whose value isn't autoform-claim/v1. Every other message stays: has invalid lease JSON for a lease that doesn't parse, and has an invalid lease schema for one that isn't an object, has no schema, or is an autoform-claim/v1 lease with a bad field. The repr escapes control characters, as the key's already does.
• Held claims. The lease is still a MalformedLeaseError, so what counts as held doesn't change. claim acquire and claim release still refuse it, exit 1, now with the new message. claim list still gives _malformed: true and schema: "unreadable", with the new message in _error, since the listing's JSON shape is a contract that a script may match on. autoform move and project worktrees still treat it as possibly held.
• Docs. None. No doc quotes these messages, and the claim contract tells a reader to act on _malformed.
• Tests. test_a_lease_of_another_schema_is_named_and_still_held plants a lease with schema legacy-block/v1. It checks that read, acquire and release each raise exactly the new message, and that claim list exits 0 with that message in _error, schema still unreadable and _malformed true.
• CHANGELOG. One line under Unreleased's Fixed, added in a second commit once the PR had its number:

### Fixed

- **A claim whose lease has another schema names it.** A claim ref whose lease
  is JSON with a schema other than `autoform-claim/v1` was reported as having
  an invalid lease schema, so telling a ref another tool wrote from a damaged
  lease meant reading its commit. The message now says the schema is
  unsupported and names it: `claim 'K' has unsupported lease schema 'X'` (#811).

Checks

• Full CI on scratch at 43e598b, this PR's code commit on main at 9e1d2b7, before Claims: remove renew, cleanup and --ttl #795 removed renew, cleanup and --ttl, with the mutants below: every job passed. That covers test on 3.11 and 3.13 (7,211 passed on each, the 3.13 count including the mutant harness's test, ruff included), the real-Lean, skeleton and REPL suites, WebKit, Windows and the Node read-back cards.
• Mutants in that run, after the new test passed unmutated, each failing it: the new check removed, so the old message returns; the message without the schema; a lease of another schema accepted as valid, so a peer could take it over; and claim list giving another schema than unreadable.
  https://github.com/facebookresearch/autoform-bot/actions/runs/43400674886
• ruff check with the pinned 0.15.17 on the changed Python files: clean.
• Rebased on main at ff33adc. Its one conflict was context in tests/test_claims.py, where Claims: remove renew, cleanup and --ttl #795 renamed the test after the new one; the commit is otherwise unchanged, and this PR's CI covers the rebased head.
• git merge-tree, with main at ff33adc and the open PRs' heads as of 2026-11-14 00:09Z: the code commit adds no conflict with any of them. Prove2me - Add skill files and modifications to the autoform-bot CLI to allow for easy integration with prove2.me #351, fix(site): check links and cards in the HTML5 element tree #621, Formulas as text: an accent on an accent adds one mark #794, CLI: build each command's parser beside its handler #804 and Add an opt-in resident REPL backend for tactic attempts #805 already conflict with main, and none of them touches claims.py or tests/test_claims.py; the others merge cleanly.
• A test for the new message, and a CHANGELOG line.
• make lint and make test, through CI on scratch.

Posted by Claude Code, at Jack's request.

[Deicyde]

No blockers at 08d34c9.

• _parse_lease names the schema only for a JSON object whose schema is present and isn't autoform-claim/v1.
• A damaged v1 lease, a non-object and a lease with no schema keep "has an invalid lease schema".
• Every such lease is still a MalformedLeaseError, so nothing that was held is freed.
• I checked seven leases by direct calls, on main at ce0c81c and at this head. The new test fails against main's message, and CI is green.

Two nits:

• The repr is unbounded. A 5,000-character schema gives a 5,044-character refusal and _error; capping the quoted value keeps both readable.
• A non-string schema reads as Python (None, True), where the lease is JSON (null, true). json.dumps would keep the lease's own spelling.

Posted by Claude Code, at Jack's request.