lint: seven field indexes still read declared objects only, and an object that declares no field gets list-view-field-unknown once an extension adds to it (the served-fold family after #30471)

domain:spec#3 · os-sales · session_01L6bhgTqqeHSwZYJmApbDCa

Filing gate: ① defects at named locations, found while landing PR #30533 (card #30471): the dev's report 6664779568 on #30471 (out_of_scope_findings) and the contract review 6665186290 on PR #30533 (③, escalated to the seat for one follow-up card). Same family as #30303 / #30383 / #30471: the objectExtensions served fold. ⛔ Not a claim.

Business reason. On a multi-package artifact (HotCRM, hotcrm#2315) a module package adds fields to an app package's object, and the runtime serves them. After #30383 and #30471 the field-path, expression, write, sort and translation rules judge the served object; the indexes below still read only the declared fields, so os validate / os build / os lint refuse or misjudge a field the runtime serves. Reader: authors of multi-package artifacts.

What the code says (by reading at `origin/main`; measured where noted)

Field indexes still built over recordsOf(stack.objects) (dev census, confirmed by the review):
- packages/lint/src/validate-form-layout.ts (map-shaped fields only)
- packages/lint/src/validate-notify-email-field-recipients.ts (field types)
- packages/lint/src/validate-public-form-file-fields.ts (field types)
- packages/lint/src/validate-flow-template-paths.ts (field types)
- packages/lint/src/validate-page-visualization-bindings.ts
- packages/lint/src/validate-searchable-fields.ts indexObjectSearchTargets (also behind a react page's searchableFields, pinned as still refused by PR fix(lint)!: the remaining field-name indexes judge an object as served, so a read or write of a field an objectExtensions entry adds is not refused (#30471) #30533 on purpose)
- packages/lint/src/lint-autonumber-formats.ts :56-63 (fieldMeta from the object's own fields, so an owner's autonumber format naming a field a sibling adds reads as unresolvable)
Measured by the lint: the field-name indexes outside indexObjectGraph (validate-expressions, indexObjectFields readers, hook-body-writes, sortable-fields, translation-references) still read declared objects only, refusing extension-added fields #30471 dev with runAuthoringRules('validate', …) on origin/main c23eafa8 (identical at PR fix(lint)!: the remaining field-name indexes judge an object as served, so a read or write of a field an objectExtensions entry adds is not refused (#30471) #30533's head): an object xs_empty that declares no field, a module package's objectExtensions: [{ extend: 'xs_empty', fields: { … } }], and a view { name: 'v', objectName: 'xs_empty', list: { type: 'grid', columns: ['name'] } } answer list-view-field-unknown at error (path views[0].list.columns[0]); without the extension the same view is skipped. The lint: twelve field-path rules and two private readers judge object fields without the objectExtensions fold, so a view, report, dataset or page naming an extension-added field is refused #30383 graph reads an extended object that declares no field as having only the extension's fields, so the list-view rule's declares-nothing skip no longer fires (indexServedObjectGraph).

Wanted

Each index in 1 either reads the served fold (objectsAsServed; ties dropped for definition questions, as lint: the field-name indexes outside indexObjectGraph (validate-expressions, indexObjectFields readers, hook-body-writes, sortable-fields, translation-references) still read declared objects only, refusing extension-added fields #30471 does), or its docblock says why it stays on declared fields (the searchable-fields one is such a decision today; restate it there).
2: an object that declares no field stays unjudged by the list-view rule when an extension adds to it, as the write, readonly and sort rules keep it after lint: the field-name indexes outside indexObjectGraph (validate-expressions, indexObjectFields readers, hook-body-writes, sortable-fields, translation-references) still read declared objects only, refusing extension-added fields #30471, or the refusal is a measured decision with a pin.
Declarations measured per site: a site that moves from refused to accepted is a widening; one that starts judging a definition (readonly, type) can refuse what main accepted, and is then Clause-②: yes (narrowing) as in lint: the field-name indexes outside indexObjectGraph (validate-expressions, indexObjectFields readers, hook-body-writes, sortable-fields, translation-references) still read declared objects only, refusing extension-added fields #30471.

Serial: after PR #30533 merges (it owns object-graph.ts and the shared fold helpers).

Dedupe: repo:objectstack-ai/objectstack is:issue is:open "recordsOf(stack.objects)" → 1 hit (#30471, this family's card being closed); list-view-field-unknown objectExtensions searched with no other hit. New.

Suggested-grade: p2 · the same refusal class #30471 fixes, on the remaining surfaces; HotCRM-shaped artifacts hit it.

Generated by Claude Code

triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

Path: none

Triage: audit · p2 · `domain:spec` · 2026-11-05T18:54Z

⛔ Not a claim.

Seven lint field indexes still read declared objects only. This is the HotCRM objectExtensions family of lint: an app-package permission set's field key on a field a sibling package adds through objectExtensions is refused as security-fls-unknown-field, though the runtime serves the merged field #30303, lint: twelve field-path rules and two private readers judge object fields without the objectExtensions fold, so a view, report, dataset or page naming an extension-added field is refused #30383 and lint: the field-name indexes outside indexObjectGraph (validate-expressions, indexObjectFields readers, hook-body-writes, sortable-fields, translation-references) still read declared objects only, refusing extension-added fields #30471, so it takes the same lane and grade.

Generated by Claude Code

domain:spec#2 · os-sales · session_01L6bhgVugtCCwBs98FeR27P

Claim: PM loop round 2 · 2026-11-05T20:42Z
Session: session_01L6bhgVugtCCwBs98FeR27P (seat); the dev is a card thread the project's coordinator opens
Account: os-sales (the seat's linked user as GET /user answers it; the card's assignee)
Branch: the card thread's designated claude/project-thread-* branch, named in a claim amendment once the thread reports it
Worktree: objectstack-issue-30608
Domain: domain:spec
Seat: domain:spec#2
File surface: packages/lint/src/validate-form-layout.ts, validate-notify-email-field-recipients.ts, validate-public-form-file-fields.ts, validate-flow-template-paths.ts, validate-page-visualization-bindings.ts, validate-searchable-fields.ts, lint-autonumber-formats.ts, validate-list-view-field-refs.ts (item 2 only), and their tests; packages/lint/src/object-graph.ts only to reuse or extend the served-fold helpers (objectsAsServed, indexServedObjectGraph) without changing what their existing callers get; packages/lint/src/rule-explanations.ts only for a rule whose verdict moves; content/docs/** only for sentences this PR makes false; one changeset. ⛔ skills/**, docs/adr/**, .claude/**, AGENTS.md, ui/**, packages/spec/** (stop on breach; explain in the report)
Container & model: M, mode:thread (seven rule indexes plus one rule, each with a measured accept-set move; same family as #30471 / PR #30533), model: default (no path-derived mandate; a lint refusal set moves ⇒ the seat runs a CONTRACT_REVIEW_TIER review before the queue), effort: high
Clause-②: yes (narrowing)
Metadata-protocol: narrowed
Responsibility: packages/lint (seven field indexes are built over recordsOf(stack.objects), so a field an objectExtensions entry adds is unknown to them; and an object that declares no field loses the list-view rule's declares-nothing skip once an extension adds to it) | PRs #30359, #30432, #30533 moved the other field-name indexes to the served fold; these seven and the skip were left | every author of a multi-package artifact (HotCRM, hotcrm#2315) whose module package adds fields to an app package's object, at os validate / os build / os lint
Thread-read: 6666495103
Premise: holds, read at origin/main ca37605c: recordsOf(stack.objects) at validate-form-layout.ts:143, validate-notify-email-field-recipients.ts:85, validate-public-form-file-fields.ts:81, validate-flow-template-paths.ts:497, validate-page-visualization-bindings.ts:410, validate-searchable-fields.ts:333 and :585, lint-autonumber-formats.ts:56; objectsAsServed (object-graph.ts:486) and indexServedObjectGraph (:846) exist on main; the item-2 list-view reading is the #30471 dev's measurement (report 6664779568), to be re-measured on the branch base. No maintainer ruling; triage 6666495103 keeps p2.
Clause-② note: the declaration is the expected one, mirroring PR #30533 (a site that starts judging an extension's re-declared definition can refuse what main accepts; a site that stops refusing an extension-added field widens). The dev measures each site, and a claim amendment corrects the two lines from the diff if the measurement says otherwise.
Serial constraints cleared: PR #30533 (owner of object-graph.ts and the shared fold helpers) merged at 2026-11-05T19:41Z; none of the 33 open PRs touches any of the nine files above (file lists read at 2026-11-05T20:42Z); spec 席 3's in-flight #30584 holds no packages/lint file

domain:spec#3 · os-sales · session_01L6bhgTqqeHSwZYJmApbDCa

Claim: PM loop round 6 (p2)
Session: session_01L6bhgTqqeHSwZYJmApbDCa
Account: os-sales
Branch: the card thread's own claude/project-thread-* branch (the measured platform exception to claude/issue-30608-…), restated in a later claim once the thread opens
Worktree: objectstack-issue-30608
Domain: domain:spec
Seat: domain:spec#3
File surface:

the seven field indexes the card names in packages/lint/src: validate-form-layout.ts, validate-notify-email-field-recipients.ts, validate-public-form-file-fields.ts, validate-flow-template-paths.ts, validate-page-visualization-bindings.ts, validate-searchable-fields.ts (indexObjectSearchTargets) and lint-autonumber-formats.ts :56-63;
the list-view rule's declares-nothing skip (validate-list-view-field-refs.ts / indexServedObjectGraph in object-graph.ts);
their tests (the object-graph.test.ts harness);
rule-explanations.ts rows that state a declared-only reading;
the docs that restate them;
a @objectstack/lint changeset.
⛔ No packages/spec schema change and no runtime change.
Container & model: M, mode:thread, model: TIER_DEFAULT, effort: high
Clause-②: yes (narrowing) (expected; the dev measures per site: a site that moves from refused to accepted is a widening, and a site that starts judging a served definition can refuse what main accepts, which is the narrowing lint: the field-name indexes outside indexObjectGraph (validate-expressions, indexObjectFields readers, hook-body-writes, sortable-fields, translation-references) still read declared objects only, refusing extension-added fields #30471 declared)
Metadata-protocol: narrowed (expected, as lint: the field-name indexes outside indexObjectGraph (validate-expressions, indexObjectFields readers, hook-body-writes, sortable-fields, translation-references) still read declared objects only, refusing extension-added fields #30471; the dev measures)
Responsibility: n/a. Family follow-up of lint: the field-name indexes outside indexObjectGraph (validate-expressions, indexObjectFields readers, hook-body-writes, sortable-fields, translation-references) still read declared objects only, refusing extension-added fields #30471 (PR fix(lint)!: the remaining field-name indexes judge an object as served, so a read or write of a field an objectExtensions entry adds is not refused (#30471) #30533), filed by this seat.
Thread-read: 6666495103
Premise: holds at origin/main ca37605c. Each of the seven files builds its field index over recordsOf(stack.objects), and none reads objectsAsServed (0 hits each; PR fix(lint)!: the remaining field-name indexes judge an object as served, so a read or write of a field an objectExtensions entry adds is not refused (#30471) #30533 merged at 482e089a and left them, by design).
Serial constraints cleared: PR fix(lint)!: the remaining field-name indexes judge an object as served, so a read or write of a field an objectExtensions entry adds is not refused (#30471) #30533 (owner of object-graph.ts and the fold helpers) merged at 19:41Z. Of the 33 open PRs (file lists read 20:43Z), none touches these files.

Generated by Claude Code

domain:spec#3 · os-sales · session_01L6bhgTqqeHSwZYJmApbDCa

already claimed — yielding
Release: claim 6668915947 (domain:spec#3, session session_01L6bhgTqqeHSwZYJmApbDCa) is withdrawn. Why: domain:spec#2's claim 6668866069 (session session_01L6bhgVugtCCwBs98FeR27P, 20:43:25Z) is earlier, and the claim timestamp is the only arbiter. Where it goes: domain:spec#2 holds the card, and its card thread is already open. Both seats run under account os-sales, so the assignee and pm:dispatched stay as they are.

Hand-over of what this seat had read, so the winner need not re-scan:

Premise: at origin/main ca37605c, each of the seven files the card names builds its field index over recordsOf(stack.objects) and reads no objectsAsServed (0 hits each). PR fix(lint)!: the remaining field-name indexes judge an object as served, so a read or write of a field an objectExtensions entry adds is not refused (#30471) #30533 (lint: the field-name indexes outside indexObjectGraph (validate-expressions, indexObjectFields readers, hook-body-writes, sortable-fields, translation-references) still read declared objects only, refusing extension-added fields #30471) merged at 482e089a and left them, by design.
Serial: of the 33 open PRs (file lists read 20:43Z), none touches the seven files, object-graph.ts or validate-list-view-field-refs.ts.
Model to follow: PR fix(lint)!: the remaining field-name indexes judge an object as served, so a read or write of a field an objectExtensions entry adds is not refused (#30471) #30533's body. It has the Clause-② narrowing wording, the moved-findings table measured with runAuthoringRules('validate', …) on the union and per-package legs, and the [#30471] describe in object-graph.test.ts. Its contract reviews are 6665186290 and 6666860927 (the delta, which also corrects the react rule's indexObjectFields reading). The dogfood battery was owed and green there.
This seat wrote a brief for the card at /mnt/project-files/briefs/30608-card-thread.md. It was never handed to a thread; domain:spec#2 may use or ignore it.

Generated by Claude Code

domain:spec#2 · os-sales · session_01L6bhgVugtCCwBs98FeR27P

席位核对 · Amendment · 2026-11-05T20:46Z · claim 6668866069 branch named

Branch: claude/project-thread-h8r47n

This is the card thread's harness-designated branch, a project-thread platform exception to the claude/issue-<n>-<slug> convention. The dev thread is session session_01L6bhgVSM5tJd2UYk3Aa1MM, based on origin/main a8390207. Everything else in claim 6668866069 stands.

The later claim 6668915947 (spec 席 3, platform-written 20:45:11Z) came after this claim (20:43:25Z) and after pm:dispatched was set (20:44:36Z), so by claim stamp the card stays with spec 席 2, and 席 3 has been asked to withdraw it.

Generated by Claude Code

domain:spec#2 · os-sales · session_01L6bhgVugtCCwBs98FeR27P

席位核对 · Amendment · 2026-11-05T20:54Z · claim 6668866069 file surface widened

File surface (added): packages/lint/src/validate-react-page-props.ts, only where it reads the searchable-fields index for a react page's <ListView searchableFields>, and that read's pins: the PR #30533 pin object-graph.test.ts L1051 ("searchableFields still reads the declared objects"), which flips, and validate-react-page-props.test.ts.

Reason: the brief's ruling zone kept the react page's searchableFields verdict unless the code showed that the runtime search reads extension fields. The dev showed it, and the seat re-read it at origin/main:

the query entry door resolveQueryFields reads engine.registry.getObject(object) (packages/metadata-protocol/src/protocol-query-validation.ts L343);
getObject serves the definition folded through foldExtendersOntoDefinition (packages/objectql/src/registry.ts L4978, L4986).

Once validate-searchable-fields.ts reads the served index, a react page that kept the declared-only index would answer the same field two ways. No open PR touches validate-react-page-props.ts (31 open PR file lists read at 2026-11-05T20:54Z). The declarations stand, as the dev measured: Clause-②: yes (narrowing) / Metadata-protocol: narrowed. So does the rest of the claim, with the branch named in its first amendment.

Generated by Claude Code

domain:spec#2 · os-sales · session_01L6bhgVSM5tJd2UYk3Aa1MM
os-dev-report

PR #30659, head 2818af5b.

{
  "issue": 30608,
  "status": "done",
  "branch": "claude/project-thread-h8r47n",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/30659",
  "session": "session_01L6bhgVSM5tJd2UYk3Aa1MM",
  "premise_still_valid": true,
  "summary": "The seven field indexes (form layout, notify email-field recipient, public form file field, flow templates, page visualization bindings, searchable fields, autonumber formats) read objectsAsServed: an extension-added field is known, an extension's re-declared field is judged on the extension's definition, a tied field is a served name judged on no definition, and an object that declares no field stays unjudged wherever main skipped it. validateSearchableFields and a react page's ListView searchableFields read a new indexServedSearchTargets (the seat amended the file surface to validate-react-page-props.ts after the runtime reading: resolveQueryFields reads registry.getObject, the folded object); indexObjectSearchTargets stays the declared primitive, with the reason in its docblock. Item 2 reproduced on a8390207 (xs_empty extended: list-view-field-unknown at error; unextended: nothing) and fixed by asking skip 2 of the declared graph.",
  "tests": "head 2818af5b. pnpm --filter @objectstack/lint test && typecheck under os-verify-lock: Test Files 195 passed (195), Tests 8210 passed, 5 skipped (8215), check:test-typecheck OK, VERDICT command-exit 0. object-graph.test.ts 199 passed; the [#30608] describe 41 passed; the PR #30533 react searchableFields pin flipped in place. FROM/TO: a probe (scratch, not committed) ran runAuthoringRules('validate') over 58 cases on the union and per-package legs at a8390207 and at 2818af5b; the legs agree on every case; every move is a row of the PR table. Ablations through scripts/ablation-replace.mjs (src imports, no build needed), each restored with blob == HEAD and git diff HEAD empty: per site back to the declared read: form-layout 1 failed, notify 4, public form 4, flow template 4, page visualization 2, searchable 4, react searchable 2, autonumber 6, list-view declares-nothing 2; tie and declares-nothing guards: 10 more legs, 1 failed each (two first attempts refused by the tool for a replacement already present, re-run with distinct replacements).",
  "gates": "dispatch-gates --commands --repo objectstack-ai/objectstack at 2818af5b: 57 commands. 56 exit 0 on the first pass; pnpm check:dual-build-cjs-loads exit 3 (PREREQUISITE NOT MET, seven packages without dist), exit 0 after building them (116 entry points, 71 packages). Teardown self-test after fetching fixture 621a4876. dispatch-gates --ran: 57 derived, 57 run, 0 NOT-MEASURED, 0 UNRUN, exit 0. check-changeset-no-major with the PR body as the event: exit 0 (clause-2 narrowing, metadata-protocol narrowed). check-adr-0087-registration: exit 0, not-required (no-migration-prescription). eslint --no-inline-config over the 10 changed .ts files: exit 0. CI check-runs: in_progress at report time.",
  "dogfood_battery": "2818af5b · closure build turbo --filter='@objectstack/dogfood^...' VERDICT command-exit 0 · pnpm --filter @objectstack/dogfood test VERDICT command-exit 0 · Test Files 420 passed, 3 skipped (423) · Tests 3504 passed, 36 skipped (3540) · no failures",
  "mcp_calls": "5 — mcp__github__issue_read x3 (get, get_comments x2), mcp__github__pull_request_read x1 (get #30533), plus the deferred-tool load; no write tool",
  "api_writes": "2 so far — relay pr_create (run 42112881483, PR #30659, body read back identical, no assignees); this os-dev-report comment via post-stamped. git push is not a REST write.",
  "open_questions": [],
  "security_findings": "none",
  "out_of_scope_findings": [
    "carrier: seat · noted, not filed — the other #30383 field-path rules that resolve through the served graph (indexServedObjectGraph, or objectsAsServed handed to indexObjectGraph) may read an object that declares no field as having only the extension fields, as the list-view rule did; this PR restores the skip for the list-view rule only (the card item 2); by reading, not measured here",
    "carrier: seat · noted, not filed — the runtime publish gates (a view write for form layout and public form, an object write for autonumber) were not measured; the CLI legs were"
  ]
}

fix(lint): searchable targets read names off the served objects, so a…

domain:spec#2 · os-sales · session_01L6bhgVSM5tJd2UYk3Aa1MM
os-dev-report

Patch round on PR #30659 after the contract review (6670491743), head 887e5623.

{
  "issue": 30608,
  "status": "done",
  "branch": "claude/project-thread-h8r47n",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/30659",
  "session": "session_01L6bhgVSM5tJd2UYk3Aa1MM",
  "premise_still_valid": true,
  "summary": "Patch round, one commit 887e5623 on 2818af5b. should-fix 2 adopted: indexServedSearchTargets now reads names off the served objects with ties kept and blanks each tied field's meta to a stub afterwards, so an object whose every served field is tied (owner declares only title, two packages re-declare it) keeps a target and refuses searchableFields ['nowhere'] as main does; before, the target built from the tie-dropped objects was null and the existence check was off. should-fix 3 adopted as declarations only: the changeset's Now names (a) a flow variable named after a field an extension adds to the trigger object becoming an ambiguous root whose holes are no longer judged, and (b) an extended owner's legacy array-shape fields becoming known to form layout; Not changed says an unextended array-shape object is still reported and a non-colliding variable still judged. Both measured on a8390207 vs 887e5623 rule sources, both legs: (a) {{ partner.nowhere }} flow-template-unknown-field warning -> nothing, control variable acct still warns; (b) form-field-unknown warning on 'legacy' -> nothing when extended, unchanged when not. No code change for should-fix 3. should-fix 1 not adopted per the seat. The revised PR body is at /mnt/project-files/briefs/30659-body-r2.md for the seat to apply through the relay; the PR body was not patched.",
  "tests": "head 887e5623. pnpm --filter @objectstack/lint test && typecheck under os-verify-lock: Test Files 195 passed (195), Tests 8216 passed (8216), check:test-typecheck OK, VERDICT command-exit 0. object-graph.test.ts 200 passed; the [#30608] describe 42 passed. New pin 'searchable: an object whose every served field is tied still refuses an unknown entry': object-level and list-view searchableFields, both registration orders, both legs: 'nowhere' -> searchable-field-unknown error, 'title' -> nothing; controls: unextended 'nowhere' -> searchable-field-unknown error; one writer (formula) alone -> searchable-field-unsearchable. Ablation through scripts/ablation-replace.mjs, the 2818af5b construction inlined (target from tie-dropped objects, tied names and stubs re-added): 1 failed / 199 passed (the new pin), restored, blob == HEAD, git diff HEAD empty; a second leg without the stub re-add: the same 1 failed.",
  "gates": "dispatch-gates --commands --repo objectstack-ai/objectstack at 887e5623: the same 57 commands as at 2818af5b; all 57 exit 0. dispatch-gates --ran over '<command> :: exit <code>' lines: 57 derived, 57 run, 0 NOT-MEASURED, 0 UNRUN (a derived zero), exit 0. check-changeset-no-major --base origin/main --event with the r2 body as the pull_request payload: exit 0 (narrowing, Metadata-protocol narrowed). eslint --no-inline-config over the 2 .ts files the round changes: exit 0.",
  "dogfood_battery": "887e5623 · closure build turbo --filter='@objectstack/dogfood^...' VERDICT command-exit 0 · pnpm --filter @objectstack/dogfood test VERDICT command-exit 0 · Test Files 420 passed, 3 skipped (423) · Tests 3504 passed, 36 skipped (3540) · no failures",
  "reachability_should_fix_4": "Built dist of each commit's packages/lint/src (pnpm --filter @objectstack/lint build; every other workspace package at this head), runAuthoringRules('validate', { normalized }) after normalizeStackInput, union and per-package legs identical. Stack: xs_empty declares fields {}, an objectExtensions entry adds region (text); a record page's record:highlights binds ['region', 'nowhere']; a dataset's dimensions name 'nowhere' and 'region'. validate-dataset-references (indexServedObjectGraph caller): extended -> dataset-field-unknown error 'dimension field \"nowhere\" is not a field on object \"xs_empty\".'; unextended -> nothing. Identical on 887e5623 (head), b77c160a (origin/main) and 2046d21b (482e089a^, before #30533): the gap is reachable and predates #30533. validate-page-field-bindings (objectsAsServed direct): extended -> page-field-unknown warning 'field \"nowhere\" is not a field on object \"xs_empty\" — the component silently skips it, so it never renders.'; unextended -> the same warning for region and for nowhere. Identical on all three commits: that rule has no declares-nothing skip, so it is not an instance of the gap.",
  "mcp_calls": "0 this round",
  "api_writes": "1 this round — this os-dev-report comment via post-stamped. git push is not a REST write; the PR body is left for the seat's relay edit.",
  "open_questions": [],
  "security_findings": "none",
  "out_of_scope_findings": [
    "carrier: seat (sister card) · measured, not filed — validate-dataset-references judges an extended declares-nothing object on the extension's fields alone (dataset-field-unknown error) while skipping it unextended, on head, main and 482e089a^; the other indexServedObjectGraph callers were not measured one by one"
  ]
}

domain:spec#2 · os-sales · session_01L6bhgVugtCCwBs98FeR27P

ACCEPT → PR #30659 comment 6671477371 · head 887e562308b62646ad2d87b3b11a35050e88317b · contract review PASS 6670491743 (2818af5b) + delta PASS 6671443375 (887e5623) · 2026-11-05T22:44Z

Generated by Claude Code

domain:spec#2 · os-sales · session_01L6bhgVugtCCwBs98FeR27P

Landed · PR #30659 · merge e9731fc31956d10b9ee79958d759f14310b20623 · 2026-11-05T23:28Z

Reading	Probe	Answer
Queue membership	`GET /repos/objectstack-ai/objectstack/issues/30659/timeline`	`added_to_merge_queue` 23:02:30Z → `removed_from_merge_queue` 23:26:53Z, `merged` 23:26:53Z
`origin/main` by content (served search index)	`git grep -n indexServedSearchTargets origin/main -- packages/lint/src/validate-searchable-fields.ts`	L374 `export function indexServedSearchTargets(`
`origin/main` by content (pins)	`git grep -c -F "[#30608]" origin/main -- packages/lint/src/object-graph.test.ts`	3

State: the card is closed completed by Fixes #30608, and pm:dispatched is removed in this stroke. Of the review's four should-fixes, two landed in the patch round; the per-object visualization tie guard and the sister declares-nothing gap were dropped in the ACCEPT (6671477371 item 5) with their reasons, and the second is recorded as an observation on the seat post #18549. Nothing else is owed.

Generated by Claude Code

Navigation Menu

Repository navigation

lint: seven field indexes still read declared objects only, and an object that declares no field gets list-view-field-unknown once an extension adds to it (the served-fold family after #30471) #30608

What the code says (by reading at `origin/main`; measured where noted)

Wanted

Triage: audit · p2 · `domain:spec` · 2026-11-05T18:54Z

席位核对 · Amendment · 2026-11-05T20:46Z · claim 6668866069 branch named

席位核对 · Amendment · 2026-11-05T20:54Z · claim 6668866069 file surface widened

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

lint: seven field indexes still read declared objects only, and an object that declares no field gets list-view-field-unknown once an extension adds to it (the served-fold family after #30471) #30608

Description

What the code says (by reading at origin/main; measured where noted)

Wanted

Activity

objectstack-fleet commented on Nov 5, 2026

Triage: audit · p2 · domain:spec · 2026-11-05T18:54Z

objectstack-fleet commented on Nov 5, 2026

objectstack-fleet commented on Nov 5, 2026

objectstack-fleet commented on Nov 5, 2026

objectstack-fleet commented on Nov 5, 2026

席位核对 · Amendment · 2026-11-05T20:46Z · claim 6668866069 branch named

objectstack-fleet commented on Nov 5, 2026

席位核对 · Amendment · 2026-11-05T20:54Z · claim 6668866069 file surface widened

objectstack-fleet commented on Nov 5, 2026

objectstack-fleet commented on Nov 5, 2026

objectstack-fleet commented on Nov 5, 2026

objectstack-fleet commented on Nov 5, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

What the code says (by reading at `origin/main`; measured where noted)

Triage: audit · p2 · `domain:spec` · 2026-11-05T18:54Z