[maintainer] validate: the field-no-consumers warning is one 856-character line, printed by validate, build and dev alike — one-line verdict + rule: id + a pointer to the full reasoning (os explain, which today takes only schema names)

Blocked-by: #22949
Unlock-action: re-check PR #22936

Filing gate: ③ task dispatched by the maintainer, quoted verbatim below; measurements class (a), this session.
reach: pnpm run validate on the tutorial project prints the warning as a single 856-character line (the whole validate output is 1,734 characters, so the one warning is half of it); pnpm run build prints it plus a second ~700-character "Give … a consumer" paragraph; npx os dev prints both again on every compile.
Reader: domain:spec seat for the rule text (packages/lint, author-time rule field-no-consumers); domain:cli seat for the printer and for an os explain entry point that can take a rule id (packages/cli/src/commands/explain.ts accepts schema names only: os explain [SCHEMA]).
Dedup: search_issues "validate warning message too long field-no-consumers paragraph unreadable terminal shorten one line rule id os explain" → 3 hits, all closed and none about message length: #17135 (what the rule counts as a consumer), #11529 (the 50-warning cap), #11947 (line-length gate for repo files).
Filed on the maintainer's instruction in this session (category ③, quoted verbatim): 「validate 的警告段落约 900 字符,不可读。 field-no-consumers 在 validate、build、dev 各打一次整段。建议一行裁决 + rule: id + "os explain field-no-consumers 看完整推理",长文搬进 explain 或文档」

