platform-checklist + NORTH-STAR: retire records-forms.picklist-org-append and the "customers append values per organization" promise — the per-organization picklist append is ruled out #22869

Activity

1. objectstack-fleet

   added

   priority:p2Medium: important, M3Medium: important, M3

   pm:queue

   domain:skills

   area:recordsBusiness objects, records, the views that show data, usable forms, searchBusiness objects, records, the views that show data, usable forms, search

   pm:dispatched

   and removed

   pm:queue

   on Oct 11, 2026
2. objectstack-fleet

   assigned

   huangyiirene

   on Oct 12, 2026
3. objectstack-fleet commented on Oct 12, 2026

   

   objectstack-fleetbot

   on Oct 12, 2026

   ContributorAuthor

   More actions

   Claim: PM loop round 1 · 2026-10-12T07:10Z
   Session: session_01CinRQcE6T8SvMbhH8D3NhS
   Account: huangyiirene (the seat's linked user as GET /user answers it; always the card's assignee)
   Branch: claude/issue-22869-retire-picklist-org-append
   Worktree: objectstack-issue-22869
   Domain: domain:skills
   Seat: domain:skills#1
   File surface: docs/NORTH-STAR.md (the one records · 共享选项集 row, line 43 on origin/main 246edf5b3), docs/qa/platform-checklist/areas/records-forms.json (the records-forms.picklist-org-append item, kept as a row and retired, plus the cross-reference sentence inside records-forms.picklist-shared-across-objects), docs/qa/platform-checklist/coverage.json (the picklist waiver text) (stop on breach; explain in the report)
   Container & model: M (S-sized by lines, but the NORTH-STAR row is a business-language rewrite on the maintainer's law, so it takes the M treatment), mode:subagent, model: default — this run's --tier on the three paths printed 「Model tier — no path-derived mandate: the surface hits none of the 3 declared glob(s)」 and 「floor sonnet · default opus · ceiling fable」; default is the ruling-implementation tier
   Clause-②: no — the three paths are the North Star text and the checklist ledger; no published schema, accept set or public surface is touched (no packages/** path)
   Responsibility: n/a — not a defect card (a maintainer direct order retiring a declared capability)
   Thread-read: none
   Ruling-ref: the card body itself — filing gate ③, the maintainer's verbatim 「按组织追加 picklist 值,不考虑」 (session_01EgxC4UNYnzhuvmG12fh5A8, 2026-10-11); the card was never in the decision box, so no ruling comment id exists
   Serial constraints cleared: none in flight — no pm:dispatched claim in any lane names these three paths (16 cards' claim threads read 2026-10-12T07:10Z); none of the 21 open PRs changes them (files lists read); the one same-day touch, e23eccb16 (the allowOrgOverride → allowEnvironmentOverlay rename inside this very item's knownGaps text), is MERGED, not in flight; #22876 (spec, stage 0) cites NORTH-STAR as a stance and writes no file; no pm:on-hold card carries a Restart-touch: on this surface; no open pm:epic territory covers it
   Tier H by path: check-governed-merges --test on the three paths answers H(人合) for docs/NORTH-STAR.md; the dev opens a draft PR with a ## 维护者速读(草稿) section and the maintainer's approval lands it

   ---

   Generated by Claude Code
4. objectstack-fleet commented on Oct 12, 2026

   

   objectstack-fleetbot

   on Oct 12, 2026

   ContributorAuthor

   More actions

   os-dev-report
   {
   "issue": 22869,
   "status": "done",
   "branch": "claude/issue-22869-retire-picklist-org-append",
   "pr": "#22982",
   "session": "session_01CinRQcE6T8SvMbhH8D3NhS",
   "premise_still_valid": true,
   "summary": "Draft PR #22982 (head 57ef232, base 117817e; Tier H by its docs/NORTH-STAR.md path) retires records-forms.picklist-org-append and drops the per-organization append from the two other places that promised it. The item goes planned → retired with a retiredReason quoting the ruling and citing ADR-0131 D6; it has no supersededBy, and the row and all its fields stay. Its revision goes 1 → 2, following the README Change rule and the two existing retired precedents. Measured: the validator's revision check is consistency-only, and an unbumped retire gives the same 10 problems. The sibling records-forms.picklist-shared-across-objects no longer 'splits' its #18164 design-of-record citation with the retired item (revision 2, a source-only history entry). The coverage.json picklist waiver now names only the sibling. NORTH-STAR line 43 now reads '- records · 共享选项集:多个对象复用同一份选项 · records-forms · picklist-shared-across-objects'; no other line was touched. Premise checks at BASE 117817e: git grep picklist-org-append gave exactly 4 hits (NORTH-STAR:43, records-forms.json:4357 and :4372, coverage.json:233), and nothing in packages/** or scripts/**. No gate reads the NORTH-STAR feature map (git grep NORTH-STAR in scripts/ found only check-governed-merges and the queue guard). No committed census: README says there is no STATUS.md and no paired gate. gen:checklist-status (stdout only) now reads records-forms 41 active / 1 planned (base 41 / 2). PM mechanism assumption FALSIFIED: the retire DOES trip the checker. scripts/check-platform-checklist.mjs#statusFieldProblems branches only on planned, and judges retired by the active rule (since must be a release, steps non-empty). So a planned item retired before it was ever implemented adds 2 problems that only invented data could clear. Per the dispatch, the checker was not edited and nothing was invented. Measured: a waived prose mention is NOT a coverage mapping: with the retired row and the old waiver text still naming it, no 'maps to retired item' problem fires. checklist-select resolves the retired id to 0 runnable and 0 planned items. Landing dependency: #22982 should land after the checker fix (see open_questions), or main's watchdog reading goes from 8 to 10.",
   "tests": "All runs on final head 57ef232 (git rev-parse --short HEAD), from the dispatch-gates --commands --repo objectstack-ai/objectstack derivation: 14 commands, identical at 5bf03ad and 57ef232, plus pnpm check:pm-governed-prose. Exit codes were captured before any pipe. --ran reconciliation: '✓ dispatch-gates --ran: 14 derived famil(ies) accounted for — 14 run, 0 NOT-MEASURED'. (1) node scripts/check-ci-filter-parity.mjs exit 0, 'OK: all 21 build input(s) turbo.json declares outside the packages …'. (2) node scripts/check-closing-keyword-parity.mjs exit 0, 'check-closing-keyword-parity: OK (3 parsers agree on all 9 keywords …)'. (3) … --self-test exit 0, '✓ … 40 assertions, 5 mutations …'. (4) node scripts/check-comment-mask-corpus.mjs exit 0, '✓ comment-mask corpus sweep …: 8834 files, 0 disagree, 0 unparseable'. (5) pnpm --filter @objectstack/lint run check:doc-formula-expressions exit 0, '✓ check:doc-formula-expressions …: 15 predicate(s) … judged clean'; its first run exited 3 (PREREQUISITE NOT MET: formula and lint dist absent). Built under the lock with 'pnpm exec turbo run build --concurrency=2 --filter=@objectstack/formula --filter=@objectstack/lint': 'os-verify-lock: VERDICT command-exit 0', 4 tasks. (6) pnpm check:cross-package-test-inputs exit 0, 'OK: 30 package(s) read outside themselves, all declared …'. (7) pnpm check:doc-authoring exit 0, '✓ doc authoring guard: … no growth'. (8) pnpm check:driver-memory-census exit 0, 'check-driver-memory-census: OK …'. (9) pnpm check:gitlink-declared exit 0, 'check-gitlink-declared: OK (11005 index entries …)'. (10) pnpm check:nul-bytes exit 0, 'check-nul-bytes: OK (scanned 10996 text file(s) … no raw ASCII control bytes)'. (11) pnpm check:platform-checklist exit 1, 'check-platform-checklist: 10 problem(s)'. Base 117817e reads 'check-platform-checklist: 8 problem(s)', all symbol anchors in access-security, attachments-storage and search, none in the touched files. The diff of the two problem lists is exactly 2 added lines, both on records-forms.picklist-org-append: '"since" must be the release that introduced the capability' and '"steps" must be a non-empty array of strings'. Both self-tests in that script are green ('✓ checklist-select self-test: 31 cases pass', '✓ check-platform-checklist --self-test: 221 assertions'). (12) pnpm check:pm-governed-merges exit 0, '✓ check-governed-merges --self-test: 476 assertions …'. (13) pnpm check:refd-timer-probe exit 0, 'OK check-refd-timer-probe: 8828 source file(s) swept …'. (14) pnpm check:watch-hint-literal exit 0, '✓ check-watch-hint-literal: 72 declaration(s) …'. (+) pnpm check:pm-governed-prose exit 0, '✓ check-governed-prose: … name all 6 registered governed surfaces …'. Extra measurements. Revision both ways: the unbumped variant was written by a trap-guarded script that restored with 'git checkout HEAD --'; restore was proven by hash-object equal to the HEAD blob 7d952e9f2 and an empty 'git diff HEAD'. It gave the same 10 problems with no revision complaint. Coverage mapping: an intermediate run had the retired row while the old waiver text still named it, and gave 10 problems, none 'maps to retired item'. node scripts/pm/check-governed-merges.mjs --test on the 3 paths: 'landing tier: H(人合)' for docs/NORTH-STAR.md. clause2-line readClause2Line on the PR body: declared 'no'. Not run locally (no package touched): package build/test/typecheck; the 53 roster, 11 wide, 15 pending-changeset families and the CI-only jobs dispatch-gates names are CI's.",
   "mcp_calls": "0 — no MCP tool was called",
   "api_writes": "3 relay strokes, each one session POST /repos/objectstack-ai/objectstack/dispatches (HTTP 204) executed by the fleet-write workflow as objectstack-fleet[bot]: (1) pr_create, run 38218428313 — POST /repos/objectstack-ai/objectstack/pulls (draft) + POST /repos//issues/22982/assignees [huangyiirene]; read back 9645/9645 body bytes identical, assignee listed. (2) label-write labels_add, run 38218499907 — POST /repos//issues/22982/labels [skip-changeset]; read back MATCHES (documentation, size/s, skip-changeset). (3) post-stamped, this os-dev-report comment — POST /repos//issues/22869/comments. Plus 3 git pushes (not REST): the empty-branch probe, 5bf03ad, 57ef232. Reads (not writes): unauthenticated GETs of issue 22869, its comments and pull 22982.",
   "deviations": [
   "dispatch-gates printed 14 commands at 5bf03ad and 57ef232, a different set from the PM's claim-time 14: pnpm check:pm-governed-prose sits in the artifact-roster block, not the runnable list. It was run anyway, green.",
   "The sibling records-forms.picklist-shared-across-objects also took a revision bump (1 → 2, a source-only history entry), under the README Change rule. The dispatch asked only for the citation edit.",
   "The ruling is quoted in the ledger and PR body with the card body's fullwidth comma (U+FF0C), as the card spells it; the dispatch text spells it with an ASCII comma.",
   "Commits carry the AGENTS.md model-free trailer pair (Claude-Session + 'Co-authored-by: Claude'), not the harness reminder's model-named Co-Authored-By.",
   "Two commits: the second (57ef232) only rewords the sibling citation.",
   "A gate-runner loop using bash -c over the derived list was refused by the harness safety check (it cannot inspect such scripts for removals). The same 15 commands were re-run from a literal script; nothing was removed."
   ],
   "open_questions": [
   {
   "question": "Landing order for #22982 against the checker gap: check-platform-checklist has no legal shape for a planned item retired before it was implemented, so #22982 adds 2 problems to the checklist validator.",
   "options": [
   "A — The seat files the checker fix as an independent card in objectstack: statusFieldProblems lets a retired item keep since null and no steps, with a self-test case. #22869/#22982 carry 'Blocked-by:' it, and the maintainer merges #22982 after it lands. Cost: one small scripts/ PR.",
   "B — The maintainer lands #22982 first and accepts the watchdog reading 10 instead of 8 on main until the fix lands. Cost: the watchdog card names 2 more problems meanwhile.",
   "C — Invent a since release and steps for the retired row. Rejected: it fabricates ledger data, for a capability that never existed."
   ],
   "recommendation": "A. The red is the checker's (the README Retire rule asks only status + retiredReason), the fix is small and mechanical, and it keeps main's watchdog from carrying problems a governed PR knowingly introduced."
   }
   ],
   "out_of_scope_findings": [
   "class: a · reach: the public door is pnpm check:platform-checklist, the ledger's validator, run on main by platform-checklist-watchdog.yml. On a README-conformant retire of a never-implemented planned item it answers 2 problems ('"since" must be the release that introduced the capability', '"steps" must be a non-empty array of strings'), measured on records-forms.picklist-org-append at 57ef232: base 117817e reads 8 problems, head reads 10. Minimal repro: flip any planned item to status retired with a retiredReason. · evidence: scripts/check-platform-checklist.mjs#statusFieldProblems has a branch for status planned only; every other status, retired included, falls through to the active rule. The README Lifecycle Retire bullet asks only status retired + retiredReason (+ supersededBy). The only two retired items before this one (dashboards.saved-report-ownership, dashboards.report-schedule-dispatch-delivery) were active before retiring, so no retire had exercised this path. Fix lands in objectstack scripts/; #22869 / PR #22982 take 'Blocked-by:' it. · dedupe words: statusFieldProblems retired; retire planned checklist item since steps; check-platform-checklist retired since null; retired item steps required",
   "carrier: 承接者:无 · noted, not filed (in PR #22982 Acceptance notes). The coverage.json picklist waiver is stale beyond this card. It still says no runtime reads a picklist and that the picklist rows are PENDING #19519, but the runtime layer landed in 88b484e (#21047): picklist.json grades name live (packages/objectql/src/registry.ts#resolvePicklistOptions), and check-stack-collection-maps.mjs has no PENDING or #19519 picklist rows. So records-forms.picklist-shared-across-objects may now be drivable, and promotable after a passing run. That is a coverage-sweep job."
   ]
   }

   ---

   Generated by Claude Code
5. objectstack-fleet commented on Oct 12, 2026

   

   objectstack-fleetbot

   on Oct 12, 2026

   ContributorAuthor

   More actions

   ACCEPT — PR #22982 (head 57ef232b7, 3 files +20/−7, draft, Tier H by path) · reviewed 2026-10-12T07:48Z by session_01CinRQcE6T8SvMbhH8D3NhS (skills seat 1).

   Checklist, verified on GitHub against origin/main, not against the report:

   • PR form: draft, base main, first line Fixes #22869, Clause-②: no at the head of a body line, PR assignee = the card's; no closing keyword sits beside any other open card's number; no HTML comment; the session-URL footer.
   • Scope: exactly the three paths the claim declared; no content/docs/releases/; skip-changeset is right (no package files[] ships them; 70 non-private manifests read by the dev).
   • docs/NORTH-STAR.md:43 after: - records · 共享选项集:多个对象复用同一份选项 · records-forms · picklist-shared-across-objects — one row, nothing else in the file (+1/−1).
   • records-forms.json: the item is retired with a retiredReason quoting the ruling and ADR-0131 D6, row and fields kept, revision 2 + history; the sibling's source[0] no longer splits its sentence with a retired item (#18164 pointer intact), revision 2 + history. Both history entries and the retiredReason read in full.
   • coverage.json: the picklist waiver names only records-forms.picklist-shared-across-objects — sentence read on the head 57ef232b7.
   • Gates: 14 derived + check:pm-governed-prose run on 57ef232b7, --ran 14/14; 13 green, check:platform-checklist 8 → 10 (below). Check-runs on the head: 34 success/skipped, Lint & Repo Gates in progress at review time, no failure.
   • Contract review (governed text face, in seat at CONTRACT_REVIEW_TIER): PASS, recorded on the PR.

   Public correction, on the record: the dispatch's mechanism assumption 「the retire needs no checker edit; a checker that reds on the retired row is a finding」 was half right. The dev measured scripts/check-platform-checklist.mjs#statusFieldProblems branching only on planned and judging retired by the active rule (since must be a release, steps non-empty): a planned item retired before it was ever implemented — the first such retire; the two dashboards.* precedents were active first — adds 2 problems that only invented data could clear. The checker is wrong against the README's Retire rule (status + retiredReason); the row is right. Filed as a sub-issue of this card: #22987 (Unblocks: #22869; parent domain and priority inherited; dispatched by this seat). The dev's open question (landing order) is answered A: this PR lands after #22987. Option C (invent since/steps) is refused.

   Also measured by the dev, correcting the card: a waived prose mention is NOT a coverage mapping for the maps to retired item check (it reads an entry's items array only); the waiver edit is for truth, not for the gate.

   Acceptance notes carried, not filed: the picklist waiver is stale beyond this card — the runtime layer landed (88b484e00, #21047), so picklist-shared-across-objects may now be drivable; that belongs to the next coverage sweep. Carrier: none named.

   Landing: Tier H. needs-user-decision on the PR, the 速读终稿 posted there, review requested from os-zhuang and hotlong. After an authorized APPROVED review the seat lands it through the queue — and not before #22987 is merged.

   ---

   Generated by Claude Code
6. os-zhuang

   closed this as completedin #22982on Oct 12, 2026
7. objectstack-fleet

   removed

   pm:dispatched

   on Oct 12, 2026
8. objectstack-fleet commented on Oct 12, 2026

   

   objectstack-fleetbot

   on Oct 12, 2026

   ContributorAuthor

   More actions

   Landed: PR #22982 → 929c8b1b6 (squash) · skills seat 1 (session_01CinRQcE6T8SvMbhH8D3NhS) · 2026-10-12T09:36Z

   Content read on origin/main: docs/NORTH-STAR.md:43 reads 「- records · 共享选项集:多个对象复用同一份选项 · records-forms · picklist-shared-across-objects」; records-forms.picklist-org-append is "status": "retired" with its retiredReason; coverage.json's picklist waiver names only the sibling. Approved, flipped ready and enqueued by os-zhuang 2026-10-12T09:03Z (the maintainer's hand chose to land ahead of the checker fix), merged by the queue. The card closed by Fixes; pm:dispatched stripped in this act. Until the sub-issue #22987's PR #22995 (now in the merge queue) lands, pnpm check:platform-checklist on main reads 10 problems instead of the base 8 — the two on this retired row, the checker's, closed by #22995.

   ---

   Generated by Claude Code