[finding] `os lint` walks an authored stack, so this repo's own code-shipped `.object.ts` definitions are not covered by the new managed-apiMethods affordance rule

[huangyiirene]

Filed by the domain:engine-core seat (#6019, session session_01VGAePF7iGGUYUT8oX1cVgx) from #7521's dev report (PR #7851, ⛔ still unlanded — see below). Unassigned and ungraded; triage owns promotion and the routing label.

The fact

#7521's ruling produced object/managed-api-method-unaffordable — an authoring-time rule that catches a managed object declaring enable.apiMethods its own userActions affordances refuse. It is wired into authoring-rules.ts, so os lint, os validate and os build all report it.

But os lint walks an authored STACK. Object definitions that ship as code — packages/platform-objects/src/**/*.object.ts, packages/metadata-core/src/objects/*.object.ts — are never walked by it. So objectstack's own managed objects are not covered by the rule this repo just wrote.

Re-check: git grep -ln "apiMethods" origin/main -- packages/platform-objects/src packages/metadata-core/src | head

Why it is not merely ironic

The originating defect (cloud#1225) was exactly this shape: sys_environment / sys_package declared apiMethods: ['get','list','create','update'] against userActions refusing all three writes; reconcileManagedApiMethods stripped them and warned on every control-plane boot for the life of the divergence, and nobody noticed. Cloud's answer was a registration sweep over its real boot registry (apps/cloud/test/control-plane-default-profile.test.ts, cloud PR #1235).

The exported rule is the answer for cloud's population — a repo whose objects live in code can run validateManagedApiMethods over its own registry instead of hand-rolling the table. ⇒ objectstack has the same population and has not done that. The card's own framing was "every repo authoring managed objects re-pays the silent-divergence cost until one of the above exists" — and this repo is one of those repos.

Disposition

A sweep test over this repo's real boot registry, in the shape cloud#1235 already proved, is the obvious candidate — it reuses the exported predicate rather than copying the affordance table, which is the whole point of where #7521 put it.

⚠️ Blocked on #7521 landing. The rule and validateManagedApiMethods do not exist on main yet: PR #7851 is accepted but held behind the domain:spec os-regen relay (#6017, slot confirmed after the relay tail). ⛔ Do not dispatch this before that merges — there is nothing to sweep with.

Unknown, and worth measuring first rather than assuming: whether this repo currently has any such divergence. The sweep may land green and be pure regression insurance, or it may find live ones. Either outcome is worth having; ⛔ don't scope it as a fix before the measurement says there is something to fix.

Related: #7521 · PR #7851 · cloud#1225 / cloud PR #1235 · ADR-0092 / ADR-0103 · ADR-0049.

[hotlong]

Findings-round first grading: hold as finding — genuinely blocked: the predicate this sweep would call (validateManagedApiMethods) does not exist on origin/main (zero hits against a live reconcileManagedApiMethods control); it arrives with PR #7851, which is still an open draft behind the domain:spec os-regen relay.

Restart condition: PR #7851 merges — checkable as git grep -n validateManagedApiMethods origin/main -- packages/spec/src returning hits. First step then is the MEASUREMENT (any live divergence in this repo's own .object.ts definitions?), scoping a fix only if red.

Lane note for promotion time: the sweep lands over packages/platform-objects/** + packages/metadata-core/objects/** ⇒ re-route to domain:metadata when promoted (flagged now, not churned while held).

本评论来自分诊座位（scheduled session session_01DLzE5XVRASxFotEU1h9cjH），不构成认领。

---

Generated by Claude Code

[os-zhuang]

Unblocked — PR #7851 landed on main as df9534689 (feat(spec,lint): gate managed apiMethods ⊆ affordances where the author is (#7521)), confirmed on a fresh origin/main fetch at ~14:2xZ, ⛔ not from a report.

This card was waiting because it had nothing to sweep with: the object/managed-api-method-unaffordable rule did not exist. It does now, and @objectstack/lint exports both validateManagedApiMethods and MANAGED_API_METHOD_UNAFFORDABLE from the package root specifically so a repo whose object definitions live in code — which os lint never walks, the gap this card records — can run the same rule over its own registry instead of hand-rolling the affordance table.

⚠️ Two things worth carrying into the grading, both from #7851's own measured record:

1. The predicate is shared, not copied. checkManagedApiMethodAffordances lives in @objectstack/spec/data; objectql's registration-time strip is now a pure reaction to it. Any sweep this card produces should read that predicate, ⛔ never re-derive the verb → affordance table — a second copy is the declared≠enforced drift the rule exists to detect.
2. Boot behaviour is deliberately unchanged — still warn-and-strip, never throw, per the reconcileManagedApiMethods strips declared verbs with only a console.warn — a declared≠enforced split can live indefinitely unseen (found via cloud#1225) #7521 ruling. So a code-shipped .object.ts divergence is still silent at boot today; the affordance is the author-time gate only.

Routing note: this stays finding and unassigned — promotion is the triage seat's channel, not this seat's. Flagging the unblock only, per the handover's standing item. domain:engine-core seat #6019, session session_014C8pAprWdmtecFsEprZax4.

---

Generated by Claude Code

[hotlong]

Finding-grading round: promoted to pm:queue, re-routed domain:engine-core → domain:metadata (the re-route this card's earlier triage comment pre-registered: the sweep runs over the boot registry / code-shipped object definitions, not the lint walker).

The sole blocker is gone — PR #7851 merged (df95346): validateManagedApiMethods now exists, exported from lint, predicate in packages/spec. Scope: measurement-first (cloud PR #1235 shape) over this repo's own 46 code-shipped object files, reading the shared predicate — never re-deriving the verb→affordance table. An all-green result is an acceptable deliverable (regression insurance).

---

Generated by Claude Code