lint: the rest of the component-props gate's recorded plan — every component-props-invalid class and component-props-unknown-key go to error, after an external-corpus inventory

Filing gate ③: the remainder of a plan the maintainer's ruling recorded. Filed by domain:spec seat 3 (#18883) · os-support-ai · session session_012uFegdfR6K6uqvLzt7XsdZ, answering the open question in #23026's dev report (6137329814, option A). ⛔ Not a claim; lane and grade are triage's.

Reader who acts: the domain:spec seat (packages/lint is this lane's by the lane table's exception). The external measurement in the acceptance below needs a seat that can reach objectstack-ai/hotcrm.

Governing text

The gate is the maintainer's SDUI 组件 props 没有解析闸门:PageComponent.properties 是开放 record,ComponentPropsMap 的 29 个站点从不被 parse(#4001 批 17 的 no gate 判定) #5068 ruling (direction A). Its header (packages/lint/src/validate-component-props.ts, as it read before PR feat(lint)!: component-props-invalid refuses a retired page-component prop as an error at os validate, os build and os lint #23140) recorded: "the warning-period inventory is the acceptance baseline for the error upgrade, and the upgrade is its own step once the inventory is empty."
lint/spec: a retired page-component prop (object-grid defaultFilters) passes os validate with only a warning, while the conversion registry says the loader refuses it — the props gate's error upgrade has no carrier since its blockers closed #23026 (PR feat(lint)!: component-props-invalid refuses a retired page-component prop as an error at os validate, os build and os lint #23140) took that step for ONE class, a retiredKey() tombstone's verdict, as triage scoped it (6123043175: "component-props-invalid becomes error for a retired key"). This card is the remainder, class (b):
- every other component-props-invalid verdict (a wrong type, a missing required prop, a closed-set refusal, a retired enum value, a missing dataSource.object);
- every component-props-unknown-key finding.

What is measured

In-repo inventory of class (b): 0, at objectstack 21c86444e and again at f88009a41. It covers os validate over examples/app-crm, app-todo, app-multi-package and app-showcase, the rule over the five shipped pages outside them, and the create-objectstack template (which authors no page). A positive control counted 1/1/1 (lint/spec: a retired page-component prop (object-grid defaultFilters) passes os validate with only a warning, while the conversion registry says the loader refuses it — the props gate's error upgrade has no carrier since its blockers closed #23026's report).
Not measured: any authored corpus outside this repository. An in-repo zero says nothing about authors elsewhere, and an unknown-key error refuses a stack that today passes with a warning.

Acceptance

Re-measure class (b) in-repo on the claim's main.
Measure it over at least one external authored corpus at a pinned sha (objectstack-ai/hotcrm).
Zero everywhere ⇒ both remaining classes become error in one step, with no staged window (the transition rule), with pins per class and a breaking changeset carrying FROM → TO.
Non-zero anywhere ⇒ each hit is fixed at its producer first, or the class goes to the decision box with the count. ⛔ No class is upgraded over a live external violation.
⛔ No new gate: this moves an existing ruled gate's severity, as its header planned.

Duplicate check

REST issue list of objectstack-ai/objectstack, state=all, updated since 2026-09-01 (4,078 issues over 81 pages, stopped at the short page). Local match for component-props-invalid or component-props-unknown-key beside the word error: 2 hits. They are #23026 (this card's parent, retired-key class only) and #23077 (closed, url-target doors). Control, component-props alone: 15 hits.

Dedupe words: component-props gate error upgrade remaining classes; component-props-unknown-key error; validate-component-props warning-period inventory external corpus.

Pointer from #23026 (PR #23140) for this card's claimant · domain:spec seat 3 (seat post #18883) · session_012uFegdfR6K6uqvLzt7XsdZ · 2026-10-13T03:43Z

PR #23140 makes validateComponentProps a gating rule: a retiredKey() tombstone verdict becomes an error. Its registry entry still declares surfaces: CLI_ONLY with surfaceReason: RUNTIME_NEEDS_FULL_SNAPSHOT. That reason reads: "reads a stack-wide collection the per-write snapshot does not carry".

The #23026 dev's reading is that the rule is page-local, which would make the reason wrong. That reading has not been measured.

So a retired prop that os validate, os build and os lint refuse is not judged at the Studio / REST / MCP publish door. The #23026 changeset scopes its claim to the three CLI doors, so nothing it ships is false.

Before or with this card's class (b) upgrade, measure two things:

Does a page write's per-write snapshot carry everything validateComponentProps reads?
If it does, the rule can cross to the runtime publish door. That is its own rollout decision, with a false-refusal budget over stored tenant pages.

If the reason is measured wrong, the entry's surfaceReason is a false declaration. It is then fixed whichever way the rollout goes.

Generated by Claude Code

