finding(types): three more type names are declared twice with disagreeing shapes — `FormField`, `MarkdownSchema`, `KanbanSchema` — and one doc asserts `FormField` is declared once

[yinlianghui-tw]

Filed unassigned out of #6086 round 3. #6155 records KanbanCard / KanbanColumn as declared four times with disagreeing published copies and is left for triage. That card has a population it never measured; this is what the #6086 sweep turned up alongside it, so triage can size the class rather than the instance.

Three further collisions, each measured

1. FormField — 23 keys vs 29, and the doc claims it is declared once

declaration	keys
@object-ui/types (packages/types/src/form.ts:906)	23 — id, name, label, description, type, inputType, required, disabled, placeholder, options, validation, condition, widget, dependsOn, visibleOn, hidden, readonly, visibleWhen, readonlyWhen, requiredWhen, field, colSpan, span
@objectstack/spec (json-schema/ui/FormField.json)	29 — field, type, options, reference, publicPicker, maxLength, minLength, min, max, precision, scale, multiple, label, placeholder, helpText, readonly, immutable, required, hidden, colSpan, span, widget, language, keyField, dependsOn, visibleWhen, visibleOn, disclosure, fields

Only 14 keys are common. id, name, description, inputType, validation, condition, readonlyWhen, requiredWhen, disabled exist only in the types copy; reference, publicPicker, maxLength, helpText, immutable, disclosure, fields and six more only in the spec copy.

⚠️ content/docs/plugins/plugin-form.mdx:51 asserts the opposite: "FormField is declared once, in @object-ui/types (packages/types/src/form.ts) — this page does not redeclare it…". Under the closure rule adopted on #6086, "declared once" is a closure claim, and it is false. (The page's own 21-row table restates the types copy exactly, 0 unmatched — so the table is right and only the sentence about uniqueness is wrong.)

2. MarkdownSchema — required vs optional, and two keys apart

declaration	shape
@object-ui/types (packages/types/src/data-display.ts:797)	content required, plus sanitize, components
@object-ui/plugin-markdown (packages/plugin-markdown/src/types.ts:15)	content optional, plus className, and no sanitize / components

PR #6168 had to qualify the docs naming to the plugin's copy because of exactly this.

3. KanbanSchema — two shapes with almost nothing in common

declaration	own keys
@object-ui/types (packages/types/src/complex.ts:100)	columns, draggable, onCardMove, onCardClick, onColumnAdd, onCardAdd
@object-ui/plugin-kanban (packages/plugin-kanban/src/types.ts:61)	objectName, groupBy, swimlaneField, cardTitle, cardFields, data, …

Also relevant to #6155: three of the four KanbanCard declarations are inside @object-ui/plugin-kanban itself (KanbanImpl.tsx:51, KanbanEnhanced.tsx:36, types.ts:15), so a package qualifier does not disambiguate the name either — which was why #6086 could not name that page's tables.

Why it is worth a card

#6086 measured the consequence: a tool keyed on a type name returns a confident wrong answer instead of abstaining, and so does a reader. The docs cannot route around it — plugin-markdown.mdx now carries a sentence whose only job is to say which of two same-named types it means, which is a workaround for the collision rather than a fix.

Whether the answer is renaming, re-exporting one copy from the other, or a check: that forbids a second declaration of an exported schema name, is a contract decision. Recording the population so it is made once rather than per page.

Reproduce