Today

  ⚠ object "my_app_ticket" · field "description": field "description" on object "my_app_ticket" is declared but nothing in this stack reads or displays it: no view column, inline grid column, form section, page binding, flow node, dataset or cube member, widget, formula, validation, hook or action names it, no declared field group places it on the synthesized layout, and no seed or import mapping matches on it. A translation label, a seed value, an import-mapping target, a permission grant, a flow that only WRITES it, an `inlineColumns` entry on a relationship field that does not set `inlineEdit` (no grid is drawn), or a dataset or cube member path the analytics door refuses (a hop or column that does not resolve, or a join the dataset's `include` does not declare) is a carrier, not a consumer. Verdict: inert — no site of any kind names it.
    rule: field-no-consumers  at objects[1].fields.description

One line, 856 characters, no wrap. build adds the second paragraph ("Give "description" a consumer — a view column, a form section, … Roots scanned: objects, views, pages, apps, flows, dashboards, reports, datasets, actions, hooks, jobs, emailTemplates, agents, tools, skills, apis, webhooks, sharingRules, analyticsCubes (consumers) · translations, data, mappings, permissions (carriers); test fixtures are never scanned."). The reasoning is correct and complete; it is also unreadable at 80 columns and arrives three times per edit-run loop.

Asked for

  ⚠ object "my_app_ticket" · field "description" is declared but nothing displays or reads it (inert)
    fix: add it to a view column / form section, or remove the declaration
    rule: field-no-consumers  at objects[1].fields.description — `os explain rule field-no-consumers` for what counts as a consumer

One sentence of verdict, one line of fix, the rule: line as it is today.
The exhaustive list of consumer and carrier kinds moves to os explain rule <id> (new: explain currently takes only a schema name) and/or the rule's docs page; the message carries the pointer.
Same shape for every author-time rule whose message today exceeds ~200 characters — the dead-button action-governance line and the security-owd-unset refusal are the next two a newcomer meets.
validate prints a warning once per run; dev prints it once per compile, not again at serve.

Generated by Claude Code

Triage: first grade, `enhancement` · `priority:p3` · `domain:spec` · `area:devpath` · `pm:queue` (`finding` removed). Direction: as the maintainer wrote it, a one-line verdict, a fix line, and the `rule:` line with a pointer to `os explain rule <id>`

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

Triage: lands in packages/lint (the author-time rule messages, starting with validate-field-consumers.ts) plus packages/cli/src/commands/explain.ts ⇒ domain:spec; rationale: most of the change is rule text, and packages/lint is the spec lane's.

Grade: p3, the same as the rest of this newcomer walk-through batch ([maintainer] dev-mode noise budget: a blank project written verbatim from the tutorial boots with 4 WARN lines and only one needs the author's hand — expected degradations to info, stacks only at debug, the actionable line highlighted with a one-line fix #22160, [maintainer] create-objectstack: the blank template's pnpm-workspace.yaml is 85 lines, 66 of them peer-dependency commentary — the third-largest file in a "clean slate" project; keep the file minimal and move the rationale out #22162–[maintainer] docs(getting-started): four overlapping entry pages (How AI development works / Build with Claude Code / Your First Project / Anatomy) — add one routing line at the top of the index so a newcomer does not have to choose #22165, graded in R242). This one was missed in that round. The output is unreadable, but nothing is wrong or lost.
One cross-lane PR: the message pointer is only true once os explain accepts a rule id. os explain [SCHEMA] takes schema names only today (explain.ts, SCHEMAS). So the explain entry rides the same PR, and the domain:cli seat reviews the packages/cli files. ⛔ Do not ship the shortened message before the entry exists.
Where the long text goes: the full reasoning moves into one static explanation per rule, exported from packages/lint and keyed by rule id. os explain rule <id> prints it, and nothing else carries a copy. There is no rule docs page today to point at instead.
Scope: the maintainer named "every author-time rule whose message today exceeds ~200 characters". Enumerate them first, by measured length, and pin the enumeration in a test that fails on a new over-long message.
Clause-②: yes, by my reading. A new os explain rule <id> form widens the CLI's surface. The claiming seat confirms.

Claim: PM loop round 1 · 2026-10-08T16:37Z
Session: session_01DhTqaEHqPVSVnAkjG3jywn
Account: os-sales (the seat's linked user as GET /user answers it; the card's assignee from this act)
Branch: claude/issue-22161-rule-message-one-line
Worktree: objectstack-issue-22161
Domain: domain:spec
Seat: domain:spec#2 (seat post #18549)
File surface (at origin/main 4e4111ca0 or later; stop on breach and explain in the report):

packages/lint/src/validate-field-consumers.ts: the field-no-consumers warning becomes one verdict sentence and one fix line, and the rule: line points at os explain field-no-consumers. The build-time "Give … a consumer" paragraph takes the same shape wherever it is produced.
One static explanation per rule id, exported from packages/lint (a new module plus packages/lint/src/index.ts). The long text moves there, and nothing else carries a copy.
The other author-time rules whose message exceeds about 200 characters, enumerated first by measured length: starting with the dead-button action-governance line (authoring-rules.ts) and security-owd-unset (validate-security-posture.ts), same shape. ⛔ Not a rule whose message lives in a file an open PR edits at this stamp (validate-expressions.ts, lint-flow-patterns.ts, validate-flow-template-paths.ts, edited by PRs fix(lint)!: os build and the object save door refuse a select option's visibleWhen that reads parent (#22157) #22268, feat(spec)!: flow text slots read the {{ }} delimiter, refusing a single-brace token with its hole spelling (#22110) #22315, fix(spec,service-automation)!: an undeclared config key on 10 more builtin node types is refused at the build doors; one judge per type #22319). Those are enumerated and left for a second stage on this card.
packages/cli/src/commands/explain.ts: os explain <rule-id> prints that rule's explanation, and a schema name resolves as today. This is the maintainer's spelling, os explain field-no-consumers, with no rule sub-word; triage's os explain rule <id> is not taken. The cli printers (commands/validate.ts, build.ts, dev.ts) change only if a measurement shows one run printing the same warning twice. Tests for each.
.changeset/22161-*.md: @objectstack/lint minor, @objectstack/cli minor.
⛔ No new gate and no ratchet test on message length. Triage's "a test that fails on a new over-long message" is not taken: a new gate needs the maintainer's naming. Each shortened rule's own test pins its new shape.
Declared cross-lane files: domain:cli (packages/cli), declared on [PM seat] domain:cli — ⏳ vacant #6024.
Container & model: M, mode:subagent, model: opus (dispatch-gates --tier --repo objectstack-ai/objectstack on these paths: no path-derived mandate; the default tier). A contract review at CONTRACT_REVIEW_TIER is owed before enqueue (this claim's Clause-②: yes), from an isolated at-tier subagent.
Clause-②: yes (widening: os explain accepts a rule id, and packages/lint exports the rule explanations)
Responsibility: n/a — not a defect card
Thread-read: 6054524310
Serial constraints cleared:
The three packages/lint files that open PRs fix(lint)!: os build and the object save door refuse a select option's visibleWhen that reads parent (#22157) #22268, feat(spec)!: flow text slots read the {{ }} delimiter, refusing a single-brace token with its hole spelling (#22110) #22315 and fix(spec,service-automation)!: an undeclared config key on 10 more builtin node types is refused at the build doors; one judge per type #22319 edit are excluded above.
Open PR feat(spec)!: PROTOCOL_VERSION 17 → 18 in an ordinary PR — regenerated spec-changes.json and upgrade guide, ^18 handshakes, pre-mode lockstep exception (#22085 Q1 → B) #22215 edits three packages/cli/src/utils/*.test.ts files and open PR fix(cli): os serve and seven sibling readers read a multi-package config's package-owned keys through its package bodies #22321 edits packages/cli/src/commands/generate.ts and serve.ts. None is on this surface. If a rule's message turns out to live there, it is named in the report, not edited.
No open PR touches validate-field-consumers.ts, authoring-rules.ts, validate-security-posture.ts, packages/lint/src/index.ts or explain.ts (the 13 open PRs' file lists, read at this stamp).

os-dev-report
{
"issue": 22161,
"status": "done",
"branch": "claude/issue-22161-rule-message-one-line",
"pr": "#22339",
"session": "session_01DhTqaEHqPVSVnAkjG3jywn — the dispatching seat's session (this run is mode:subagent; the harness stamped the same id on every commit trailer)",
"premise_still_valid": true,
"summary": "Stage 1 of #22161, scoped by the dispatch's stop condition (H5 measured 157 rule ids with a message over 200 chars, far more than 8): the mechanism plus field-no-consumers and security-owd-unset; the PR body opens with 'Part of #22161' and lists the second stage with measured lengths. Mechanism: one static explanation per rule id in @objectstack/lint (RULE_EXPLANATIONS / explainRule, new module rule-explanations.ts, exported from the root barrel and from a new import-free entry @objectstack/lint/rule-explanations); 'os explain RULE_ID' resolves an exact rule id after the schema names (one positional, the maintainer's spelling); the rule: line carries the pointer, spelled once in packages/cli/src/utils/format.ts (explainPointer / authoringFindingDetailLines), printed only for ids the table holds; the hint line is labelled 'fix:'. Measured on a tutorial-shaped project: os validate field-no-consumers 852 chars on one line before, now 114/77/126 (verdict/fix/rule); os build 852+692+62 before, same 3 lines after; security-owd-unset 374+175+58 before, 156/160/130 after. Premise corrections, measured: (1) before this change os validate printed NO rule line and no fix for a registry warning (only the 'warning' line; the card's 'Today' block is build's shape), so validate.ts now renders the same fix/rule lines via the shared helper; (2) H4 false: one 'os dev --compile' run prints the warning once (the compile child), not again at serve — no printer change for it; (3) the dead-button action-governance line is not an author-time rule and is not in authoring-rules.ts: it is the boot-time logger.warn in packages/objectql/src/action-governance.ts:584 (163 chars + payload; sibling at :568 is 628) — named, not edited (stop condition). Also fixed in-PR because this change rewrote the lookup block: 'os explain constructor' / 'proto' printed 'Schema: Object … undefined' and threw 'schema.required is not iterable' on main; both lookups are own-key reads now (commit 6d2eb85, pinned, ablated red).",
"tests": "lint: 'pnpm --filter @objectstack/lint exec vitest run --maxWorkers=2' → Test Files 128 passed (128), Tests 5853 passed (5853) at ed786eb (no lint file changed after it); 'pnpm --filter @objectstack/lint run typecheck' → exit 0, check:test-typecheck OK (2 files / 6 errors / 2 pinned signatures held). cli: 'pnpm --filter @objectstack/cli run typecheck' → exit 0, check:test-typecheck OK (3/28/6 held) at 6d2eb85. Unit tier in full, three foreground shards ('--project unit --shard=N/3'): shard 1 89 files/1523 tests passed and shard 2 88 passed + 1 failed at ed786eb; shard 3 89/1264 passed at 315a266; the shard-2 failure (src/utils/author-time-rules.test.ts read the field name from message) fixed in 315a266 and re-run with test/lint-per-package-authoring-seam.test.ts → 2 files/10 tests passed; test/explain-rule-id.test.ts + test/commands.test.ts → 2 files/61 tests passed at 6d2eb85. Integration tier (declared to CI as a whole; ran the ten files that spawn validate/build/verify/lint and read their text) → Test Files 10 passed (10), Tests 62 passed (62) at 315a266. Nightly tier: OS_TEST_TIERS=nightly test/rule-line-explain-pointer.e2e.test.ts → 2 passed; validate-json-warning-parity.e2e.test.ts → 3 passed. Ablations (one-shot, via scripts/ablation-replace.mjs, on committed state, restore proven blob==HEAD and git diff HEAD empty): (a) explainPointer return → '' in format.ts (blob 9d90c98c409d → 4427f41a866d): explain-rule-id.test.ts 3 failed | 7 passed; (b) own-key schema lookup reverted to SCHEMAS[schemaKey] in explain.ts (blob 09b7564b4b6c → 1159a49bff27): 1 failed | 10 passed. CLI src is run from source by vitest, so no build/dist leg applies. Cross-package read: the CLI build compiles against @objectstack/lint/rule-explanations, which exists only in the rebuilt dist (rule-explanations.{js,cjs,d.ts,d.cts}); CJS require and ESM import of it both load. ESLint narrowed to the diff: 'npx eslint --no-inline-config --format json' over the 18 changed .ts files → 18 files in the report, 0 errors, 0 warnings; eslint.config.mjs never enables type-aware linting (its own comment at :327), so untouched files cannot change verdict. Manual: os validate / build / dev / lint / explain on the scratch project before and after (lengths in summary).",
"mcp_calls": "0 — no MCP tool used",
"api_writes": "3 — every write through the fleet-write relay (POST /repos/objectstack-ai/objectstack/dispatches, executed as objectstack-fleet[bot]): (1) pr_create → POST /repos/objectstack-ai/objectstack/pulls (draft, #22339; read-back 21042 bytes sent = stored); (2) label-write.mjs --assign os-sales → POST /repos//issues/22339/assignees (read-back matches; size/l was added by the size labeler, not by this write); (3) post-stamped.mjs os-dev-report → POST /repos//issues/22161/comments. Reads via gh api (issue + comments) and the relay's own read-backs. git push (6 pushes of the branch) is not a REST write.",
"open_questions": [],
"out_of_scope_findings": [
"carrier: second stage of #22161 itself (not a new card) — 124 more author-time rule ids in packages/lint with a fired message over 200 chars, 19 in the three excluded files (validate-expressions.ts, lint-flow-patterns.ts, validate-flow-template-paths.ts; open PRs #22268 #22315 #22319), 8 whose message lives in packages/spec/src/kernel/functional-completeness.ts, and the action-governance boot-log lines in packages/objectql/src/action-governance.ts:568/:584 — all listed with measured lengths in the PR body's 'Second stage' section; each takes the same shape (text into RULE_EXPLANATIONS, one verdict + one fix, pin in the rule's own test).",
"noted, not filed (observation): security-owd-unset also runs on the runtime publish gate, so Studio/REST/MCP refusals now carry the shorter message and hint while the explanation is reachable from the CLI only — recorded in the PR's Acceptance notes; no consumer is broken (the runtime wire carries rule/path/message as before)."
],
"gates": {
"derived": "node scripts/pm/dispatch-gates.mjs --commands (no paths) at 6d2eb85 → 78 commands (identical set at 315a266), a superset of the 51 in the dispatch gate file (comm: none missing)",
"run": "all 78 at 6d2eb85: 78 exit 0 (the first battery at 315a266 had check:dual-build-cjs-loads and check:i18n-coverage at exit 3 PREREQUISITE NOT MET; at 6d2eb85 both exit 0 — the missing dists had been built by gates in the first battery). After the two changeset-only commits (head c76a01b) re-ran the 20 changeset/text families plus check-adr-0087-registration: all exit 0. Also exit 0: check:authz-resolver, check:error-code-casing, check:filter-alias-parity, check:published-readme-exports, check:published-readme-links, check:cli-examples-parity; control-char scan of every changed file: no match.",
"ran_verdict": "✓ dispatch-gates --ran: 78 derived famil(ies) accounted for — 78 run, 0 NOT-MEASURED (a DERIVED zero — all 78 recorded an exit code and none of them is 3).",
"ci": "PR #22339 CI not awaited (PM's)."
},
"line_budget": "21 files, +832 / -63 vs merge base 59d993c (head c76a01b); governed paths touched: 0",
"deviations": [
"Landing outside the claim's file surface (each in the PR body with its reason): packages/cli/src/utils/format.ts (the H2 printer — pointer and fix/rule lines spelled once); packages/cli/src/commands/validate.ts (measured: validate printed no fix and no rule line, so the shortened message needed the pointer there; the --strict/--json warnings list is unchanged); packages/cli/src/commands/lint.ts (os lint's rule line gets the same pointer); packages/lint/package.json + tsup.config.ts + rule-id-barrel-exports.test.ts (new import-free entry ./rule-explanations: format.ts is documented as no rule-engine import and loading the lint root barrel measured 456-547 ms per command); packages/cli/README.md (explain row).",
"The claim placed the action-governance line in authoring-rules.ts; measured, it is a boot log in packages/objectql — named and not edited, per the stop condition. So the PR body's first line is 'Part of #22161'.",
"The claim said the cli printers validate.ts/build.ts/dev.ts change only on a measured duplicate; H4 measured no duplicate and build.ts/dev.ts are untouched, but validate.ts changed for the H2 reason above (no rule line existed at validate).",
"In-PR fix beyond the claim: os explain's schema lookup made own-key (constructor/proto crashed on main) because this change rewrote that block; commit 6d2eb85 + changeset line. The PR body (written once, at pr_create) does not mention it: seat to append under '## What changes' one bullet — 'os explain schema lookup is an own-key read: os explain constructor / proto printed Schema: Object … undefined and threw schema.required is not iterable on main; now refused as an unknown id (6d2eb85; pinned in test/explain-rule-id.test.ts; own-key check reverted → 1 failed | 10 passed)' — and update 'head 315a266' in the Tests heading to c76a01b with the gate rerun line from this report's gates.run.",
"Branch not merged with origin/main (4 commits behind at PR open; none touches a file in this diff, checked by name). The full CLI unit tier ran as three shards because one foreground run exceeded the container cap under lock contention.",
"Commit trailers use the model-free pair (Claude-Session + 'Co-authored-by: Claude') per AGENTS.md, not the harness reminder's model-named Co-Authored-By line; PR footer uses the AGENTS.md session-URL form, not the reminder's text."
],
"files_changed": [
".changeset/22161-rule-message-one-line.md",
"packages/cli/README.md",
"packages/cli/src/commands/explain.ts",
"packages/cli/src/commands/lint.ts",
"packages/cli/src/commands/validate.ts",
"packages/cli/src/utils/author-time-rules.test.ts",
"packages/cli/src/utils/format.ts",
"packages/cli/test/explain-rule-id.test.ts",
"packages/cli/test/rule-line-explain-pointer.e2e.test.ts",
"packages/cli/test/truncation-remainder-notices.test.ts",
"packages/cli/test/validate-build-gate-parity.test.ts",
"packages/lint/package.json",
"packages/lint/src/index.ts",
"packages/lint/src/rule-explanations.test.ts",
"packages/lint/src/rule-explanations.ts",
"packages/lint/src/rule-id-barrel-exports.test.ts",
"packages/lint/src/validate-field-consumers.test.ts",
"packages/lint/src/validate-field-consumers.ts",
"packages/lint/src/validate-security-posture.test.ts",
"packages/lint/src/validate-security-posture.ts",
"packages/lint/tsup.config.ts"
]
}

Generated by Claude Code

Seat review of PR #22339 at `c76a01bb6`: patch round 2 (one defect the diff creates, plus the docs blocks it makes false), then the contract review

domain:spec seat 2 (#18549) · os-sales · session session_01DhTqaEHqPVSVnAkjG3jywn · 2026-10-08T19:27Z · holder of claim 6064555982. This amends that claim's file surface. ⛔ Not a new claim.

The build report is 6067329013. The seat read the whole diff at c76a01bb6 (21 files, +832 / -63 against merge base 59d993c97).

Accepted as reported:

The mechanism: RULE_EXPLANATIONS / explainRule keyed by rule id, the exact-id lookup after the schema names, and the two reshaped rules.
The Part of #22161 first line and the stage-2 list in the PR body.
The landings outside the claim's surface, each with its measured reason:
- packages/cli/src/utils/format.ts: the pointer, spelled once.
- commands/validate.ts: validate printed no rule: line. The index map is append-only between the push and the print, so it lines up.
- commands/lint.ts: the pointer.
- The import-free @objectstack/lint/rule-explanations entry: 456–547 ms measured for the root barrel. It sits inside the claim's Clause-②: yes (widening) line, which already names "packages/lint exports the rule explanations".
- The README row.
- The own-key fix in explain.ts: the lookup block this change rewrote.
H4 measured false, so build.ts and dev.ts are untouched.
The action-governance line is named, not edited.
The runtime note: runtime-authoring-gate.ts toIssue carries where and hint on the 422's issues. A Studio, REST or MCP author still gets the object (where) and the four values (hint); only the reasoning moved to the CLI. That stays in ## Acceptance notes.

The defect: a fix: label on a line that is not a fix. authoringFindingDetailLines prefixes every finding's hint with fix: . packages/lint/src/authoring-rules.ts:687 sets hint: \source: `${i.source}``forexpression-invalid, the gating rule an author meets most. So every one of its findings now prints fix: source: `status != "resolved"`. That line tells the reader the fix is the expression they already wrote. Before this PR it printed source: …, unlabelled. The maintainer's shape (fix:on the fix line) is right, and this PR's own changeset says every hint line is now labelledfix:. So the label is kept, and what is not a fix leaves hint`.

Patch round 2 (same dev, same branch, merge origin/main first):

Measure first. Enumerate every producer of an author-time finding's hint in packages/lint/src/** and packages/spec/src/kernel/functional-completeness.ts whose text is not a fix: a quote of the authored value, a location, or context. :687 is one. List each with file:line in the report.
Fix each one at its producer. What it carries goes to the field that fits: the verdict (message), or where/path for a location. Nothing goes in a printer-side label sniff (⛔ no startsWith('source:') branch in format.ts). For expression-invalid, the authored source stays visible on the text face and on the runtime 422 issue. If its message changes, state that runtime-wire change in the changeset.
- ⛔ Not a producer in validate-expressions.ts, lint-flow-patterns.ts or validate-flow-template-paths.ts. Open PRs edit those files, and :687 is in authoring-rules.ts, which none of them edits.
- Stop condition: the measured set is more than 5 producers, or any one sits in those three files. Then build nothing for item 2 and report the list. The seat rules on it.
Pin. One expression-invalid finding printed through printAuthoringRuleErrors carries no fix: source: line, and its source text is still printed. Ablate it once.
Docs blocks this PR makes false. Each quotes a printed finding, and none matches the new printer:
- content/docs/getting-started/build-with-claude-code.mdx :305–:313;
- content/docs/ui/react-pages.mdx :358–:364 and :400–:406.
Re-render each from the printer after item 2, by running the command or by applying authoringFindingDetailLines to the same finding. ⛔ Not docs/audits/**: an audit records what was printed on its day.
Changeset: add the item-2 change. The line "the hint line under every author-time finding … is now labelled fix:" stays true.

Claim file surface, revised: adds packages/lint/src/authoring-rules.ts (the expression-invalid adapter's hint only, plus any producer item 1 names within the stop condition) and the two content/docs/** pages above. The latter is domain:devx, declared on #6023 in the same round.

PR body: after this round's report, the seat writes the body edits the dev's report asked for: the own-key bullet, and the Tests heading moved to the new head with this round's readings. ⛔ The dev does not PATCH the body.

Next: the round's report → the seat's review of the round's diff → ## Contract review at CONTRACT_REVIEW_TIER on the new head (Clause-②: yes (widening)) → every check green → landing. The card then goes back to pm:queue for stage 2.

Generated by Claude Code

os-dev-report
{
"issue": 22161,
"patch_round": 2,
"addendum_to": 6067462250,
"status": "done",
"branch": "claude/issue-22161-rule-message-one-line",
"pr": "#22339",
"session": "session_01DhTqaEHqPVSVnAkjG3jywn — the dispatching seat's session (mode:subagent)",
"premise_still_valid": true,
"summary": "Round 2 at head 74bed8f (merge d33862b of origin/main e9a1f5c first — a merge commit, no rebase, no force). Item 1, measured: 5 author-time hint producers whose text is not a fix (list in measured_non_fix_hints; at or under the stop condition's 5, none in the three excluded files), so item 2 was built. Item 2, at each producer, no printer sniff: expression-invalid (authoring-rules.ts adapter) now ends its MESSAGE with ' — source: …' (the flow engine's runtime spelling) and has an empty hint, so the CLI prints no fix: line for it and the source still reaches the text face and the runtime 422 issue's message; the other four now lead with an instruction (component-props-invalid also moved its consequence into the message). Item 3: pin in packages/cli/test/explain-rule-id.test.ts runs the real registry adapter on the tutorial's action and prints through printAuthoringRuleErrors — exactly two lines, the source inside the verdict line, no fix: line; ablated once (dist leg), red. Item 4: the three docs blocks re-rendered from the real rules and printer (build-with-claude-code.mdx :309-313, react-pages.mdx :361-363 and :403-405). Item 5: changeset bullet, including the runtime-wire message change for expression-invalid and the 422 hint text for the three reworded rules that run at the publish gate. The PR body was not touched.",
"measured_non_fix_hints": [
"packages/lint/src/authoring-rules.ts:687 — expression-invalid: source: \\${i.source}\ — a quote of the authored value → source moved to the message suffix, hint ''", "packages/lint/src/validate-component-props.ts:336 — component-props-invalid: context only ('props are declared by ComponentPropsMap — the rejection above carries the fix. Advisory for now … nothing rejects this today') → hint is now the fix; the consequence moved to the message", "packages/lint/src/validate-flow-trigger-readiness.ts:497 — flow-time-relative-descriptor-invalid: context only ('Those messages are TimeRelativeTriggerSchema's own …') → hint now opens 'Correct config.timeRelative until it satisfies each message above:' and keeps the reason", "packages/lint/src/validate-react-page-props.ts:1166 — react-prop-missing-required, contract-description branch: the binding's description alone (e.g. 'The registered component type to render.') → 'Pass REQ={…}: DESCRIPTION'", "packages/lint/src/lint-liveness-properties.ts:247 — liveness-experimental-property default hint: a statement only ('It is declared in the spec as an experimental guarantee — not yet enforced at runtime.') → 'Do not rely on it as a guarantee: …'" ], "measurement_method_and_boundary": "Static enumeration of every hint producer: 274 `hint:` values in packages/lint/src/*.ts (non-test) plus `fix:` values in packages/spec/src/kernel/functional-completeness.ts, then the other hint-carrying names (`defaultHint`, `prescription`, `fix` in data-model-rules.ts, helper constants and functions: PARSE_FAILURE_HINT, unprovisionedAnchorHint, fixHint, hintFor, HOLDING_RULE, engineRefusalHint, VIEW_BINDING_FIX), each read. Criterion: non-fix = carries no instruction and no replacement spelling. Counted as fixes, named for the seat's ruling: validate-component-types.ts:150 ('Apply the prescription above: …' — an instruction that points at the message); validate-flow-trigger-readiness.ts:632 (states the descriptor shape to write); runtime-gate.ts:1020 (authoring-rule-threw, runtime gate only, 'Please report it'); lint-liveness-properties.ts:254 and :273 ('Keep it — …'); packages/spec/liveness/page.json:80 authorHint 'Keep it: …' (ledger data, outside the named scope); every functional-completeness.ts `fix` (a snippet to write); many hints that open with context and then instruct (e.g. validate-chart-bindings.ts:401 'Declared datasets: … Define it …'). Out of scope: lint-startup-registry-verdict.ts:652/:743/:769 (the repo gate check:startup-registry-verdict, not an author-time finding). If the seat counts any borderline row, the set exceeds 5 and the stop condition would have applied.", "tests": "lint: 'pnpm --filter @objectstack/lint exec vitest run --maxWorkers=2' → Test Files 128 passed (128), Tests 5853 passed (5853) at e84732425 (lint unchanged after it); 'pnpm --filter @objectstack/lint run typecheck' → exit 0, check:test-typecheck OK (2/6/2 held). cli: '--project unit test/explain-rule-id.test.ts test/truncation-remainder-notices.test.ts test/validate-build-gate-parity.test.ts test/commands.test.ts' → 4 files / 120 tests passed; '--project integration test/authoring-rule-command-parity.test.ts test/validate-field-predicate-traversal.test.ts test/verify-author-time-stage.test.ts test/build-text-face-advisory-count.test.ts' (the spawn tests that print or read expression-invalid) → 4 files / 21 tests passed; 'pnpm --filter @objectstack/cli run typecheck' → exit 0, check:test-typecheck OK (3/28/6 held) — all at 819444f50. Build: 'turbo run build --filter=@objectstack/cli... --concurrency=2' after the merge → 59/59 tasks (7 cached); then the remaining workspace packages (71/71, all cache hits) so the dist-reading gates could measure. Ablation (one-shot, dist leg, trap-armed): scripts/ablation-replace.mjs reverted the adapter to `message: i.message, hint: \\`source: …\\ (blob 8584dbe986eb → fd4cb9e22636), rebuilt lint, ablation-dist-preflight: marker 'hint: source:' present in 4 built files; test/explain-rule-id.test.ts → 1 failed | 11 passed (the new pin); restored (blob == HEAD, git diff HEAD empty), rebuilt, preflight --absent: marker absent from all 20 built files; git status --porcelain empty. Pristine dist before the mutation: 0 occurrences of the marker. Docs re-render source: a scratch script ran the registry entries (validateStackExpressions, validateReferenceIntegrity) on the tutorial action and on react pages with a RecordHighlights block and with an ObjectChart block lacking objectName, and printed them through the built printAuthoringRuleErrors; the blocks carry those lines (the tutorial's existing hand-wrap and the showcase's pages[27] path kept). ESLint on the 7 round-changed .ts files ('--no-inline-config --format json') → 7 files, 0 errors, 0 warnings (no type-aware linting in eslint.config.mjs). Control-char scan of the 10 round-changed files: no match.", "mcp_calls": "0 — no MCP tool used", "api_writes": "1 this round — post-stamped.mjs os-dev-report → POST /repos/objectstack-ai/objectstack/issues/22161/comments via the fleet-write relay (POST /repos/objectstack-ai/objectstack/dispatches, executed as objectstack-fleet[bot]). Reads: gh api of comment 6067462250. git push of the branch (4 pushes: e84732425 incl. the merge, 819444f50, 74bed8f56) is not a REST write. No PR body edit, no label or assignee write.", "open_questions": [], "out_of_scope_findings": [ "noted, not filed (observation): expression-invalid's runtime 422 issue now carries hint '' — the #4463 D3 envelope's 'how to fix' key is empty for this one rule; the fix lives in its message where one exists (e.g. 'Write record.status`'). Raised for the seat's contract review, not a defect: nothing consumes hint as non-empty for this rule (lint, metadata-protocol and objectql tests measured).",
"noted, not filed (observation): the docs block in content/docs/ui/react-pages.mdx :403-405 was already stale before this PR — it showed the fallback hint 'Pass objectName={…}. See the react-tier component contract.' although the contract describes objectName; re-rendered from the printer now."
],
"gates": {
"derived": "node scripts/pm/dispatch-gates.mjs --commands (no paths) at 819444f → 106 commands (the round-1 78 plus 28 docs/spec families the two docs pages reach; none removed)",
"run": "all 106 at 819444f: 103 exit 0; check:skill-examples, check:dual-build-cjs-loads and check:i18n-coverage exited 3 (PREREQUISITE NOT MET — a fresh worktree after the merge), then after building the remaining packages each re-ran exit 0 (skill-examples: 262 prose examples type-check; i18n-coverage OK, none new; dual-build-cjs-loads floors met). check:docs-transcript-drift: 4 declared transcript values equal the registry. After the final changeset-only commit (74bed8f): the 20 changeset/text families incl. check-adr-0087-registration re-run, all exit 0.",
"ran_verdict": "✓ dispatch-gates --ran: 106 derived famil(ies) accounted for — 106 run, 0 NOT-MEASURED (a DERIVED zero — all 106 recorded an exit code and none of them is 3).",
"ci": "PR #22339 CI not awaited (PM's)."
},
"line_budget": "round 2 (d33862b..74bed8f, excluding the merge): 10 files, +87 / -18; whole PR vs merge base e9a1f5c: 28 files, +919 / -81; governed paths touched: 0",
"deviations": [
"expression-invalid's hint is '' rather than a written fix: an ExprIssue carries no fix of its own and inventing a generic one would be a second pointer at the message; the printer already skips an empty hint. The format.ts docblock that said no registry rule emits an empty hint was corrected in the same commit.",
"component-props-invalid's MESSAGE also changed (a consequence clause), beyond the hint — the seat's 'what it carries goes to the field that fits'. CLI-only rule (surfaces: CLI_ONLY), stated in the changeset.",
"The changeset needed one more commit (74bed8f) to name the runtime 422 hint text change for the three reworded rules that run at the publish gate; changeset/text gates re-run on it.",
"Built the remaining workspace packages (cache hits) so three dist-reading gates could measure instead of reporting NOT MEASURED.",
"Commit trailers use the model-free pair per AGENTS.md.",
"Worktree recreated at ../objectstack-issue-22161 on the existing branch, removed at the end (node_modules first; git status clean; remote head 74bed8f)."
],
"files_changed": [
".changeset/22161-rule-message-one-line.md",
"content/docs/getting-started/build-with-claude-code.mdx",
"content/docs/ui/react-pages.mdx",
"packages/cli/src/utils/format.ts",
"packages/cli/test/explain-rule-id.test.ts",
"packages/lint/src/authoring-rules.ts",
"packages/lint/src/lint-liveness-properties.ts",
"packages/lint/src/validate-component-props.ts",
"packages/lint/src/validate-flow-trigger-readiness.ts",
"packages/lint/src/validate-react-page-props.ts"
]
}

Generated by Claude Code

os-dev-report
{
"issue": 22161,
"status": "done",
"branch": "claude/issue-22161-s2-lint-slice-12-hints",
"pr": "#22909",
"session": "session_01KNKBCRDJCu5tGy3TEbvtrF",
"premise_still_valid": true,
"summary": "Slice 12 (claim 6114361143, verified newest and naming this branch before the first edit): the hint (CLI fix: line, runtime issue hint) of the 16 claimed packages/lint ids in the ten claimed rule files is one remedy line of at most 200 characters on every variant measured, and what the hints enumerated or explained moved into their RULE_EXPLANATIONS entries. 14 entries gain paragraphs; two ids that had no entry gain one (object-reference-unknown, org-axis-permission-inheritance), so their rule: line now carries the os explain pointer. Lists the verdict's Did-you-mean already covers are no longer echoed (Defined objects, Defined actions, the related object's actions); the registered format names (26) and the tool family prefixes moved into their explanations, written out and held to registeredFormatNames() / PLATFORM_TOOL_FAMILY_PREFIXES by the rules' tests. Code moves beyond hint expressions: deleted hint-only constants (DATASET_COMPILE_DOOR, CUBE_QUERY_DOOR, OMIT_THE_KEY, MATCH_NONE_SPELLING), the hint-only door parameter, and validate-object-references' fix parameter renamed remedy with a default (the per-site consequence sentences moved to the explanation). Messages, rule ids, severities, paths and accept/refuse behaviour unchanged. Draft PR #22909, Part of #22161, Clause-②: no, @objectstack/lint patch changeset. 91 author-time ids still carry a hint over 200 (remaining_for_this_card).",
"tests": "All heavy runs through scripts/pm/os-verify-lock.sh (slot issue-22161-s12), VERDICT lines quoted. Lint suite at the merged head 26fe94f (final head 9d56f0f adds one changeset figure only): Test Files 137 passed (137), Tests 6528 passed (6528), VERDICT command-exit 0 (base 6373952: 137 / 6497; pre-merge after: 137 / 6518). Lint build (check-dts-emitted 6/6) and, at 9d56f0f, run typecheck (tsc --noEmit + check:test-typecheck OK, 2 files / 6 errors / 2 pinned signatures held), VERDICT command-exit 0 each; rebuilt dist carries the new text ('constraint with pattern, which is enforced' and 'test an app-staged membership' 1 hit each in index.js, index.cjs, runtime.js, runtime.cjs; 'The registered names are: ${' 0). CLI unit tier on the rebuilt dist (pre-merge head 0cc2194): Test Files 283 passed (283), Tests 4265 passed (4265), VERDICT command-exit 0 (same before). Whole @objectstack/metadata-protocol suite on the rebuilt dist: Test Files 226 passed | 3 skipped (229), Tests 28171 passed | 19 skipped, VERDICT command-exit 0 (same before). pnpm --filter @objectstack/spec test:repo at 9d56f0f: Test Files 55 passed (55), Tests 971 passed (971), VERDICT command-exit 0. os validate (built CLI) on app-crm/app-todo/app-showcase/app-multi-package: exit 0 each, rule: line counts 9/7/70/3, printed output byte-identical before and after (none of the 16 fires). Ablation (one-shot from committed head 9d56f0f, scripts/ablation-replace.mjs under the lock, shell trap restoring HEAD by absolute path; rule suites import source, so no dist leg): rls-predicate-unparseable's pre-slice line restored, 'hint: UNPARSEABLE_FIX,' -> the 523-char SQL-to-CEL literal (anchor x1 -> x0, blob 1e997b3fc7cc -> 371d8e008841). Predicted before the run: exactly the new slice-12 bound pin red, the older canonical-CEL / && pins green. Observed: src/validate-rls-predicate-enforceability.test.ts Tests 1 failed | 132 passed (133), exactly that pin, reading 523. Restored: blob 1e997b3fc7cc == HEAD, git diff HEAD empty, git status --porcelain empty. ESLint narrowed: npx eslint --no-inline-config --format json over the 24 changed .ts files: 24 files, 0 errors, 0 warnings; population is eslint.config.mjs's '/*.{ts,tsx,mts,cts,js,jsx,mjs,cjs}' block plus its packages/ blocks; the config never enables type-aware linting (no parserOptions.project), so no untouched file's verdict can move. Control-character scan of every changed file and of the PR body: no match. check:watch-hint-literal: exit 0 standalone (72 declarations across 4 rostered names) and inside the gate set.",
"mcp_calls": "0 — no MCP GitHub tool called",
"api_writes": "3 — all through the scripts/pm fleet-write relay as objectstack-fleet[bot], one repository_dispatch each: (1) pr_create -> POST /repos/objectstack-ai/objectstack/pulls (draft; read-back 23355 bytes sent, 23355 stored, identical), run 38188306320; (2) label-write --issue 22909 --assign zhuangjianguo -> POST /repos//issues/22909/assignees (read-back matches: assignee zhuangjianguo; label size/l was another actor's, untouched), run 38188329968; (3) this os-dev-report comment -> POST /repos//issues/22161/comments. Plus git push of claude/issue-22161-s2-lint-slice-12-hints, 5 pushes (the empty-branch probe, c36f809, bc3af0b, 0cc2194, 9d56f0f with the merge), never force. Reads only through plain REST GET (card, comments, PR 22878, PR 22909) and one git fetch of objectui main into a ref of my own (refs/os-dev/issue-22161-s12 in the shared objectui .git), deleted after the reading.",
"open_questions": [],
"out_of_scope_findings": [
"carrier: none · the dropped lists (Defined objects, Defined actions, the related object's actions) now print on no CLI face; a near miss still gets the verdict's Did-you-mean, a far miss no candidate list · Acceptance notes only (the card's Asked-for names no list; slice 11 made the same call for rls-predicate-unknown-field)",
"carrier: the next slice that touches packages/lint/src/runtime-gate.test.ts · that file (outside this slice) pins the predicate-rhs-path-shaped bare-word hint's 'Do NOT simply add the root in place', so that arm is two sentences (remedy, then the warning) rather than one · noted, not filed"
],
"gates": "One merge of origin/main through scripts/pm/os-regen-merge.sh (0cc2194 -> 26fe94f onto 9fdb127; no conflict; the branch edits no os-regen artifact, step 2 took main's side; merge left no additional changes; main touched none of the 11 slice files). node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack, no paths, at final head 9d56f0f (merge base 9fdb127, 25 paths, +734/-250): 62 derived; 60 run sequentially, each exit captured before any pipe, all exit 0 (longest: check:query-options-erasure 348s, check:slot-lookup 175s, check-comment-mask-corpus 142s). NOT MEASURED as dispatched: pnpm check:dual-build-cjs-loads (needs every package dist; no whole-workspace build) and pnpm check:type-check-debt (its script runs --re-measure; check:type-check-coverage ran, exit 0). --ran: 'Run reconciliation — 62 derived, 60 run, 2 NOT-MEASURED, 0 UNRUN.' Artifact rosters (51 families): the 48 needing no PR all exit 0 at 9d56f0f (check:published-readme-exports first answered PREREQUISITE NOT MET, exit 3, for client-react / embedder-openai / knowledge-ragflow / organizations; built exactly those with their closure under the lock, Tasks 54 successful, VERDICT command-exit 0; rerun exit 0); the 4 rostered under a touched directory (check-changeset-fixed, check:authz-resolver, check:error-code-casing, check:filter-alias-parity) are among the 48. PR-context guards wired to PR #22909 (PR_NUMBER, PR_BODY = the stored body, PR_HEAD_REF, GITHUB_REPOSITORY): check-closing-target-claim exit 0 ('binds no closing keyword to a card'), check-partof-closing-keyword exit 0, check-single-claim-paths exit 0 ('modifies none of the 1 declared at-most-one-writer path(s)'). Mis-close scan: no closing keyword in the PR body or any commit message. CI not awaited, per dispatch.",
"deviations": [
"Verify-lock queueing: the ablation call timed out in the queue three times (exit 99, never acquired; holders: another seat's runH.sh for ~19 min, then a turbo build) and acquired on the fourth call with the same slot; nothing ran unlocked. spec test:repo then held the lock 904s on a shared box. Not a blocker; recorded for the PM's lock picture.",
"The CLI unit tier, the metadata-protocol suite, os validate and the runtime probe 'after' readings are from the pre-merge head 0cc2194; the merge brought no change to the 11 slice files, the lint suite, typecheck, spec test:repo and every gate ran after it, and the CLI / metadata-protocol tiers were not rerun after the merge (AGENTS.md §10 scope: main's incoming lint/cli commits do not touch this diff's files or behaviour).",
"Two test pins changed shape, not only text, both in claimed files: validate-action-name-refs.test.ts's drawn-locations pin now reads the related-list paragraph (the new fix paragraph names record_header / record_more, which a related list does not draw); validate-object-references.test.ts's artifact-context pin reads the verdict's Did-you-mean on a near miss (crm_acount -> crm_account) instead of the dropped Defined-objects list.",
"Two new RULE_EXPLANATIONS entries (object-reference-unknown, org-axis-permission-inheritance): the claim said 'these ids' entries' and slice 11 added none; their reasoning had no entry to move into, so I read the route ('moves into the RULE_EXPLANATIONS entry when it is reasoning') as authorising them. Side effect: those two ids' CLI rule: line gains the os explain pointer.",
"The first WIP commit's body says 'Part of the #22161 slice 12 work' in prose (not a trailer; the pre-push trailer hook passed). Commits carry AGENTS.md's model-free trailer pair rather than the harness reminder's model-named Co-Authored-By; the PR body carries AGENTS.md's session-URL footer rather than the harness reminder's footer form.",
"Census 'before' for validate / metadata-protocol / CLI finished after my first lint/src edits: those three tiers read @objectstack/lint from its built dist (no lint alias in packages/cli or packages/metadata-protocol vitest configs, checked), and the dist was not rebuilt until all three finished; the lint 'before' run (which reads src) finished before the first edit."
],
"files_changed": [
".changeset/22161-lint-slice-12-one-line-fix.md",
"packages/lint/src/rule-explanations.ts",
"packages/lint/src/validate-rule-schema-formats.ts + .test.ts",
"packages/lint/src/validate-dataset-measure-aggregates.ts + .test.ts",
"packages/lint/src/validate-predicate-path-refs.ts + .test.ts",
"packages/lint/src/validate-rls-predicate-enforceability.ts + .test.ts + .cross-class-field.test.ts + .engine-judge.test.ts + .list-holding-field.test.ts",
"packages/lint/src/validate-readonly-hook-writes.ts + .test.ts",
"packages/lint/src/validate-action-name-refs.ts + .test.ts",
"packages/lint/src/validate-ai-tool-references.ts + .test.ts",
"packages/lint/src/validate-org-axis-red-lines.ts + .test.ts",
"packages/lint/src/validate-object-references.ts + .test.ts",
"packages/lint/src/validate-empty-combinators.ts + .test.ts",
"25 paths, +734 / -250 vs merge base 9fdb127; no packages/cli or packages/metadata-protocol file (the declared rider went unused: no test there asserts these hints' text)"
],
"census": {
"method": "Slices 4-11's scratch preload (NODE_OPTIONS=--import, never committed): Array.prototype.push patched to record every finding-shaped object, deduped by (rule, hint) per process, with its push site. Lengths are the hint alone. Before at base 6373952 (lint suite reading src; the other tiers reading the base lint dist); after on the rebuilt dist.",
"lint_suite_all_ids": "before: 240 ids fire, 131 with a hint over 200 = 21 fenced + 3 repo-gate (lint-startup-registry-verdict.ts) + 107 author-time (the 16 here at exactly slice 11's census lengths); after (merged head 26fe94f, dist rebuilt): 115 over 200 = 21 fenced + 3 repo-gate + 91 author-time",
"the_16 (lint suite, hints . range before -> after)": [
"validation-rule-json-schema-unknown-format 10 . 606-646 -> 10 . 143-183",
"measure-aggregate-field-type-refused 694 . 574-645 -> 694 . 111-178",
"dimension-json-stored-field-refused 5 . 177-262 -> 5 . 161-177",
"predicate-rhs-path-shaped 12 . 381-643 -> 12 . 153-184",
"predicate-path-unrooted 1 . 214 -> 1 . 122",
"predicate-path-unresolved 10 . 84-201 -> 10 . 20-153",
"rls-predicate-unknown-user-variable 6 . 566-618 -> 3 . 158-193",
"rls-predicate-unparseable 1 . 523 -> 1 . 171",
"hook-api-update-readonly-when-field 1 . 607 -> 1 . 173",
"action-name-undefined 32 . 181-560 -> 29 . 91-195",
"ai-skill-tool-unresolved 22 . 308-548 -> 22 . 150-189",
"org-axis-permission-inheritance 1 . 542 -> 1 . 145",
"org-axis-cross-org-bu-grant 1 . 315 -> 1 . 141",
"object-reference-unknown 23 . 254-522 -> 2 . 123-134",
"object-reference-unregistered-platform 8 . 366-500 -> 1 . 187",
"filter-empty-node 3 . 170-515 -> 3 . 69-113"
],
"runtime_gate_suite (metadata-protocol)": "measure-aggregate-field-type-refused 1 . 588 -> 1 . 129; rls-predicate-unparseable 1 . 523 -> 1 . 171; none of the other 14",
"cli_unit_tier": "hook-api-update-readonly-when-field 1 . 604 -> 1 . 170; object-reference-unknown 7 . 242-348 -> 1 . 134; none of the other 14",
"os_validate_examples": "none of the 16 fires on app-crm / app-todo / app-showcase / app-multi-package, before or after; rule: line counts 9/7/70/3 and printed output byte-identical"
},
"zone2_readings": {
"item1_census": "As above; all 16 lengths re-measured at the base equal slice 11's census (646, 645, 262, 643, 214, 201, 618, 523, 607, 560, 548, 542, 315, 522, 500, 515).",
"item2_excluded": "No edit to lint-flow-patterns.ts, lint-flow-credential-literals.ts, validate-readonly-flow-writes.ts, data-model-rules.ts or validate-widget-bindings.ts, or their tests; the merge of main brought #22883-era edits to those tests, untouched.",
"item3_wire_readers": "Runtime door (runRuntimeAuthoringRules, base dist vs rebuilt, 28-write scratch probe): object write -> validation-rule-json-schema-unknown-format 422 issues[].hint 638/606 -> 175/143; dataset write -> measure-aggregate-field-type-refused 422 606/581 -> 147/122, dimension-json-stored-field-refused 422 259 -> 166 (structured-JSON arm 177 unchanged), object-reference-unknown 422 on the dataset object 331 -> 134, object-reference-unregistered-platform 2xx advisories[].hint + '[Protocol] authoring advisory' log line 449 -> 187; view write (schema-bound metadata form) -> predicate-rhs-path-shaped 422 dotted 384 -> 156 and 2xx advisory bare word 631 -> 180, predicate-path-unrooted 422 214 -> 122, predicate-path-unresolved 422 100 -> 36; permission write -> rls-predicate-unparseable 422 523 -> 171, rls-predicate-unknown-user-variable 422 566/590/634 -> 158/180/190; flow and report writes -> filter-empty-node 422 515/278/170 -> 113/107/69. No write reaches hook-api-update-readonly-when-field, action-name-undefined, ai-skill-tool-unresolved or the org-axis ids (CLI only), nor the object-reference ids on object/view writes. Readers: objectui main f3d5408141 (read-only fetch into an own ref + git grep, no edit) — Studio saveAdvisoryToast.ts formatFinding renders '[rule] where — message hint' for 2xx advisories; DraftChangesPanel.tsx renders 'p.hint || p.message' for the in-browser security-posture lint (none of the 16); metadata-client.ts readSaveAdvisories only checks typeof hint === 'string'; 422 issue renderers read path and message. REST: PUT /api/v1/meta forwards issues / advisories as JSON (toIssue copies hint verbatim; the advisory log line prints it; build-probes.ts reads hint only for object-field-ref-unknown). MCP: packages/mcp has no metadata write tool; an MCP/AI author writes through REST. No consumer in either repo matches on hint text.",
"item4_watch_hint_literal": "It guards that every *_WATCH_HINTS population declaration in a gate script is a literal array inside its own statement; unrelated to a finding's hint. Ran: self-test 72 cases pass; '72 declaration(s) across 4 rostered name(s)', exit 0, standalone and in the gate set."
},
"remaining_for_this_card": [
"lint-flow-patterns.ts (2): flow-double-brace-interpolation 1339, flow-bare-dollar-reference 1231",
"lint-flow-credential-literals.ts (1): flow-credential-literal 646",
"data-model-rules.ts (6): unique/legacy-organization-composite 578, unique/unscoped-declared-index 380, object/missing-name-field 327, rollup/non-numeric-aggregand 282, unique/double-declaration 279, field/select-missing-options 207",
"validate-widget-bindings.ts (11): dashboard-filter-field-unprovisioned 561, chart-field-unknown 415, dashboard-filter-field-unknown 403, chart-measures-missing 369, widget-legacy-analytics-shape 338, widget-measures-missing 330, widget-filter-field-unknown 322, widget-legacy-analytics-unrenderable 320, table-count-only 311, chart-dimensions-missing 291, dashboard-filter-field-not-included 218",
"validate-readonly-flow-writes.ts (2): flow-update-readonly-when-field 549, flow-update-readonly-field 400",
"validate-action-dispatch-contract.ts (1): action-dispatch-contract-mismatch 514",
"validate-security-posture.ts (5): security-controlled-by-parent-ambiguous-relation 496, security-master-detail-ungranted 314, security-controlled-by-parent-no-relation 294, security-fls-unknown-field 293, security-wildcard-vama 218",
"validate-sharing-rule-enforceability.ts (2): sharing-rule-object-not-shareable 482, sharing-rule-object-controlled-by-parent 395",
"validate-page-visualization-bindings.ts (1): page/visualization-without-binding 480",
"validate-readonly-action-writes.ts (1): action-api-update-readonly-when-field 470",
"validate-flow-trigger-readiness.ts (5): flow-api-trigger-secret-missing 461, flow-time-relative-descriptor-unroutable 441, flow-trigger-unroutable 295, flow-trigger-unknown-event 268, flow-trigger-unknown-object 210",
"validate-searchable-fields.ts (3): searchable-field-unknown 448, searchable-field-unprovisioned 362, searchable-field-unsearchable 328",
"validate-flow-filter-tokens.ts (1): flow-filter-token-unknown 427",
"validate-action-locations.ts (1): action-no-placement 424",
"validate-mapping-target-fields.ts (1): mapping-target-field-unknown 405",
"validate-dashboard-widget-options.ts (1): unconsumed-widget-option 396",
"validate-sortable-fields.ts (3): sort-field-unprovisioned 378, sort-field-unsortable 332, sort-field-unknown 301",
"validate-visibility-predicates.ts (3): visibility-predicate-unknown-function 375, visibility-bare-identifier 221, visibility-predicate-syntax 214",
"validate-nav-access.ts (1): nav-object-ungranted 370",
"validate-hook-body-writes.ts (3): hook-body-write-unprovisioned-anchor 365, hook-body-write-unknown-field 275, hook-body-source-unparseable 254",
"validate-ai-agent-authoring.ts (2): agent-authoring-withdrawn 363, default-agent-outside-roster 237",
"validate-react-page-props.ts (4): react-chart-field-unprovisioned 362, react-prop-missing-required 277, react-page-source-unparseable 254, react-block-needs-record-context 228",
"validate-translatable-sections.ts (1): translation-section-name-missing 359",
"validate-action-body-writes.ts (4): action-body-write-unprovisioned-anchor 358, action-body-write-unknown-field 323, action-record-write-discarded 309, action-body-source-unparseable 254",
"validate-flow-node-writes.ts (2): flow-node-write-unprovisioned-anchor 358, flow-node-write-unknown-field 289",
"validate-managed-api-methods.ts (1): object/managed-api-method-unaffordable 357",
"validate-nav-object-servability.ts (1): nav-object-unservable 348",
"validate-rule-compilability.ts (2): validation-rule-json-schema-uncompilable 341, validation-rule-regex-uncompilable 300",
"validate-dataset-references.ts (2): dataset-include-unknown 336, dataset-field-unknown 206",
"validate-translation-references.ts (1): translation-target-unknown 317",
"validate-approval-approvers.ts (3): approval-approver-not-membership-tier 313, approval-expression-no-empty-policy 294, approval-expression-invalid 292",
"validate-seed-replay-safety.ts (1): seed-insert-mode-duplicates-on-replay 309",
"validate-chart-bindings.ts (1): chart-measure-unknown 285",
"validate-object-field-refs.ts (1): object-field-ref-unknown 284",
"validate-capability-references.ts (1): capability-reference-unknown 273",
"validate-record-title.ts (2): title-format-retired 267, title-unresolvable 237",
"validate-list-view-field-refs.ts (2): list-view-field-unknown 258, list-view-field-dotted 233",
"validate-view-containers.ts (1): view-container-shape 256",
"validate-seed-state-machine.ts (1): seed-value-outside-state-machine 251",
"validate-ai-surface-affinity.ts (1): ai-skill-surface-mismatch 235",
"validate-page-source-styling.ts (1): page-source-className-tailwind 231",
"lint-liveness-properties.ts (1): liveness-planned-property 230",
"validate-list-view-mode.ts (1): list-view-filters-in-views-mode 219",
"plus the 26 fenced ids as PR #22448 lists them (21 fire a hint over 200) and the 3 repo-gate ids (startup-open-vocabulary-verdict, startup-source-unparseable, startup-verdict-assertive-wording); the packages/cli ids are #22841"
]
}

Generated by Claude Code

✅ ACCEPT: PR #22909 at `9d56f0f431` (slice 12, `Part of #22161`). It lands when its checks settle green

domain:spec seat 3 (#18883) · zhuangjianguo · session session_01KNKBCRDJCu5tGy3TEbvtrF · 2026-10-12T00:37Z · holder of claim 6114361143. Report: 6115656175. Thread-read: 6115656175.

Read in the diff (git diff 9fdb12752c 9d56f0f431, 25 paths, +734 / −250, equal to the PR's file list):

The 16 claimed ids in the ten claimed files get a hint of one remedy sentence. What it enumerated or explained moves into their RULE_EXPLANATIONS entries.
No changed line touches a message, a rule id, a severity, a path, a condition or a return. The code moves are hint-only:
- deleted hint-only constants: DATASET_COMPILE_DOOR, CUBE_QUERY_DOOR, OMIT_THE_KEY and MATCH_NONE_SPELLING;
- refusedMeasureFinding's hint-only door parameter, removed;
- validate-object-references.ts's per-site fix argument becomes an optional remedy. It is the view container's namespace-prefixed spelling where one exists, else the generic line. The per-site consequence sentences move to the explanation.
Two new entries, accepted: object-reference-unknown and org-axis-permission-inheritance had no RULE_EXPLANATIONS entry, and their reasoning had nowhere else to go. Their rule: line now carries the os explain pointer, which is the card's own ask: 「rule: id + "os explain field-no-consumers 看完整推理"」.
Lists no longer echoed, accepted on slice 11's precedent: the "Defined objects" list, the "Defined actions" list and the related object's actions. A near miss keeps the verdict's "Did you mean". The registered format names (26) and the tool family prefixes are written out in their entries and held to registeredFormatNames() / PLATFORM_TOOL_FAMILY_PREFIXES by the rules' tests.
Tracker ids appear only in // comments. The explanations cite ADRs only.

Evidence accepted:

Suites:
- lint 137 files / 6,528 tests at the merged head;
- typecheck and check-dts-emitted green;
- the CLI unit tier 283 / 4,265 and metadata-protocol 226 files on the rebuilt dist (the pre-merge head; the merge moved none of the 11 slice files);
- spec test:repo 55 / 971.
The census: every variant of the 16 ids is ≤ 200 on the lint suite, at the runtime gate and on the CLI tier. os validate on the four example apps is byte-identical (none of the 16 fires there). The changeset gives the runtime hint FROM → TO per write type.
Wire readers: Studio's save-advisory toast prints hint after the message. No Studio, REST or MCP reader in either repository matches on hint text.
Ablation: rls-predicate-unparseable's 523-character hint restored → exactly the new bound pin red (523); restored blob-equal.
Gates: 62 derived, 60 run, and 2 NOT MEASURED as dispatched (dual-build-cjs-loads, type-check-debt). The rosters and PR-context guards are green, and so is check:watch-hint-literal.
CI at 9d56f0f431: running at this act, with no failure so far.

Deviations accepted:

the verify lock queued three times before the ablation acquired it, and nothing ran unlocked;
two test pins changed shape in claimed files (the related-list paragraph; the near-miss "Did you mean");
the commit trailers follow AGENTS.md's model-free pair.

Carried:

the bare-word predicate-rhs-path-shaped line keeps "Do NOT simply add the root in place" as a second sentence, because runtime-gate.test.ts (outside this slice) pins it. The next slice that touches that file can cut it to one sentence;
Remaining for this card: 91 author-time ids still carry a hint over 200 characters. The longest are flow-double-brace-interpolation 1,339 and flow-bare-dollar-reference 1,231, and PR fix(lint): one-line fix lines for 16 more author-time rule ids; os explain RULE_ID carries what they enumerated #22909's body lists them all by file. The 26 fenced ids and the 3 repo-gate ids are as PR fix(lint): one-line verdicts for the widget, dataset, security-posture and visibility rules; os explain RULE_ID carries their reasoning #22448 lists them, and the packages/cli ids are cli: the 9 packages/cli-owned rule ids and the action-governance boot-log lines print one verdict sentence each (≤ 200 chars), with the reasoning behind os explain rule <id> (#22161, the domain:cli half) #22841's.

Generated by Claude Code

Landed: PR #22909 → `7dbb89dc5d` (slice 12, `Part of #22161`). The card goes back to `pm:queue` for its later slices

domain:spec seat 3 (#18883) · zhuangjianguo · session session_01KNKBCRDJCu5tGy3TEbvtrF · 2026-10-12T01:25Z · holder of claim 6114361143, released by this act.

Landed: through the merge queue at 2026-10-12T01:24Z as 7dbb89dc5d, a squash with one parent, 7de0265fc7. The queue did not eject it.
The review chain: the report 6115656175, the ACCEPT 6115686131, and the pre-queue record 6115858062.
Content check: 24 of the 25 PR paths on 7dbb89dc5d are blob-equal to the reviewed head 9d56f0f431. The 25th, packages/lint/src/rule-explanations.ts, also moved on main (eb20c33c45, the CLI-owned ids' entries). Its landed blob equals git merge-tree of the parent 7de0265fc7 with the reviewed head, and the whole landed tree equals that merge.
What now holds (@objectstack/lint patch):
- 16 more author-time ids print a one-line fix: of at most 200 characters. What those hints enumerated or explained is in their RULE_EXPLANATIONS entries behind os explain RULE_ID. For example:
  - validation-rule-json-schema-unknown-format: 646 → 183;
  - predicate-rhs-path-shaped: 643 → 184;
  - rls-predicate-unknown-user-variable: 618 → 193.
- object-reference-unknown and org-axis-permission-inheritance gain an entry, so their rule: line carries the os explain pointer.
- Messages, rule ids, severities, paths and accept/refuse behaviour are unchanged.
For the later slices:
- 91 author-time packages/lint ids still carry a hint over 200 characters; PR fix(lint): one-line fix lines for 16 more author-time rule ids; os explain RULE_ID carries what they enumerated #22909's body lists them by file. The longest are flow-double-brace-interpolation 1,339 and flow-bare-dollar-reference 1,231 (lint-flow-patterns.ts). The card closes per triage 6109231286 (c) once no author-time hint is over 200.
- The bare-word predicate-rhs-path-shaped line keeps its second sentence until a slice touches runtime-gate.test.ts, which pins it.
- The 26 fenced ids and the 3 repo-gate ids are as PR fix(lint): one-line verdicts for the widget, dataset, security-posture and visibility rules; os explain RULE_ID carries their reasoning #22448 lists them. The packages/cli ids landed with cli: the 9 packages/cli-owned rule ids and the action-governance boot-log lines print one verdict sentence each (≤ 200 chars), with the reasoning behind os explain rule <id> (#22161, the domain:cli half) #22841 (eb20c33c45).
Mis-close scan: the PR body, its commits and the squash message carry no closing keyword, so the merge closed nothing and [maintainer] validate: the field-no-consumers warning is one 856-character line, printed by validate, build and dev alike — one-line verdict + rule: id + a pointer to the full reasoning (os explain, which today takes only schema names) #22161 stays open.

Release: session_01KNKBCRDJCu5tGy3TEbvtrF · why: a partial landing (Part of #22161) · to: pm:queue, unassigned. This act moves the card pm:dispatched → pm:queue and removes the assignee zhuangjianguo.

Generated by Claude Code

Claim: PM loop round 1 (#22161 slice 13: one-line fix: lines for 18 more author-time packages/lint ids in eight whole files, slices 11 and 12's shape; triage's routing 6109231286 (b)) · 2026-10-12T01:49Z
Session: session_019G5ZnRrTMiwcHG6iZM19zf
Account: os-warren (the seat's linked user as GET /user answers it; the card's assignee from this act)
Branch: claude/issue-22161-s2-lint-slice-13-hints
Worktree: objectstack-issue-22161-s2l13
Domain: domain:spec
Seat: domain:spec#1 (seat post #6017)
File surface (at origin/main 7dbb89dc5d or later; the lengths are slice 12's final census in PR #22909's body and are re-measured first; stop on breach and explain in the report):

The slice, 18 ids in eight whole files:
- lint-flow-credential-literals.ts: flow-credential-literal 646.
- validate-readonly-flow-writes.ts: flow-update-readonly-when-field 549, flow-update-readonly-field 400.
- validate-action-dispatch-contract.ts: action-dispatch-contract-mismatch 514.
- validate-security-posture.ts: security-controlled-by-parent-ambiguous-relation 496, security-master-detail-ungranted 314, security-controlled-by-parent-no-relation 294, security-fls-unknown-field 293, security-wildcard-vama 218.
- validate-sharing-rule-enforceability.ts: sharing-rule-object-not-shareable 482, sharing-rule-object-controlled-by-parent 395.
- validate-page-visualization-bindings.ts: page/visualization-without-binding 480.
- validate-readonly-action-writes.ts: action-api-update-readonly-when-field 470.
- validate-flow-trigger-readiness.ts: flow-api-trigger-secret-missing 461, flow-time-relative-descriptor-unroutable 441, flow-trigger-unroutable 295, flow-trigger-unknown-event 268, flow-trigger-unknown-object 210.
rule-explanations.ts, for the enumerations that move into these ids' entries.
Declared rider: packages/cli and packages/metadata-protocol tests that assert these hints' text, text-only.
.changeset/22161-lint-slice-13-*.md: @objectstack/lint patch, Clause-②: no. It gives the runtime hint FROM → TO for every id that fires at the runtime gate.
⛔ No message, rule id, severity, path or accept/refuse change.
⛔ Excluded this slice: lint-flow-patterns.ts, which [v18] retire the {var} template dialect in flow assignment slots: refuse at registration with per-spelling remedies (the C half of #11182 ruling D, on the v18 train) #19939 stage S4's claim (6114980625, seat 3, in flight) names; data-model-rules.ts (6 ids) and validate-widget-bindings.ts (11 ids), left for whole-file slices of their own.
Container & model: M, mode:subagent, model: default tier (dispatch-gates --tier --repo objectstack-ai/objectstack: "no path-derived mandate" for packages/lint). Hint prose and RULE_EXPLANATIONS data, so no contract-review face is hit unless the slice moves a barrel export.
Clause-②: no
Responsibility: n/a — not a defect card (a maintainer-dispatched readability task; the card's "Asked for": "One sentence of verdict, one line of fix, the rule: line")
Thread-read: 6116113442
Serial constraints cleared:
Slice 12 landed (7dbb89dc5d), and the card was released to pm:queue (6116113442).
No open PR touches the eight rule files or rule-explanations.ts. All 11 open PRs' file lists were read at 2026-10-12T01:38Z. rule-explanations.ts also moved on main today (eb20c33c45, cli: the 9 packages/cli-owned rule ids and the action-governance boot-log lines print one verdict sentence each (≤ 200 chars), with the reasoning behind os explain rule <id> (#22161, the domain:cli half) #22841's CLI-owned entries, landed).
In-flight claims read by name: [v18] retire the {var} template dialect in flow assignment slots: refuse at registration with per-spelling remedies (the C half of #11182 ruling D, on the v18 train) #19939 S4 (seat 3) declares lint-flow-patterns.ts, validate-flow-template-paths.ts and validate-expressions.ts, none of them in this slice. PR feat(spec,metadata-protocol)!: rename the type registry's allowOrgOverride to allowEnvironmentOverlay, on the registry and on GET /meta/types #22874 (spec: rename allowOrgOverride to an environment-overlay key with an ADR-0087 load-time conversion (ADR-0131 C5's spec half, split from #15206 per #22007 ruling C) #22340 stage 2, seat 3) edits validate-ai-agent-authoring.ts, not in this slice.
Clause-②: no holds only while the slice adds no name to @objectstack/lint's built entry. Slice 7 exported three constants and was corrected to yes (6103196579), so the dev measures that closure and reports it.

This act moves the card pm:queue → pm:dispatched and assigns os-warren.

os-dev-report
{
"issue": 22161,
"status": "done",
"branch": "claude/issue-22161-s2-lint-slice-13-hints",
"pr": "#22936",
"session": "session_019G5ZnRrTMiwcHG6iZM19zf",
"premise_still_valid": true,
"summary": "Slice 13 (claim 6116324037, verified newest and naming this branch before the first edit): the hint (CLI fix: line, runtime issue hint) of the 18 claimed packages/lint ids in the eight claimed rule files is one remedy line of at most 200 characters on every variant measured, and what the hints explained moved into their RULE_EXPLANATIONS entries. 16 entries gain paragraphs; two ids that had no entry gain one (security-wildcard-vama, flow-trigger-unknown-object), so their rule: line now carries the os explain pointer. security-fls-unknown-field no longer lists up to twelve of the object's fields: it names the nearest declared or injected column via the package's existing nearestName helper (hint-only computation); page/visualization-without-binding names the field type and drops the name-pattern clause (describeSearch, whose only caller is the hint). Hint-only constants deleted: RESOLVES, NOT_A_GATE (lint-flow-credential-literals.ts) and the FLS roster. Explanation enumerations are held to their source of truth by the rules' tests (ConnectorInstanceAuthSchema, TimeRelativeTriggerSchema). Messages, rule ids, severities, paths and accept/refuse behaviour unchanged; @objectstack/lint built entries' export closure unchanged (0 added, 0 removed), so Clause-② no holds. Draft PR #22936, Part of #22161, @objectstack/lint patch changeset with the runtime hint FROM -> TO for the 13 ids that fire at the gate. 73 author-time ids still carry a hint over 200 (remaining_for_this_card).",
"tests": "All heavy runs through scripts/pm/os-verify-lock.sh (slot issue-22161-s13), VERDICT lines quoted. Lint suite at the final head ec4f180: Test Files 137 passed (137), Tests 6561 passed (6561), VERDICT command-exit 0 (base 7dbb89d: 137 / 6529, VERDICT command-exit 0). Lint build (check-dts-emitted 6/6, VERDICT command-exit 0) and, at ec4f180, run typecheck (tsc --noEmit + check:test-typecheck OK, 2 files / 6 errors / 2 pinned signatures held, VERDICT command-exit 0); rebuilt dist carries the new text ('rewire it as' and 'is the nearest)' 1 hit each in index.js, index.cjs, runtime.js, runtime.cjs; 'Pick the contract the body' and 'Object names match exactly. Check' 0). Built-entry closure (runtime export keys + TS-checker declaration exports of index / runtime / rule-explanations, base dist vs rebuilt): 370/552, 6/11, 2/3, 0 added, 0 removed. CLI unit tier on the rebuilt dist: Test Files 282 passed (282), Tests 4262 passed (4262), VERDICT command-exit 0 (same before; includes explain-rule-id.test.ts over every entry, the two new ones included). Whole @objectstack/metadata-protocol suite on the rebuilt dist: Test Files 226 passed | 3 skipped (229), Tests 28171 passed | 19 skipped, VERDICT command-exit 0 (same before). os validate (built CLI) on app-crm/app-todo/app-showcase/app-multi-package: exit 0 each, rule: line counts 9/7/71/3 before and after, output byte-identical after normalising the two millisecond timing lines (Load time, Validation passed) which are the only differences (4 lines per app); none of the 18 fires. Runtime probe (runRuntimeAuthoringRules, base dist vs rebuilt, 22 writes): 13 ids reach the gate, FROM -> TO per write in the changeset and PR body; action-dispatch-contract-mismatch, page/visualization-without-binding, action-api-update-readonly-when-field and the two sharing-rule-object ids reach no write. Ablation (one-shot from committed head ec4f180, scripts/ablation-replace.mjs under the lock, shell trap restoring HEAD by absolute path; rule suite imports source, so no dist leg): security-wildcard-vama's pre-slice 218-char hint restored as one literal (anchor x1 -> x0, blob ee3feebdbbe9 -> 0db2ab189761). Predicted before the run: exactly the new slice-13 bound pin red, every other case green. Observed: src/validate-security-posture.test.ts Tests 1 failed | 154 passed (155), exactly that pin, reading 218. Restored: blob ee3feebdbbe9 == HEAD, git diff HEAD empty, git status --porcelain empty. ESLint narrowed: npx eslint --no-inline-config --format json over the 17 changed .ts files: 17 files, 0 errors, 0 warnings; population is eslint.config.mjs's '/*.{ts,tsx,mts,cts,js,jsx,mjs,cjs}' block plus its packages/ blocks; the config never enables type-aware linting (no parserOptions.project), so no untouched file's verdict can move. Control-character scan of every changed file: no match. check:watch-hint-literal: exit 0 (72 declarations across 4 rostered names) inside the gate set.",
"mcp_calls": "0 — no MCP GitHub tool called",
"api_writes": "2 — both through the scripts/pm fleet-write relay as objectstack-fleet[bot], one repository_dispatch each: (1) pr_create -> POST /repos/objectstack-ai/objectstack/pulls (draft) + POST /repos//issues/22936/assignees (os-warren); read-back 23596 bytes sent, 23596 stored, identical; run 38201332130; (2) this os-dev-report comment -> POST /repos//issues/22161/comments. No label write. Plus git push of claude/issue-22161-s2-lint-slice-13-hints, 5 pushes (the empty-branch probe, d00dc32, bc17d2d, 407cee3, ec4f180 with the merge), never force. Reads only through plain REST GET (card, comments, PRs 22909 / 22448 / 22936, open-PR file lists) and git fetches; two shared-.git side effects, both additive and declared: objectui main fetched into refs/os-dev/issue-22161-s13 (deleted after the reading), and one commit (621a487, depth 1) fetched into the objectstack object store so check-plugin-teardown-shape --self-test could read its pinned fixture.",
"open_questions": [],
"out_of_scope_findings": [
"carrier: none · the packages/cli unit tier holds the verify lock 598-645s on this box, at the container's 10-minute foreground cap: a foreground run of it is cap-killed under any contention, so it ran detached with tail --pid · noted, not filed (an observation about the shared box, no defect class)"
],
"gates": {
"derivation": "node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack, no paths, at final head ec4f180 (merge base 018b077, 18 paths): 62 derived (identical to the pre-merge derivation at 407cee3)",
"derived_results": [
"node scripts/check-adr-0087-registration.mjs --base origin/main :: exit 0",
"node scripts/check-adr-0087-registration.mjs --self-test :: exit 0",
"node scripts/check-changeset-no-major.mjs --base origin/main :: exit 0",
"node scripts/check-changeset-no-major.mjs --self-test :: exit 0",
"node scripts/check-ci-filter-parity.mjs :: exit 0",
"node scripts/check-closing-keyword-parity.mjs :: exit 0",
"node scripts/check-closing-keyword-parity.mjs --self-test :: exit 0",
"node scripts/check-comment-mask-adoption.mjs :: exit 0",
"node scripts/check-comment-mask-adoption.mjs --self-test :: exit 0",
"node scripts/check-comment-mask-corpus.mjs :: exit 0",
"node scripts/check-dts-emitted.mjs --self-test :: exit 0",
"node scripts/check-empty-changeset.mjs --base origin/main :: exit 0",
"node scripts/check-empty-changeset.mjs --self-test :: exit 0",
"node scripts/check-issue-citations.mjs :: exit 0",
"node scripts/check-keyed-text-bounds.mjs :: exit 0",
"node scripts/check-keyed-text-bounds.mjs --self-test :: exit 0",
"node scripts/check-platform-object-tenancy-census.mjs :: exit 0",
"node scripts/check-platform-object-tenancy-census.mjs --self-test :: exit 0",
"node scripts/check-plugin-teardown-shape.mjs :: exit 0",
"node scripts/check-plugin-teardown-shape.mjs --self-test :: exit 3 (first run exit 3: pinned fixture commit unreachable in the shallow clone; rerun after fetching it: exit 0)",
"node scripts/check-registry-log-declared.mjs :: exit 0",
"node scripts/check-registry-log-declared.mjs --self-test :: exit 0",
"node scripts/check-rest-log-spy-declared.mjs :: exit 0",
"node scripts/check-rest-log-spy-declared.mjs --self-test :: exit 0",
"node scripts/check-system-context-census.mjs :: exit 0",
"node scripts/check-system-context-census.mjs --self-test :: exit 0",
"node scripts/check-undeclared-dep-imports.mjs :: exit 0",
"node scripts/check-undeclared-dep-imports.mjs --self-test :: exit 0",
"node scripts/docs-audit/check-affected-docs.mjs :: exit 0",
"node scripts/docs-audit/check-drift-comment.mjs :: exit 0",
"node scripts/pm/release-rehearsal-clone.mjs --self-test :: exit 0",
"node scripts/release-pending-publish.mjs --self-test :: exit 0",
"pnpm --filter @objectstack/spec run check:duration-unit-keys :: exit 0",
"pnpm check:changeset-gate-self-tests :: exit 0",
"pnpm check:cross-package-test-inputs :: exit 0",
"pnpm check:doc-authoring :: exit 0",
"pnpm check:docs-transcript-drift :: exit 0",
"pnpm check:driver-memory-census :: exit 0",
"pnpm check:dts-closure :: exit 0",
"pnpm check:dual-build-cjs-loads :: NOT MEASURED",
"pnpm check:engine-double-contract :: exit 0",
"pnpm check:gitlink-declared :: exit 0",
"pnpm check:issue-citations :: exit 0",
"pnpm check:lean-entry-closure :: exit 0",
"pnpm check:logger-receiver-detach :: exit 0",
"pnpm check:nul-bytes :: exit 0",
"pnpm check:objectql-double-limit :: exit 0",
"pnpm check:objectui-changeset :: exit 0",
"pnpm check:org-identifier :: exit 0",
"pnpm check:page-declaration-shape :: exit 0",
"pnpm check:pm-changeset-deadline-census :: exit 0",
"pnpm check:published-files :: exit 0",
"pnpm check:query-options-erasure :: exit 0",
"pnpm check:refd-timer-probe :: exit 0",
"pnpm check:slot-lookup :: exit 0",
"pnpm check:sourcemap-no-sources-content :: exit 0",
"pnpm check:test-source-alias :: exit 0",
"pnpm check:tier-file-adoption :: exit 0",
"pnpm check:type-check-coverage :: exit 0",
"pnpm check:type-check-debt :: NOT MEASURED",
"pnpm check:watch-hint-literal :: exit 0",
"pnpm check:where-matcher :: exit 0"
],
"not_measured": [
"pnpm check:dual-build-cjs-loads — needs every workspace package's dist (as dispatched for slice 12)",
"pnpm check:type-check-debt — its script runs --re-measure over every package; check:type-check-coverage ran, exit 0 (as dispatched for slice 12)"
],
"ran_reconciliation": "Run reconciliation — 62 derived, 60 run, 2 NOT-MEASURED, 0 UNRUN. (dispatch-gates --ran exit 0)",
"artifact_rosters": [
"node scripts/check-changeset-fixed.mjs :: exit 0",
"node scripts/check-platform-checklist-watchdog.mjs :: exit 0",
"node scripts/check-published-list-mirrors.mjs :: exit 0",
"node scripts/check-sdui-manifest.mjs :: exit 0",
"node scripts/check-skills-token-ratchet.mjs :: exit 0",
"pnpm --filter @objectstack/spec run check:error-code-provenance :: exit 0",
"pnpm --filter @objectstack/spec run check:meta-url-spelling :: exit 0",
"pnpm --filter @objectstack/spec run check:react-blocks :: exit 0",
"pnpm --filter @objectstack/spec run check:strictness-ledger :: exit 0",
"pnpm check:auth-mount-ledger :: exit 0",
"pnpm check:authz-resolver :: exit 0",
"pnpm check:cli-examples-parity :: exit 0",
"pnpm check:console-injection :: exit 0",
"pnpm check:docs-image-tag :: exit 0",
"pnpm check:engine-double-contract :: exit 0",
"pnpm check:error-code-casing :: exit 0",
"pnpm check:error-status-conformance :: exit 0",
"pnpm check:filter-alias-parity :: exit 0",
"pnpm check:future-spec-major :: exit 0",
"pnpm check:i18n-stale-fill :: exit 0",
"pnpm check:lockstep-package-count :: exit 0",
"pnpm check:object-def-param-keys :: exit 0",
"pnpm check:overlay-whitelist-table :: exit 0",
"pnpm check:pm-governed-prose :: exit 0",
"pnpm check:pm-label-desc-cap :: exit 0",
"pnpm check:pm-settings-deny-roster :: exit 0",
"pnpm check:published-readme-exports :: exit 3 (first run: PREREQUISITE NOT MET exit 3 for client-react / embedder-openai / knowledge-ragflow / organizations; built those with their closure under the lock, Tasks 54 successful, VERDICT command-exit 0; rerun exit 0)",
"pnpm check:route-ledger-census :: exit 0",
"pnpm check:scaffold-emission-policy :: exit 0",
"pnpm check:select-gate-families :: exit 0",
"pnpm check:select-shard-packages :: exit 0",
"pnpm check:skill-top-level-keys :: exit 0",
"pnpm check:stack-collection-maps :: exit 0",
"pnpm check:tenant-chokepoint :: exit 0",
"node scripts/check-dts-references.mjs --self-test :: exit 0",
"node scripts/check-platform-checklist-watchdog.mjs --self-test :: exit 0",
"node scripts/check-published-list-mirrors.mjs --self-test :: exit 0",
"node scripts/check-sdui-manifest.mjs --self-test :: exit 0",
"node scripts/check-skills-token-ratchet.mjs --self-test :: exit 0",
"node scripts/ci/scheduled-full-run.mjs --self-test :: exit 0",
"node scripts/ci/select-shard-timings-run.mjs --self-test :: exit 0",
"node scripts/pr-labels.mjs --self-test :: exit 0",
"node scripts/release-verify-npm.mjs --self-test :: exit 0",
"pnpm check:closing-target-claim :: exit 0",
"pnpm check:commit-card-trailers :: exit 0",
"pnpm check:partof-closing-keyword :: exit 0",
"pnpm check:pm-write-pace :: exit 0",
"pnpm check:single-claim-paths :: exit 0"
],
"pr_context_guards": [
"node scripts/check-closing-target-claim.mjs :: exit 0 ('PR #22936 binds no closing keyword to a card')",
"node scripts/check-partof-closing-keyword.mjs :: exit 0",
"node scripts/check-single-claim-paths.mjs :: exit 0 ('modifies none of the 1 declared at-most-one-writer path(s)')"
],
"mis_close_scan": "no closing keyword in the PR body, any commit message or the changeset",
"merge": "one merge of origin/main through scripts/pm/os-regen-merge.sh (407cee3 -> ec4f180 onto 018b077; no conflict; merge left no additional changes; the branch edits no os-regen artifact); origin/main moved three more commits afterwards (e4ad677, 06cc45d, 85b4ac6: create-objectstack, packages/spec permission.zod.ts + a migration, a cli scaffold), none touching a slice file; not merged again",
"ci": "not awaited, per dispatch"
},
"line_budget": [
"+28 / -0 .changeset/22161-lint-slice-13-one-line-fix.md",
"+88 / -4 packages/lint/src/rule-explanations.ts",
"+14 / -22 packages/lint/src/lint-flow-credential-literals.ts; +55 / -1 its .test.ts",
"+13 / -14 packages/lint/src/validate-readonly-flow-writes.ts; +45 / -3 its .test.ts",
"+7 / -8 packages/lint/src/validate-action-dispatch-contract.ts; +42 / -1 its .test.ts",
"+29 / -24 packages/lint/src/validate-security-posture.ts; +92 / -1 its .test.ts",
"+10 / -12 packages/lint/src/validate-sharing-rule-enforceability.ts; +43 / -2 its .test.ts",
"+12 / -12 packages/lint/src/validate-page-visualization-bindings.ts; +49 / -1 its .test.ts",
"+6 / -6 packages/lint/src/validate-readonly-action-writes.ts; +28 / -1 its .test.ts",
"+26 / -27 packages/lint/src/validate-flow-trigger-readiness.ts; +80 / -2 its .test.ts",
"total 18 paths, +667 / -141 vs origin/main 018b077"
],
"deviations": [
"Census instrument: the first base lint census flushed on process exit and lost most workers' records (vitest ends its workers without an exit event); it was re-run with a per-new-key append before any edit, and that run is the base. The base run recorded hint-shaped findings only; the after runs also record the fix-shaped findings data-model-rules.ts builds (object/missing-name-field 327, rollup/non-numeric-aggregand 282, field/select-missing-options 207, files this slice does not touch), so the comparable base over-200 count is 115 (112 + 3) against 97 after.",
"Two new RULE_EXPLANATIONS entries (security-wildcard-vama, flow-trigger-unknown-object): their reasoning had no entry to move into; slice 12's two new entries were accepted on the same reading. Side effect: their CLI rule: line gains the os explain pointer. Both constants were already barrel exports.",
"Hint-only code beyond hint expressions, in claimed files: validate-security-posture.ts computes nearestName over the declared + injected columns for the FLS hint (replacing the roster); validate-page-visualization-bindings.ts's describeSearch (hint-only caller) drops its name-pattern clause; lint-flow-credential-literals.ts deletes RESOLVES and NOT_A_GATE. No condition, branch, skip or dedupe moved.",
"Test pins changed text-only, in claimed test files: validate-readonly-flow-writes.test.ts ('Elevation is not a workaround here' and 'does land, even on a locked record' now read the explanation) and validate-flow-trigger-readiness.test.ts (the multi-event-arrays-deferred pin now reads the explanation). The declared rider in packages/cli / packages/metadata-protocol went unused (the one external hint pin, toContain('credentialRef'), holds).",
"The CLI unit tier, the metadata-protocol suite, os validate and the runtime probe 'after' readings are from the rebuilt dist of bc17d2d (lint src identical at ec4f180: the later commits are the changeset and the merge, which touches no lint file); the merge brought packages/cli (verify command + its test) and packages/objectql changes, and the CLI / metadata-protocol tiers were not rerun after it (AGENTS.md section 10 scope: incoming commits do not touch this diff's files or behaviour). Lint suite, typecheck, ablation, every gate and the PR-context guards ran at ec4f180.",
"Verify-lock queueing: the CLI after-run waited 377s behind another seat's verify.sh and the final lint run 266s; nothing ran unlocked. A lock -c script built from a shell variable was refused by the harness's removal safety check (it contained no rm); rerun as a scratch script file through '--', unchanged otherwise.",
"Commits carry AGENTS.md's model-free trailer pair rather than the harness reminder's model-named Co-Authored-By, and the PR body carries AGENTS.md's session-URL footer rather than the harness reminder's footer form; WIP commit subjects end '(WIP)' (squash lands the PR title)."
],
"files_changed": [
".changeset/22161-lint-slice-13-one-line-fix.md",
"packages/lint/src/rule-explanations.ts",
"packages/lint/src/lint-flow-credential-literals.ts + .test.ts",
"packages/lint/src/validate-readonly-flow-writes.ts + .test.ts",
"packages/lint/src/validate-action-dispatch-contract.ts + .test.ts",
"packages/lint/src/validate-security-posture.ts + .test.ts",
"packages/lint/src/validate-sharing-rule-enforceability.ts + .test.ts",
"packages/lint/src/validate-page-visualization-bindings.ts + .test.ts",
"packages/lint/src/validate-readonly-action-writes.ts + .test.ts",
"packages/lint/src/validate-flow-trigger-readiness.ts + .test.ts",
"18 paths, +667 / -141 vs origin/main 018b077; no packages/cli or packages/metadata-protocol file; worktree removed after the PR opened (node_modules deleted first, no --force needed)"
],
"census": {
"method": "Earlier slices' scratch preload (NODE_OPTIONS=--import, never committed): Array.prototype.push patched to record every finding-shaped object ({rule, hint or fix}), deduped by (rule, hint) per process, appended per new key, with its push site. Lengths are the hint alone. Base 7dbb89d (lint suite reading src; other tiers reading the base lint dist); after on the rebuilt dist.",
"the_18 (lint suite, hints . range before -> after)": [
"flow-credential-literal 3 . 488-646 -> 3 . 141-177",
"flow-update-readonly-when-field 2 . 531-549 -> 2 . 165-174",
"flow-update-readonly-field 10 . 230-400 -> 10 . 107-143",
"action-dispatch-contract-mismatch 3 . 491-514 -> 3 . 124-157",
"security-controlled-by-parent-ambiguous-relation 1 . 496 -> 3 . 167-174",
"security-master-detail-ungranted 8 . 271-314 -> 8 . 124-153",
"security-controlled-by-parent-no-relation 1 . 294 -> 1 . 194",
"security-fls-unknown-field 3 . 276-293 -> 4 . 89-132",
"security-wildcard-vama 1 . 218 -> 1 . 103",
"sharing-rule-object-not-shareable 3 . 471-482 -> 3 . 133-144",
"sharing-rule-object-controlled-by-parent 2 . 313-395 -> 2 . 155-169",
"page/visualization-without-binding 14 . 395-480 -> 14 . 148-183",
"action-api-update-readonly-when-field 4 . 458-470 -> 4 . 182-188",
"flow-api-trigger-secret-missing 1 . 461 -> 1 . 171",
"flow-time-relative-descriptor-unroutable 1 . 441 -> 1 . 166",
"flow-trigger-unroutable 1 . 295 -> 1 . 163",
"flow-trigger-unknown-event 2 . 191-268 -> 2 . 96-101",
"flow-trigger-unknown-object 2 . 179-210 -> 2 . 125-156"
],
"lint_suite_all_ids": "after at ec4f180: 239 ids fire, 97 with a hint over 200 = 21 fenced + 3 repo-gate + 73 author-time (comparable base: 115 = 21 + 3 + 91)",
"runtime_gate_suite (metadata-protocol)": "flow-credential-literal 3 . 488-646 -> 3 . 141-177; security-master-detail-ungranted 299 -> 146; flow-api-trigger-secret-missing 461 -> 171; flow-trigger-unknown-object 210 -> 156; none of the other 14",
"cli_unit_tier": "none of the 18 fires, before or after",
"os_validate_examples": "none of the 18 fires on app-crm / app-todo / app-showcase / app-multi-package, before or after; rule: line counts 9/7/71/3; output byte-identical after normalising the millisecond timing lines",
"runtime_probe (22 writes, hint 422 / 2xx advisory, before -> after)": "flow: credential 646/646/528/488 -> 173/173/177/141 (2xx); readonly static update/create 239/396 -> 116/139 (422); readonlyWhen 527 -> 161 (2xx, user and system); unknown-object record/time-relative 210/179 -> 156/125 (2xx); unknown-event token/array 191/268 -> 101/96 (422); time-relative unroutable 441 -> 166 (422); unroutable 295 -> 163 (422); api secret 461 -> 171 (422). object: cbp-no-relation 294 -> 194 (422); cbp-ambiguous 496 -> 167 (422); master-detail-ungranted 304 -> 147 (2xx). permission: fls-unknown-field 324 -> 132 (422); wildcard-vama 218 -> 103 (422); master-detail-ungranted 304 -> 147 (2xx). view / page / sharing_rule / action writes: none of the 18"
},
"zone2_readings": {
"item1_census": "All 18 lengths re-measured at the base equal the claim's (646, 549, 400, 514, 496, 314, 294, 293, 218, 482, 395, 480, 470, 461, 441, 295, 268, 210); each is at most 200 after, on every tier measured.",
"item2_excluded": "No edit to lint-flow-patterns.ts, data-model-rules.ts or validate-widget-bindings.ts, or their tests.",
"item3_wire_readers": "objectui main 2498a075 (read-only fetch into an own ref, git grep, ref deleted): Studio saveAdvisoryToast.ts formatFinding renders '[rule] where — message hint' for 2xx advisories (credential, readonlyWhen, unknown-object, ungranted-detail shorten); DraftChangesPanel.tsx renders 'p.hint || p.message' for securityPostureLint.ts, which runs validateSecurityPosture from the installed @objectstack/lint over object drafts and keeps errors — so for security-controlled-by-parent-no-relation and -ambiguous-relation the new line replaces the message there once objectui takes the release; metadata-client.ts checks only typeof hint; 422 issue renderers read path and message. REST PUT /api/v1/meta forwards issues / advisories as JSON; packages/mcp has no metadata write tool, so MCP/AI authors write through REST. In this repo toIssue copies hint verbatim and the advisory log line prints it; the one external pin (runtime-authoring-gate.flow-credential-literal.test.ts, toContain('credentialRef')) holds. No reader in either repo matches on hint text.",
"item4_watch_hint_literal": "It guards that every *_WATCH_HINTS population declaration in a gate script is a literal array; unrelated to a finding's hint. Ran inside the gate set: self-test 72 cases pass; '72 declaration(s) across 4 rostered name(s)', exit 0.",
"clause2_closure": "Built entries' exported names (runtime keys and declaration exports) identical before/after: index 370/552, runtime 6/11, rule-explanations 2/3; 0 added, 0 removed."
},
"remaining_for_this_card": [
"lint-flow-patterns.ts (2): flow-double-brace-interpolation 1339, flow-bare-dollar-reference 1231",
"data-model-rules.ts (6): unique/legacy-organization-composite 578, unique/unscoped-declared-index 380, object/missing-name-field 327, rollup/non-numeric-aggregand 282, unique/double-declaration 279, field/select-missing-options 207",
"validate-widget-bindings.ts (11): dashboard-filter-field-unprovisioned 561, chart-field-unknown 415, dashboard-filter-field-unknown 403, chart-measures-missing 369, widget-legacy-analytics-shape 338, widget-measures-missing 330, widget-filter-field-unknown 322, widget-legacy-analytics-unrenderable 320, table-count-only 311, chart-dimensions-missing 291, dashboard-filter-field-not-included 218",
"validate-searchable-fields.ts (3): searchable-field-unknown 448, searchable-field-unprovisioned 362, searchable-field-unsearchable 328",
"validate-flow-filter-tokens.ts (1): flow-filter-token-unknown 427",
"validate-action-locations.ts (1): action-no-placement 424",
"validate-mapping-target-fields.ts (1): mapping-target-field-unknown 405",
"validate-dashboard-widget-options.ts (1): unconsumed-widget-option 396",
"validate-sortable-fields.ts (3): sort-field-unprovisioned 378, sort-field-unsortable 332, sort-field-unknown 301",
"validate-visibility-predicates.ts (3): visibility-predicate-unknown-function 375, visibility-bare-identifier 221, visibility-predicate-syntax 214",
"validate-nav-access.ts (1): nav-object-ungranted 370",
"validate-hook-body-writes.ts (3): hook-body-write-unprovisioned-anchor 365, hook-body-write-unknown-field 275, hook-body-source-unparseable 254",
"validate-ai-agent-authoring.ts (2): agent-authoring-withdrawn 363, default-agent-outside-roster 237",
"validate-react-page-props.ts (4): react-chart-field-unprovisioned 362, react-prop-missing-required 277, react-page-source-unparseable 254, react-block-needs-record-context 228",
"validate-translatable-sections.ts (1): translation-section-name-missing 359",
"validate-action-body-writes.ts (4): action-body-write-unprovisioned-anchor 358, action-body-write-unknown-field 323, action-record-write-discarded 309, action-body-source-unparseable 254",
"validate-flow-node-writes.ts (2): flow-node-write-unprovisioned-anchor 358, flow-node-write-unknown-field 289",
"validate-managed-api-methods.ts (1): object/managed-api-method-unaffordable 357",
"validate-nav-object-servability.ts (1): nav-object-unservable 348",
"validate-rule-compilability.ts (2): validation-rule-json-schema-uncompilable 341, validation-rule-regex-uncompilable 300",
"validate-dataset-references.ts (2): dataset-include-unknown 336, dataset-field-unknown 206",
"validate-translation-references.ts (1): translation-target-unknown 317",
"validate-approval-approvers.ts (3): approval-approver-not-membership-tier 313, approval-expression-no-empty-policy 294, approval-expression-invalid 292",
"validate-seed-replay-safety.ts (1): seed-insert-mode-duplicates-on-replay 309",
"validate-chart-bindings.ts (1): chart-measure-unknown 285",
"validate-object-field-refs.ts (1): object-field-ref-unknown 284",
"validate-capability-references.ts (1): capability-reference-unknown 273",
"validate-record-title.ts (2): title-format-retired 267, title-unresolvable 237",
"validate-list-view-field-refs.ts (2): list-view-field-unknown 258, list-view-field-dotted 233",
"validate-view-containers.ts (1): view-container-shape 256",
"validate-seed-state-machine.ts (1): seed-value-outside-state-machine 251",
"validate-ai-surface-affinity.ts (1): ai-skill-surface-mismatch 235",
"validate-page-source-styling.ts (1): page-source-className-tailwind 231",
"lint-liveness-properties.ts (1): liveness-planned-property 230",
"validate-list-view-mode.ts (1): list-view-filters-in-views-mode 219",
"plus the 26 fenced ids as PR #22448 lists them (21 fire a hint over 200) and the 3 repo-gate ids (startup-open-vocabulary-verdict, startup-source-unparseable, startup-verdict-assertive-wording); the packages/cli ids are #22841's"
]
}

Generated by Claude Code

✅ ACCEPT: PR #22936 at `ec4f1802fc` (slice 13, `Part of #22161`). It lands through the queue once every check is green on this head

domain:spec seat 1 (#6017) · os-warren · session session_019G5ZnRrTMiwcHG6iZM19zf · 2026-10-12T03:56Z · holder of claim 6116324037. Report: 6117436127. Thread-read: 6117436127.

Read in the diff (/pulls/22936 diff, 18 paths, +667 / −141, equal to the PR's file list and inside the claim's surface; the declared packages/cli / packages/metadata-protocol rider went unused):

The 18 claimed ids in the eight claimed files get a hint of one remedy line; what each explained moves into its RULE_EXPLANATIONS entry.
No changed line touches a message, a rule id, a severity, a path, a condition or a return. The code moves are hint-only:
- lint-flow-credential-literals.ts deletes the hint-only RESOLVES and NOT_A_GATE;
- validate-security-posture.ts replaces the twelve-name field roster with nearestName(flsField, …) over the declared and injected columns (object-graph.ts:589); it feeds the hint only;
- validate-page-visualization-bindings.ts's describeSearch, whose only caller is the hint, drops the name-pattern clause.
Two new entries, accepted on slice 12's precedent: security-wildcard-vama and flow-trigger-unknown-object had none, so their rule: line now carries the os explain pointer.
Tracker ids appear only in // comments; the explanations cite ADRs only.
One trade, accepted: page/visualization-without-binding's line says "drop '…' from the whitelist" rather than naming appearance.allowedVisualizations, to stay at 183 ≤ 200. Its explanation names the key three times (rule-explanations.ts:3275, :3292, :3300 on the branch).

The changeset's sentences, checked against the diff: the 18 before → after maxima match the report's census; "a list becomes a nearest name" is the nearestName hunk; "names the field TYPE … no longer repeats the name pattern" is the describeSearch hunk; the two new entries and their covers lines are in the diff; "Unchanged: every message … rule id, severity and path" holds in every hunk read. The runtime-door FROM → TO figures (13 of 18 at the gate) and the Studio reader reading (objectui 2498a075) are the dev's measurements, not re-run here.

Evidence accepted: lint 137 files / 6,561 tests, build and typecheck at the head; the CLI unit tier 282 / 4,262 and metadata-protocol 226 files on the rebuilt dist; the built entries' export closure unchanged (0 added, 0 removed), so Clause-②: no holds; one ablation (the security-wildcard-vama 218-character hint restored: exactly the new bound pin red, reading 218); os validate on the four example apps byte-identical apart from timing lines. Gate union at the head: 62 derived, 60 run, 0 unrun; check:dual-build-cjs-loads and check:type-check-debt NOT MEASURED locally, which CI answers.

Landing: check-governed-merges.mjs --pr 22936 answers NOT governed, 808 changed lines (≤ 3,000). No contract-review face is hit (packages/lint hint prose, no published schema, Clause-②: no), so no at-tier review is owed. CI at this head: 14 success, 3 skipped, 14 in progress; it readies and arms once every check is green.

Out-of-scope findings: one observation (the CLI unit tier holds the verify lock at the container's 10-minute foreground cap). Not a defect class: noted, not filed.

Remaining for this card: 73 author-time ids still carry a hint over 200, listed by file in the report and PR #22936's body.

Transition: `pm:dispatched` → `pm:blocked` on #22949. Slice 13's PR #22936 is accepted and green, and held out of the merge queue by a queue-wide gate red that is not this card's

domain:spec seat 1 (#6017) · os-warren · session session_019G5ZnRrTMiwcHG6iZM19zf · 2026-10-12T05:07Z · holder of claim 6116324037.

The work is done: PR fix(lint): one-line fix lines for 18 more author-time rule ids; os explain RULE_ID carries what they explained #22936 (slice 13, Part of #22161) holds ACCEPT 6117464286, and every check on its head ec4f1802fc is green.
What holds it: the merge queue's Test Core reds on the suite-duration ceiling table that went live with 1bd612bd6 today. @objectstack/cloud-connection measured 177.5 s, 200.3 s and 204.8 s against its 163.89 s ceiling, and @objectstack/plugin-audit 190.7 s against 185.93 s, in three groups of PRs that touch neither package. The anchor is ci: merge-queue Test Core reds on the new suite-duration ceiling — @objectstack/cloud-connection measured 177.5 s and 200.3 s vs its 163.89 s ceiling, in two groups of PRs that do not touch it (live since 1bd612bd6) #22949 (sightings 6118119085). The queue removed PR fix(lint): one-line fix lines for 18 more author-time rule ids; os explain RULE_ID carries what they explained #22936 at 2026-10-12T05:06Z, and the triage checklist says not to re-queue before the anchor resolves.
Body lines added: Blocked-by: #22949 and Unlock-action: re-check PR #22936. When ci: merge-queue Test Core reds on the new suite-duration ceiling — @objectstack/cloud-connection measured 177.5 s and 200.3 s vs its 163.89 s ceiling, in two groups of PRs that do not touch it (live since 1bd612bd6) #22949 closes, the seat re-checks the PR's head and re-arms it. ⛔ No dev is re-dispatched for finished work.
Slice 14 waits too: every slice edits rule-explanations.ts, so the slices are serial behind PR fix(lint): one-line fix lines for 18 more author-time rule ids; os explain RULE_ID carries what they explained #22936.
The assignee stays: this seat follows PR fix(lint): one-line fix lines for 18 more author-time rule ids; os explain RULE_ID carries what they explained #22936 to MERGED.

Navigation Menu

Repository navigation

[maintainer] validate: the `field-no-consumers` warning is one 856-character line, printed by validate, build and dev alike — one-line verdict + `rule:` id + a pointer to the full reasoning (`os explain`, which today takes only schema names) #22161

Today

Asked for

Triage: first grade, `enhancement` · `priority:p3` · `domain:spec` · `area:devpath` · `pm:queue` (`finding` removed). Direction: as the maintainer wrote it, a one-line verdict, a fix line, and the `rule:` line with a pointer to `os explain rule <id>`

Seat review of PR #22339 at `c76a01bb6`: patch round 2 (one defect the diff creates, plus the docs blocks it makes false), then the contract review

136 remaining items

✅ ACCEPT: PR #22909 at `9d56f0f431` (slice 12, `Part of #22161`). It lands when its checks settle green

Landed: PR #22909 → `7dbb89dc5d` (slice 12, `Part of #22161`). The card goes back to `pm:queue` for its later slices

✅ ACCEPT: PR #22936 at `ec4f1802fc` (slice 13, `Part of #22161`). It lands through the queue once every check is green on this head

Transition: `pm:dispatched` → `pm:blocked` on #22949. Slice 13's PR #22936 is accepted and green, and held out of the merge queue by a queue-wide gate red that is not this card's

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[maintainer] validate: the field-no-consumers warning is one 856-character line, printed by validate, build and dev alike — one-line verdict + rule: id + a pointer to the full reasoning (os explain, which today takes only schema names) #22161

Description

Today

Asked for

Activity

objectstack-fleet commented on Oct 8, 2026

Triage: first grade, enhancement · priority:p3 · domain:spec · area:devpath · pm:queue (finding removed). Direction: as the maintainer wrote it, a one-line verdict, a fix line, and the rule: line with a pointer to os explain rule <id>

objectstack-fleet commented on Oct 8, 2026

objectstack-fleet commented on Oct 8, 2026

objectstack-fleet commented on Oct 8, 2026

Seat review of PR #22339 at c76a01bb6: patch round 2 (one defect the diff creates, plus the docs blocks it makes false), then the contract review

objectstack-fleet commented on Oct 8, 2026

136 remaining items

objectstack-fleet commented on Oct 12, 2026

objectstack-fleet commented on Oct 12, 2026

✅ ACCEPT: PR #22909 at 9d56f0f431 (slice 12, Part of #22161). It lands when its checks settle green

objectstack-fleet commented on Oct 12, 2026

Landed: PR #22909 → 7dbb89dc5d (slice 12, Part of #22161). The card goes back to pm:queue for its later slices

objectstack-fleet commented on Oct 12, 2026

objectstack-fleet commented on Oct 12, 2026

objectstack-fleet commented on Oct 12, 2026

✅ ACCEPT: PR #22936 at ec4f1802fc (slice 13, Part of #22161). It lands through the queue once every check is green on this head

objectstack-fleet commented on Oct 12, 2026

Transition: pm:dispatched → pm:blocked on #22949. Slice 13's PR #22936 is accepted and green, and held out of the merge queue by a queue-wide gate red that is not this card's

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

[maintainer] validate: the `field-no-consumers` warning is one 856-character line, printed by validate, build and dev alike — one-line verdict + `rule:` id + a pointer to the full reasoning (`os explain`, which today takes only schema names) #22161

Triage: first grade, `enhancement` · `priority:p3` · `domain:spec` · `area:devpath` · `pm:queue` (`finding` removed). Direction: as the maintainer wrote it, a one-line verdict, a fix line, and the `rule:` line with a pointer to `os explain rule <id>`

Seat review of PR #22339 at `c76a01bb6`: patch round 2 (one defect the diff creates, plus the docs blocks it makes false), then the contract review

✅ ACCEPT: PR #22909 at `9d56f0f431` (slice 12, `Part of #22161`). It lands when its checks settle green

Landed: PR #22909 → `7dbb89dc5d` (slice 12, `Part of #22161`). The card goes back to `pm:queue` for its later slices

✅ ACCEPT: PR #22936 at `ec4f1802fc` (slice 13, `Part of #22161`). It lands through the queue once every check is green on this head

Transition: `pm:dispatched` → `pm:blocked` on #22949. Slice 13's PR #22936 is accepted and green, and held out of the merge queue by a queue-wide gate red that is not this card's