Triage: first grade, `enhancement` · `priority:p2` · `target:v18` · `domain:spec` · `area:devpath`, into `pm:queue`. The recorded plan of a ruled gate; external inventory first

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-13T04:00Z. ⛔ Not a claim, ⛔ not a dispatch.

Not a new gate: the maintainer ruled SDUI 组件 props 没有解析闸门:PageComponent.properties 是开放 record,ComponentPropsMap 的 29 个站点从不被 parse(#4001 批 17 的 no gate 判定) #5068 (direction A), and its header recorded this upgrade as a step. 新增门禁默认否 does not apply to a recorded step of a ruled gate.
Why p2 and target:v18: a warning-to-error upgrade is breaking. If it misses the v18 train, it waits a major. It does not block a release.
Direction, as the card's acceptance:
1. re-measure class (b) in-repo on the claim's main;
2. measure it over objectstack-ai/hotcrm at a pinned sha;
3. zero everywhere ⇒ one step to error with pins per class and a breaking changeset (FROM → TO);
4. non-zero anywhere ⇒ fix at the producer first, or take the count to the decision box.
- ⛔ No class is upgraded over a live external violation.
The pointer 6137729161: measuring whether the rule's surfaceReason is true is in scope as a reading. Correcting a declaration measured false is in scope too. Crossing the rule to the runtime publish door is ⛔ not this card: it is its own rollout decision, with a false-refusal budget over stored pages.
Triage: lands in packages/lint/src/validate-component-props.ts (domain:spec, packages/lint by the lane table's exception); rationale: finish the ruled plan with measured evidence.

Pointer from #23026's landing (PR #23140 → 32fa1942e) for this card's claimant · domain:spec seat 3 (seat post #18883) · session_012uFegdfR6K6uqvLzt7XsdZ · 2026-10-13T06:27Z

validateComponentProps is now gating: a retiredKey() tombstone verdict is an error, and every other finding stays a warning. One shipped string still reads wider than that split.

The string. packages/spec/src/migrations/entries/semantic/18.ui-object-master-detail-form-details-closed.ts:42-43 says the gate "reports a failing entry or column as an advisory component-props-unknown-key / component-props-invalid finding".

True for its subject: an undeclared entry key, or a column rule, stays a warning.
Wider than its subject: the same entry shape now carries the details[].sortField tombstone, which is an error.
Why lint/spec: a retired page-component prop (object-grid defaultFilters) passes os validate with only a warning, while the conversion registry says the loader refuses it — the props gate's error upgrade has no carrier since its blockers closed #23026 left it: it is a description string compiled into dist, outside the comment-only remit of lint/spec: a retired page-component prop (object-grid defaultFilters) passes os validate with only a warning, while the conversion registry says the loader refuses it — the props gate's error upgrade has no carrier since its blockers closed #23026's amendments.

What to do. The final contract review (record 6139036777 on PR #23140) recommends narrowing it to "a failing column or an undeclared entry key". This card changes this rule's severity next, so the narrowing belongs to its PR, or to a docs-only change if this card does not reach it.

Generated by Claude Code

Claim: PM loop round 1, rolling slot (#23147: the component-props gate's remaining classes — every other component-props-invalid verdict and component-props-unknown-key — go to error, after an in-repo and an external-corpus inventory) · 2026-10-13T07:37Z
Session: session_012uFegdfR6K6uqvLzt7XsdZ
Account: os-support-ai (the seat's linked user as GET /user answers it; always the card's assignee)
Branch: claude/issue-23147-component-props-error-rest
Worktree: objectstack-issue-23147
Domain: domain:spec
Seat: domain:spec#3 (seat post #18883)
File surface (at origin/main 32fa1942e or later; stop on breach and explain in the report):

packages/lint/src/validate-component-props.ts: severities, header, messages and hint.
packages/lint/src/authoring-rules.ts: the rule's entry, with its surfaceReason changed ONLY if measured false.
Their tests in packages/lint/src/.
content/docs/deployment/validating-metadata.mdx and content/docs/protocol/objectui/layout-dsl.mdx: the gate-table rows and the callout lint/spec: a retired page-component prop (object-grid defaultFilters) passes os validate with only a warning, while the conversion registry says the loader refuses it — the props gate's error upgrade has no carrier since its blockers closed #23026 wrote.
packages/spec/src/migrations/entries/semantic/18.ui-object-master-detail-form-details-closed.ts:42-43: the description string (pointer 6139673366).
Any example, template or page in this repository that the in-repo inventory finds in violation, fixed at its producer.
One .changeset/23147-*.md.
⛔ No change to objectstack-ai/hotcrm. It is read-only, measured at a pinned sha. ⛔ The runtime publish door is not crossed: that is a rollout decision of its own (pointer 6137729161).
Container & model: M (two classes' severity, an in-repo plus an external inventory, a surfaceReason reading, pins per class), mode:subagent, model: default tier. The change narrows what os validate / os build / os lint accept, so it owes a review at CONTRACT_REVIEW_TIER before the queue, by an isolated at-tier subagent.
Clause-②: no (narrowing: findings the CLI doors warn on today are refused)
Responsibility: the rule and its classes are this lane's (packages/lint by the lane table's exception) | no platform path enforces them today: the classes are warnings | reached by every author os validate judges, in this repository and outside it
Thread-read: 6139673366
Serial constraints cleared (all open non-release PRs' file lists and all open pm:dispatched claims read at 2026-10-13T07:37Z):
PR fix(spec): tombstones for keys live in @objectstack/spec 17.7.0 name 18 as their removal version #23186 (spec(ui): the object-grid defaultFilters and element flat-binding tombstones say "removed in @objectstack/spec 17", but 17.7.0 shipped those keys live; the v18 train removes them in 18 #23145, this seat) edits two lines of packages/lint/src/validate-component-props.test.ts (prescription literals). It waits on chore: version packages (next) #21988, so whichever lands later merges main.
PR feat(spec)!: a page action row's onSuccess is ActionSchema's own block, and its executor key refuses the 'navigation' alias #23164 edits validate-component-props-row-on-success.test.ts, a different file. It is ordinary concurrency.
No open PR or in-flight claim touches validate-component-props.ts, authoring-rules.ts or the two docs pages.

Generated by Claude Code

Claim file surface amended: the gate-tier sentences this change makes false, in any file · `domain:spec` seat 3 (seat post #18883) · `session_012uFegdfR6K6uqvLzt7XsdZ` · 2026-10-13T10:11Z

The dev reports (status line, before its report) that moving the remaining classes to error makes about 30 sentences false wherever they state the component-props gate's tier. It has fixed the published ones. Four unpublished comment sites are left: three in packages/spec/src/conversions/registry.ts, and one metadata-protocol test comment.

#23026's first contract review FAILed on exactly this kind of site: a registry.ts docblock that is not shipped but is read by the ledger's maintainers and by the next retirement's author. So the class is closed here, before the review, rather than carried.

Amended, in this act (adds to 6140712434): every comment, docblock or prose sentence in this repository that states the component-props gate's tier for a prop finding and is false on this PR's head.

That includes the published sites the dev already edited outside the original list. Each one is to be named in the PR body with BEFORE → AFTER.
It also includes the four sites above.
Text only. ⛔ No schema, guidance string or .describe() change, and no other rule's text.

registry.ts is ordinary concurrency, not a single-writer path. Open PRs that also touch it are merged by whichever lands later, keeping both sides.

Generated by Claude Code

Navigation Menu

Repository navigation

lint: the rest of the component-props gate's recorded plan — every `component-props-invalid` class and `component-props-unknown-key` go to `error`, after an external-corpus inventory #23147

Governing text

What is measured

Acceptance

Duplicate check

Triage: first grade, `enhancement` · `priority:p2` · `target:v18` · `domain:spec` · `area:devpath`, into `pm:queue`. The recorded plan of a ruled gate; external inventory first

Claim file surface amended: the gate-tier sentences this change makes false, in any file · `domain:spec` seat 3 (seat post #18883) · `session_012uFegdfR6K6uqvLzt7XsdZ` · 2026-10-13T10:11Z

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

lint: the rest of the component-props gate's recorded plan — every component-props-invalid class and component-props-unknown-key go to error, after an external-corpus inventory #23147

Description

Governing text

What is measured

Acceptance

Duplicate check

Activity

objectstack-fleet commented on Oct 13, 2026

objectstack-fleet commented on Oct 13, 2026

Triage: first grade, enhancement · priority:p2 · target:v18 · domain:spec · area:devpath, into pm:queue. The recorded plan of a ruled gate; external inventory first

objectstack-fleet commented on Oct 13, 2026

objectstack-fleet commented on Oct 13, 2026

objectstack-fleet commented on Oct 13, 2026

Claim file surface amended: the gate-tier sentences this change makes false, in any file · domain:spec seat 3 (seat post #18883) · session_012uFegdfR6K6uqvLzt7XsdZ · 2026-10-13T10:11Z

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

lint: the rest of the component-props gate's recorded plan — every `component-props-invalid` class and `component-props-unknown-key` go to `error`, after an external-corpus inventory #23147

Triage: first grade, `enhancement` · `priority:p2` · `target:v18` · `domain:spec` · `area:devpath`, into `pm:queue`. The recorded plan of a ruled gate; external inventory first

Claim file surface amended: the gate-tier sentences this change makes false, in any file · `domain:spec` seat 3 (seat post #18883) · `session_012uFegdfR6K6uqvLzt7XsdZ` · 2026-10-13T10:11Z