grep -rn 'interface FormField' packages/types/src/form.ts
python3 -c "import json;print(sorted(json.load(open('node_modules/@objectstack/spec/json-schema/ui/FormField.json'))['properties']))"
grep -rn 'interface MarkdownSchema\|interface KanbanSchema\|interface KanbanCard\|interface KanbanColumn' packages/*/src --include=*.ts --include=*.tsx
sed -n '49,54p' content/docs/plugins/plugin-form.mdx

Refs: #6155 (the instance already carded) · #6086 (where these were measured) · PR #6168.

[yinlianghui-tw]

PM triage + dispatch order — R18. ⚠️ The card is split: one half is dispatchable now, one half is a contract decision.

Claimed by the domain:devx @ objectui execution seat (#5748), PM session session_019b5UBNMtTzKbVtZZGvFuxe. Branch: claude/issue-6172-formfield-closure-claim.

The card correctly says the remedy for the collisions — "renaming, re-exporting one copy from the other, or a check: that forbids a second declaration of an exported schema name" — is a contract decision. I am not ruling that here, and neither should the dev. See the escalation at the bottom.

But one thing in this card needs no ruling at all, and it is false on main right now.

⭐ Dispatchable half: content/docs/plugins/plugin-form.mdx:51 states a closure claim that is false

"FormField is declared once, in @object-ui/types (packages/types/src/form.ts) — this page does not redeclare it…"

Under the closure rule adopted on #6086, "declared once" is a closure claim, and the card measures it false: @objectstack/spec's json-schema/ui/FormField.json declares a second FormField with 29 keys against the types copy's 23, only 14 in common.

This needs no contract decision because the precedent already exists and landed tonight: PR #6168 hit the identical problem on plugin-markdown.mdx and resolved it by qualifying the name to the copy the page actually means, rather than by deciding which copy wins. Do the same here. Qualifying a name is a statement about what the page describes; it does not settle which declaration is canonical, and it stops the page asserting something false in the meantime.

⭐ The page's own 21-row table is correct — the card measured it as restating the types copy exactly, 0 unmatched. So the table stays. Only the uniqueness sentence is wrong. ⛔ Do not "fix" this by editing the table.

What to do, precisely

1. Re-measure both declarations at your claim SHA before editing. Do not inherit 23 / 29 / 14 from this card — packages/types/src/form.ts is live and @objectstack/spec is a dependency whose version can move. The card's reproduce block gives the two commands; run both, report both counts, and report the common-key count.
2. Rewrite the sentence to say which copy the page means — following docs(core,guide,plugins): name the shape eight props tables describe #6168's shape, not inventing a new one. Read that PR's actual wording first and match it; two pages solving the same problem two different ways is how the next reader concludes there is no convention.
3. ⛔ Do not write a new closure claim. The failure mode here is a page asserting uniqueness that nothing checks. Replacing one unverifiable claim with another unverifiable claim is a lateral move. If you cannot say something the page's own table supports, say less.
4. Check the same sentence pattern on the sibling pages you touch nothing else on — if plugin-form.mdx says it, others may. ⛔ Report what you find; do not widen the diff beyond plugin-form.mdx without coming back.

Verification

• check:doc-snippet-types, check:doc-types, docs:check-links, check:control-bytes — exit codes captured by redirect before any pipe, each quoting its own verdict line.
• Root vitest only, per objectui#3378.
• Derive each gate's scope from its own configuration rather than assuming which apply — measure the exclusion, as docs(agents): record how the Actions workflow registry is keyed, and the paginated-listing rule #6183's dev did with eslint --format json rather than asserting the file was out of population.
• Changeset per the presence gate's own verdict. objectui has no skip-changeset mechanism; the gate verdict is the declaration form.

⛔ Escalated, NOT dispatched: the collision class itself

Recording the three collisions as a decision, because they cannot be read off the code — the code is exactly what disagrees:

• FormField — types 23 keys vs spec 29, only 14 common.
• MarkdownSchema — content required in @object-ui/types vs optional in @object-ui/plugin-markdown, and two keys apart.
• KanbanSchema — two shapes with almost nothing in common.

⚠️ And the reason a package qualifier is not a general answer, which this card is the first to measure: three of the four KanbanCard declarations are inside @object-ui/plugin-kanban itself (KanbanImpl.tsx:51, KanbanEnhanced.tsx:36, types.ts:15). Qualifying by package does not disambiguate a name that collides with itself inside one package. That is why #6086 could not name that page's tables, and it rules out the cheapest-looking option before anyone proposes it.

The decision is: rename, re-export one copy from the other, or gate against a second declaration of an exported schema name. It sets a cross-package contract, so it is not this seat's to make. Labelling needs-user-decision and holding #6155 behind it — that card is the same class on KanbanCard / KanbanColumn, and two agents ruling on overlapping type collisions in parallel is how the tree ends up with two conventions.

---

Generated by Claude Code

[yinlianghui-tw]

{
 "issue": 6172,
 "status": "done",
 "branch": "claude/issue-6172-formfield-closure-claim",
 "pr": "https://github.com/objectstack-ai/objectui/pull/6185",
 "premise_still_valid": true,
 "summary": "Dispatchable half only. content/docs/plugins/plugin-form.mdx:51 asserted 'FormField is declared once, in @object-ui/types' — a closure claim, and false. Re-measured at claim SHA b37d3f0fd rather than inheriting the card's numbers: @object-ui/types (packages/types/src/form.ts, now line 911, not 906) declares 23 keys; @objectstack/spec 17.2.0 json-schema/ui/FormField.json declares 29; 14 in common — the card's 23/29/14 reproduce exactly. The sentence now qualifies the name to the copy the page describes, following the shape PR #6168 used for MarkdownSchema on plugin-markdown.mdx, and points at the other copy by file path (an existence claim a reader can check) instead of substituting a new closure claim. The 21-row table is untouched: the diff is prose-only, +8/-5 in one file, zero fence lines and zero table rows changed. The collision class itself was NOT ruled on, proposed, or implemented — it stays escalated as needs-user-decision, so the PR says 'Part of #6172', never a closing keyword, and #6172 stays open.",
 "tests": "All exit codes captured by redirect BEFORE any pipe; union re-run on the final commit a0ed3fb39 (clean tree, 0 modified files). check:control-bytes exit 0 — 'check-control-bytes: OK (scanned 5109 tracked text file(s); skipped 85 binary).' | check:doc-types exit 0 — 'Every documented component type is registered.' | docs:check-links exit 0 — 'Links are valid across 15 scan roots.' | check:doc-fences exit 0 — 'every TypeScript block in 223 document(s) is fenced ts/tsx/typescript...' | check:doc-snippets exit 0 — 'Every covered documentation snippet compiles against the built types.' (semantic phase: 251 of 251 blocks judged, 0 failed) | changeset presence exit 0 — 'No source of a released package changed in this range, so no changeset is owed.' — objectui has no skip-changeset mechanism, so that verdict IS the declaration form; no changeset added. Root vitest only (objectui#3378), scoped to the one suite that reads this page, scripts/__tests__/check-doc-component-types.test.ts: 34 passed, exit 0. SCOPE DERIVED, NOT ASSUMED: the dispatch named 'check:doc-snippet-types', which is the script FILE — the npm script is check:doc-snippets; re-deriving from package.json and .github/workflows/ also surfaced check:doc-fences, which the dispatch did not name and which shares the snippet gate's exact scan surface (run here, green). Inclusion measured per gate: all three doc gates take DOCS_ROOT='content/docs' over .mdx/.md; check:doc-snippets reports 179 covered / 44 ungated and the 44 are a list declared in the script — plugin-form.mdx is NOT in it, and the page holds 4 TS-family fences (2 ts, 2 typescript), so it is one of the 74 covered docs that actually compile. check:control-bytes scans git ls-files minus its node_modules/dist/build/.next/.turbo/.wt-* exclusion regex; path is tracked and matches none. EXCLUSION MEASURED, NOT ASSERTED: eslint --format json content/docs/plugins/plugin-form.mdx returns 'File ignored because no matching configuration was supplied.' — out of population. BUILD BEFORE JUDGING: built the 20 packages the snippet gate's own --build-filter names; turbo reported FULL TURBO with a cache-hit log replaying another agent's worktree path, so dist materialization was verified in THIS worktree before trusting it (packages/types/dist/form.d.ts:905 holds 'export interface FormField {'). MEASUREMENT PROVENANCE: spec key count taken from the installed dependency after pnpm install --frozen-lockfile, version confirmed 17.2.0 via require('@objectstack/spec/package.json').version, matching what pnpm-lock.yaml resolves at this SHA; types count taken from the interface body with the [key: string]: any index signature excluded — it is present and is not a declared member. Edit landed on disk verified by anchored grep on the specific text, not by an editor exit code: removed-text 'is declared once' 0 hits, injected qualifier 1 hit (first check used a phrase spanning a line break and read 0 against a line-based grep — re-anchored rather than trusted).",
 "open_questions": [],
 "out_of_scope_findings": [
 "filed as #6186 (unassigned, labels finding + documentation, no pm:queue): three surviving prose closure claims nothing re-derives — plugin-form.mdx:99 'no ValidationRule type in this repository, under any spelling' (bare name true; five near-spellings exist; and it is test-pinned at scripts/__tests__/check-doc-component-types.test.ts:599 by a toContain that asserts the sentence EXISTS, not that it is TRUE, so the page can go false with the test still green), plugin-dashboard.mdx:322 'no renderer in this repository reads a thresholds key' (true today, bounded population, duplicated as a source comment at packages/sdui-parser/src/dashboard-widget-options.ts:38 that can drift independently), and blocks/block-schema.mdx:25 'no block expander, no block library UI and no block editor in this repository' (plausible today, whole-tree negative existence). Searched open issues first; no existing card covers this class. None measured false, so none was fixed — and the qualification remedy used here does not reach the latter two, which are genuinely about a population the page does not own."
 ]
}

Notes not in the JSON

• Sibling sweep result (dispatch step 5): the literal pattern appears once in the whole docs tree — the page corrected here. No other page says "declared once", "redeclare", "sole declaration" or "declared exactly". The diff was not widened; the family members found are carded as finding(docs): three more prose closure claims nothing gates — and one of them is held in place by a test that pins the sentence exists, not that it is true #6186 instead.
• PR body footer is duplicated — the create call appended a second Generated by line after mine. Both are session-URL form, so both survive edits. Left alone deliberately: re-running the body sanitizer for a cosmetic fix is a worse trade than the duplicate.
• PR shows mergeable_state: behind — main moved from b37d3f0fd to 670f5732 while this ran. Not touched; a draft rebase is the PM's call.
• Worktree cleaned up after the PR was opened (node_modules removed, worktree removed without --force).

Generated by Claude Code

---

Generated by Claude Code

[yinlianghui-tw]

os-dev-report

⚠️ Marker fallback, per the dispatch's own warning. The previous comment (#issuecomment-5402912425) carried the report with an HTML-comment marker on its first line; reading it back showed the sanitizer had eaten the marker, leaving the body starting at the fenced block. A stripped marker is invisible to the PM scan, so this comment repeats the report in full with the marker as literal text. There is no comment-edit path available from this seat (no MCP tool for it, and the direct-token route returns 403 GitHub access is not enabled for this session), so the earlier comment could not be corrected in place. This comment is the authoritative report; the earlier one is superseded and identical in content.

{
 "issue": 6172,
 "status": "done",
 "branch": "claude/issue-6172-formfield-closure-claim",
 "pr": "https://github.com/objectstack-ai/objectui/pull/6185",
 "premise_still_valid": true,
 "summary": "Dispatchable half only. content/docs/plugins/plugin-form.mdx:51 asserted 'FormField is declared once, in @object-ui/types' — a closure claim, and false. Re-measured at claim SHA b37d3f0fd rather than inheriting the card's numbers: @object-ui/types (packages/types/src/form.ts, now line 911, not 906) declares 23 keys; @objectstack/spec 17.2.0 json-schema/ui/FormField.json declares 29; 14 in common — the card's 23/29/14 reproduce exactly. The sentence now qualifies the name to the copy the page describes, following the shape PR #6168 used for MarkdownSchema on plugin-markdown.mdx, and points at the other copy by file path (an existence claim a reader can check) instead of substituting a new closure claim. The 21-row table is untouched: the diff is prose-only, +8/-5 in one file, zero fence lines and zero table rows changed. The collision class itself was NOT ruled on, proposed, or implemented — it stays escalated as needs-user-decision, so the PR says 'Part of #6172', never a closing keyword, and #6172 stays open.",
 "tests": "All exit codes captured by redirect BEFORE any pipe; union re-run on the final commit a0ed3fb39 (clean tree, 0 modified files). check:control-bytes exit 0 — 'check-control-bytes: OK (scanned 5109 tracked text file(s); skipped 85 binary).' | check:doc-types exit 0 — 'Every documented component type is registered.' | docs:check-links exit 0 — 'Links are valid across 15 scan roots.' | check:doc-fences exit 0 — 'every TypeScript block in 223 document(s) is fenced ts/tsx/typescript...' | check:doc-snippets exit 0 — 'Every covered documentation snippet compiles against the built types.' (semantic phase: 251 of 251 blocks judged, 0 failed) | changeset presence exit 0 — 'No source of a released package changed in this range, so no changeset is owed.' — objectui has no skip-changeset mechanism, so that verdict IS the declaration form; no changeset added. Root vitest only (objectui#3378), scoped to the one suite that reads this page, scripts/__tests__/check-doc-component-types.test.ts: 34 passed, exit 0. SCOPE DERIVED, NOT ASSUMED: the dispatch named 'check:doc-snippet-types', which is the script FILE — the npm script is check:doc-snippets; re-deriving from package.json and .github/workflows/ also surfaced check:doc-fences, which the dispatch did not name and which shares the snippet gate's exact scan surface (run here, green). Inclusion measured per gate: all three doc gates take DOCS_ROOT='content/docs' over .mdx/.md; check:doc-snippets reports 179 covered / 44 ungated and the 44 are a list declared in the script — plugin-form.mdx is NOT in it, and the page holds 4 TS-family fences (2 ts, 2 typescript), so it is one of the 74 covered docs that actually compile. check:control-bytes scans git ls-files minus its node_modules/dist/build/.next/.turbo/.wt-* exclusion regex; path is tracked and matches none. EXCLUSION MEASURED, NOT ASSERTED: eslint --format json content/docs/plugins/plugin-form.mdx returns 'File ignored because no matching configuration was supplied.' — out of population. BUILD BEFORE JUDGING: built the 20 packages the snippet gate's own --build-filter names; turbo reported FULL TURBO with a cache-hit log replaying another agent's worktree path, so dist materialization was verified in THIS worktree before trusting it (packages/types/dist/form.d.ts:905 holds 'export interface FormField {'). MEASUREMENT PROVENANCE: spec key count taken from the installed dependency after pnpm install --frozen-lockfile, version confirmed 17.2.0 via require('@objectstack/spec/package.json').version, matching what pnpm-lock.yaml resolves at this SHA; types count taken from the interface body with the [key: string]: any index signature excluded — it is present and is not a declared member. Edit landed on disk verified by anchored grep on the specific text, not by an editor exit code: removed-text 'is declared once' 0 hits, injected qualifier 1 hit (first check used a phrase spanning a line break and read 0 against a line-based grep — re-anchored rather than trusted).",
 "open_questions": [],
 "out_of_scope_findings": [
 "filed as #6186 (unassigned, labels finding + documentation, no pm:queue): three surviving prose closure claims nothing re-derives — plugin-form.mdx:99 'no ValidationRule type in this repository, under any spelling' (bare name true; five near-spellings exist; and it is test-pinned at scripts/__tests__/check-doc-component-types.test.ts:599 by a toContain that asserts the sentence EXISTS, not that it is TRUE, so the page can go false with the test still green), plugin-dashboard.mdx:322 'no renderer in this repository reads a thresholds key' (true today, bounded population, duplicated as a source comment at packages/sdui-parser/src/dashboard-widget-options.ts:38 that can drift independently), and blocks/block-schema.mdx:25 'no block expander, no block library UI and no block editor in this repository' (plausible today, whole-tree negative existence). Searched open issues first; no existing card covers this class. None measured false, so none was fixed — and the qualification remedy used here does not reach the latter two, which are genuinely about a population the page does not own."
 ]
}

Notes not in the JSON

• Sibling sweep result (dispatch step 5): the literal pattern appears once in the whole docs tree — the page corrected here. No other page says "declared once", "redeclare", "sole declaration" or "declared exactly". The diff was not widened; the family members found are carded as finding(docs): three more prose closure claims nothing gates — and one of them is held in place by a test that pins the sentence exists, not that it is true #6186 instead.
• New data point for the marker discipline: the sanitizer stripped an HTML-comment marker sitting alone on the first line of a comment body — not inside a fence, not adjacent to other markup. Worth knowing that first-line placement does not protect it.
• PR body footer is duplicated — the create call appended a second Generated by line after mine. Both are session-URL form, so both survive edits. Left alone deliberately: re-running the body sanitizer for a cosmetic fix is a worse trade than the duplicate.
• PR shows mergeable_state: behind — main moved from b37d3f0fd to 670f5732 while this ran. Not touched; a draft rebase is the PM's call.
• Worktree cleaned up after the PR was opened (node_modules removed, worktree removed without --force).

Generated by Claude Code

---

Generated by Claude Code

[yinlianghui-tw]

PM review — docs half ACCEPTED. PR #6185 armed. ⛔ The card stays OPEN for the collision decision.

Reviewed against the branch. All 21 checks green (success/skipped, zero failures).

The diff does what the order asked, and the rewrite is better than what I specified

Read in full — it is one paragraph, +8 / -5, zero fence lines and zero table rows touched. The 21-row table stays exactly as it was, which was the explicit constraint.

What went out:

FormField is declared once, in @object-ui/types …

What went in:

FormField here means the one declared by @object-ui/types … @objectstack/spec ships its own copy of this name (json-schema/ui/FormField.json) with a different key set, so read this table against the @object-ui/types copy rather than the same-named schema in the spec.

⭐ This is the part I want to name. The order forbade replacing one unverifiable closure claim with another, and the obvious way to comply would have been to say less. Instead the sentence says more, and everything it adds is checkable: "here means" is a scoping statement, not a uniqueness claim, and the other copy is identified by file path — an existence claim a reader can resolve in one command. It also keeps the original's real insight (a locally written interface compiles no matter how far it has drifted), which I would have accepted losing.

Re-measured, and I re-derived the types side myself

23 / 29 / 14 reproduce. The card's line number had moved (form.ts:906 → :911), which is exactly why re-measuring rather than inheriting was required.

⭐ The counting decision is load-bearing and the dev flagged it rather than burying it: the 23 excludes [key: string]: any, which is present and is not a declared member. I checked that independently — FormField has 23 named members and an index signature.

⚠️ Carrying that forward, because it bears directly on the escalated half. An index signature means FormField is OPEN: annotating an object literal against it does not reject an undeclared key. This is the same fact that falsified my own option-2 ruling on #6143 (BaseSchema ends the same way). It does not make anything on this page false — the page counts declared keys and does not claim closedness — but whoever rules on the collision must not assume "annotate against the types copy" gives a reader protection it does not give.

⭐ The dev corrected my dispatch order, and it was a real error

My order named check:doc-snippet-types. That is the script file, not the npm script — the script is check:doc-snippets. Re-deriving the gate set from package.json and .github/workflows/ rather than from my list also surfaced check:doc-fences, which I did not name and which shares the snippet gate's exact scan surface. Both were run, both green.

That is the second defect in my own orders this round. Naming gates from memory instead of from the repo's own configuration is precisely the "confident wrong enumeration" failure this lane has been carding all evening, and I did it in the instruction telling someone else to derive scope from configuration.

Inclusion was measured, not assumed: check:doc-snippets reports 179 covered / 44 ungated, plugin-form.mdx is not in the declared ungated list, and the page holds 4 TS-family fences — so it is genuinely one of the covered pages that compile. Exclusion measured too: eslint --format json reports the file out of population.

⭐ And two verification habits worth repeating: the build cache reported FULL TURBO replaying another agent's worktree path, so dist materialisation was checked in this worktree before being trusted; and the on-disk edit check first read 0 hits because the anchor spanned a line break against a line-based grep — re-anchored rather than trusted. Both are the stale-artifact and zero-hit-lies traps, caught live.

Scope held, and the card stays open

No ruling on the collision class was made, proposed, or implemented. The PR says "Part of #6172", never a closing keyword, so the card survives its own PR — which is what a split card requires and is easy to get wrong.

#6172 remains needs-user-decision for: FormField (types 23 vs spec 29, 14 common), MarkdownSchema (content required vs optional), KanbanSchema (two shapes with almost nothing in common). And the constraint that rules out the cheapest option stands: three of the four KanbanCard declarations are inside @object-ui/plugin-kanban itself, so a package qualifier cannot disambiguate a name that collides with itself inside one package. #6155 stays pm:blocked behind it.

⭐ The out-of-scope finding is the best thing in this round

Filed as #6186 — three surviving prose closure claims that nothing re-derives. One of them is a genuinely sharp catch:

plugin-form.mdx:99 — "no ValidationRule type in this repository, under any spelling" — is test-pinned at scripts/__tests__/check-doc-component-types.test.ts:599 by a toContain that asserts the sentence EXISTS, not that it is TRUE.

A guard that pins the presence of a claim rather than its truth is worse than no guard: it reads as coverage, it goes green forever, and it makes the page look ratcheted while the claim rots. That is the #6086 class with a guard on top of it, and it is exactly the shape #6179 was cleaning up in the i18n baseline an hour ago. Correctly not fixed here — the dev searched for an existing card first, found none, measured none of the three false, and filed rather than widened.

---

Generated by Claude Code