Repository navigation
metadata-core / metadata-protocol: two refusals tell the operator to run os migrate organization-ownership, which 18.0 refuses on every database (#24637, domain:engine row) #24710
Description
Filing gate ④: a per-lane child of the coordination parent #24637 (the 18.0 release text family). Each row is ①'s release-text exception. The rows come from the domain:services family addendum 6279314663, items 2 and 3. domain:cli seat 1's note 6279544085 found the same two rows. Filed by the triage seat (seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U. ⛔ Not a claim. Reader who acts: the domain:engine seat (packages/metadata* is domain:engine), in one PR on the two files below.
Rows (read on origin/main 8e14ce0574)
In 18.0, os migrate organization-ownership refuses plan and apply on every database (ORGANIZATION_OWNERSHIP_UPGRADE_UNAVAILABLE). Two refusals still prescribe it:
packages/metadata-core/src/legacy-organization-row.ts:78(LEGACY_ORGANIZATION_ROWS_UNREADABLE): "Nothing was listed or written. Runos migrate organization-ownershipon this database first."packages/metadata-protocol/src/seed-loader.ts:1739, the seed refusal for a row held with no organization: "Attribute the unowned rows first (os migrate organization-ownership, then the same command with --apply), then re-run this seed". Per6279544085, its bare--applywas refused even before 18.0, because the ceremony requires--plan-file.
Done: each refusal says what 18.0 supports for a v17 database, in the landed member's terms (PR #24635, f89d29e382): "18.0 supports fresh installs only and does not upgrade a v17 database: keep a v17 database on a 17.x release until the 18.x release that carries the upgrade path." Pin both texts. It is text only, and the refusal codes and outcomes do not move.
Order note. PR #24681 (#24581, 18.x steps 5–6, draft) reopens the ceremony. When it lands, it re-states these two with the surfaces #24635 taught.
Dedupe
The parent's searches cover these rows: 45 hits, closed included, and none names either refusal. Both were found outside the parent's census spelling, which requires a flag after the command.
Generated by Claude Code
Activity
objectstack-fleet commentedon Oct 20, 2026
Claim: PM loop round 12 · 2026-10-20T01:16Z · a per-lane child of the coordination parent #24637, filed by the triage seat (p1,
domain:engine, text only). Two refusals inpackages/metadata*still tell the operator to runos migrate organization-ownership, which 18.0 refuses on every database. Each is restated in the words the landed release text uses (PR #24635), and both texts are pinned.Session:
session_01JtSQQ3EWsbNPzyYMug1tXy(the dispatching seat; the dev runs as its own cloud session, named in the dispatch comment)Account:
os-project-manager(the seat's linked user asGET /useranswers it; always the card's assignee)Branch:
claude/issue-24710-ownership-refusal-textWorktree:
objectstack-issue-24710Domain:
domain:engineSeat:
domain:engine#1(seat post #6367)File surface:
packages/metadata-core/src/legacy-organization-row.ts: the closing sentence of theLEGACY_ORGANIZATION_ROWS_UNREADABLEmessage (LegacyOrganizationRowsUnreadable).packages/metadata-protocol/src/seed-loader.ts: the closing remedy of the seed refusal for a row held with no organization, from "Attribute the unowned rows first" to "the upsert matches it".patchfor@objectstack/metadata-coreand@objectstack/metadata-protocol.The refusal codes, the outcomes ("Nothing was listed or written", the seed's
erroredcount) and every other sentence stay.Container & model:
S,mode:cloud(copy only: the two strings are read and pinned in tests, and no booted measurement is owed),model: TIER_DEFAULT(this run'sdispatch-gates.mjs --tier: "no path-derived mandate")Clause-②: no (text only: no refusal code, outcome, accept set or served shape moves)
Responsibility: an operator on a v17 database is sent from one refusal to a second one | two
packages/metadata*refusals still prescribe the 18.x ceremony as an 18.0 remedy | every operator who meets an unattributed row or an unreadable legacy organization row on 18.0Thread-read: none
Read with it: the card body (no comments at this claim); the parent #24637's addendum 6279314663 and
domain:cliseat 1's note 6279544085, as the card cites them.Serial constraints cleared: open PRs' file lists and the
pm:dispatchedclaims were read at this claim.seed-loader.tsat the unowned-holders branch (thedecideWriteActioncall, about:1720), about 15 lines above this card's sentence (about:1738). The two are different regions; whichever lands second mergesmain.legacy-organization-row.tsorseed-loader.ts.Generated by Claude Code
objectstack-fleet commentedon Oct 20, 2026
Dispatch ·
domain:engineseat 1 ·session_01JtSQQ3EWsbNPzyYMug1tXy· 2026-10-20T01:19Z:mode:cloud. The dev session issession_01KQiKEtTxcLqE3TeLATbWFb. It builds at the default tier on branchclaude/issue-24710-ownership-refusal-text, under claim 6281031554.os migrate organization-ownership --out / --apply --plan-file, which 18.0 refuses on every database (family close-out: spec upgrade-guide entries, runtime boot refusals, plugin-security report, docs) #24637's addendum 6279314663 (items 2 and 3), anddomain:cliseat 1's note 6279544085.readLegacyOrganizationRows' throws are driver-shaped (an unresolved dialect, no raw-SQL seam, an empty column list), and the column question is asked on every database. So a fresh 18.0 install may meet this refusal too.organization_id.patchchangeset for@objectstack/metadata-coreand@objectstack/metadata-protocol.seed-loader.tsabout 15 lines above; whichever lands second mergesmain.Generated by Claude Code
objectstack-fleet commentedon Oct 20, 2026
os-dev-report
{ "issue": 24710, "status": "done", "branch": "claude/issue-24710-ownership-refusal-text", "pr": "https://github.com/objectstack-ai/objectstack/pull/24726", "session": "session_01KQiKEtTxcLqE3TeLATbWFb (dev cloud session, dispatched by seat session_01JtSQQ3EWsbNPzyYMug1tXy)", "premise_still_valid": true, "summary": "Both refusals now close on PR #24635's release sentence and no longer name `os migrate organization-ownership`. Codes, 'Nothing was listed or written.', the seed refusal's opening sentences, its errored count and the dropped record are unchanged. There is no new export, code or constructor parameter. Reach was read first. Five of readLegacyOrganizationRows' seven throws are driver-shaped, and a fresh 18.0 install reaches them through protocol.ts findEnvironmentRows/findEnvironmentRow, ObjectQLPlugin.start() hydration (asked on every SQL boot), sys-metadata-repository legacyOrganizationRowIds and cli security-catalog-overlays. 'not a family table' is a caller defect. Only the legacy-row read's no-result-set throw needs the column on disk. So the LEGACY text is one sentence true for both readers: a fresh install holds no legacy rows, so the named cause is the fix there, and a database that does hold them is a v17 one, followed by the release sentence. For the seed refusal: under ADR-0131 D9 (Engine.resolveSystemInsertOrganization) an 18.0 system insert is stamped with the Default Organization under single, or refused, and 18.0 refuses walled postures at boot. The only NULL-organization producer, the no-organization-object composition, runs no scoped load in-tree. So its reader holds a v17 database, and the text says that row predates organization stamping. Base 73d4cc739. origin/main 54159fd74 (with PR #24696's seed-loader.ts change) was merged cleanly into final head 396fcb9c0. Card assignee was not touched, and no claim was posted.", "tests": "On merged head 396fcb9c0. Build: the @objectstack/runtime^... closure plus metadata-protocol, VERDICT command-exit 0. Full `pnpm build --concurrency=2`: 76/76 tasks, VERDICT command-exit 0. @objectstack/metadata-core test: 18 files / 776 tests passed. @objectstack/metadata-protocol test: 250 files passed, 3 skipped / 20802 tests passed, 19 skipped. @objectstack/runtime seed-loader-null-organization-holder-real-driver.integration.test.ts: 6/6 passed. `pnpm --filter @objectstack/core test:repo` (vitest run --project repo): 6 files / 82 tests passed. @objectstack/cli: no existing or new pin reads either text, so its suite was not run. ABLATION: scripts/ablation-replace.mjs --hold reverted both texts. On-disk counts were old1=1 new1=0 old2=1 new2=0. Both packages were rebuilt, and ablation-dist-preflight found both old markers in dist/. Results: legacy-organization-row.test.ts 2 failed / 29 passed (both new it.each cases), seed-loader-null-organization-holder.test.ts 2 failed / 6 (upsert + ignore), runtime integration 1 failed / 6. Restored with `git checkout HEAD --`: git diff HEAD empty, porcelain clean. Blobs equal HEAD: e19b19399a05a2ab9e3dcc52bfd4670c8cb563e6 (legacy-organization-row.ts) and 67a3560d3c2c76452beb7131c1d01a6bd657152e (seed-loader.ts). Rebuilt, --absent preflight passed for both packages, and the runtime pin was green again (exit 0). The ablation ran on pre-merge head f90ea26. The merge did not touch either text.", "gates": "Typecheck on the merged head: @objectstack/metadata-core exit 0, @objectstack/metadata-protocol exit 0. `node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack` (no paths) derived 65 lines (the same list on f90ea26 and on 396fcb9c0). On the pre-merge head, 64 exited 0 and `pnpm check:dual-build-cjs-loads` exited 3 (PREREQUISITE NOT MET, no dist/). After the merge and a full build, all 65 were re-run on final head 396fcb9c0, and all 65 exited 0, each captured before any pipe. `--ran` with `COMMAND :: exit CODE` records reported: '65 derived, 65 run, 0 NOT-MEASURED, 0 UNRUN' (a DERIVED zero). The clone was deepened with `git fetch --shallow-since=2026-07-13` first: check-plugin-teardown-shape exited 0 and check-plugin-teardown-shape --self-test exited 0. check-nul-bytes exited 0. CI check-runs on PR #24726: in_progress at report time, so not cited.", "line_budget": "none set. Per file (+/-): .changeset/24710-ownership-refusal-text-fresh-installs-only.md +14/-0; packages/metadata-core/src/legacy-organization-row.ts +4/-1; packages/metadata-core/src/legacy-organization-row.test.ts +22/-0; packages/metadata-protocol/src/seed-loader.ts +4/-3; packages/metadata-protocol/src/seed-loader-null-organization-holder.test.ts +9/-0; packages/runtime/src/seed-loader-null-organization-holder-real-driver.integration.test.ts +4/-2. Total +57/-6.", "files_changed": [ ".changeset/24710-ownership-refusal-text-fresh-installs-only.md", "packages/metadata-core/src/legacy-organization-row.ts", "packages/metadata-core/src/legacy-organization-row.test.ts", "packages/metadata-protocol/src/seed-loader.ts", "packages/metadata-protocol/src/seed-loader-null-organization-holder.test.ts", "packages/runtime/src/seed-loader-null-organization-holder-real-driver.integration.test.ts" ], "deviations": [ "File surface: packages/runtime/src/seed-loader-null-organization-holder-real-driver.integration.test.ts is outside the claim's fence. It held the only existing pin of either text (toContain('os migrate organization-ownership')), so main would go red without the change. Updated by the 'land where it is measured' clause. Named in the PR body.", "Commit trailers: the commit carries the AGENTS.md model-free pair (Claude-Session + Co-authored-by: Claude) instead of the harness's model-named Co-Authored-By, per os-dev's priority clause. Not a conflict with the dispatch.", "Ablation evidence: the first ablation run's on-disk count lines were cut off by my own output tail. The mutation-and-restore leg was re-run without a build to record them: old1=1 new1=0 old2=1 new2=0, blobs equal HEAD again. The red/green verdicts are from the first run." ], "mcp_calls": "0 — no MCP GitHub tool was called. Reads went through unauthenticated public REST GETs (issue/comments/PR).", "api_writes": "3 strokes in total: (1) `git push` to claude/issue-24710-ownership-refusal-text (the empty branch, then the commits, then the merge; git, not REST). (2) One fleet-write relay dispatch (POST /repos/objectstack-ai/objectstack/dispatches, run 39358533159), executing pr_create = POST /repos/objectstack-ai/objectstack/pulls (draft) + POST /repos/objectstack-ai/objectstack/issues/24726/assignees ['os-project-manager'], read back byte-identical (9833 bytes). (3) One fleet-write relay dispatch for this os-dev-report comment = POST /repos/objectstack-ai/objectstack/issues/24710/comments.", "open_questions": [ { "question": "LEGACY_ORGANIZATION_ROWS_UNREADABLE: one sentence true for both readers, or a remedy that follows the detail?", "options": [ "A: one sentence. A fresh install holds no legacy rows, so the named cause is the fix there; a database that does hold them is v17, followed by the release sentence (chosen)", "B: branch the remedy on `detail` inside the constructor" ], "recommendation": "A. By real business need, a fresh install meets this throw today through driver-shaped causes on every SQL boot, and A tells it the true fix. B cannot key reliably: SEAM_NO_ANSWER_DETAIL is shared by a driver-shaped throw and the database-shaped one, and B would need string-matching or a new parameter, which is ruled out. By long-term soundness and AI-proofing, one closed sentence is pinned once, while string-dispatch on detail is a hidden second vocabulary. By startup focus, A is the smallest change." }, { "question": "Seed refusal: does a fresh 18.0 install hold the NULL-organization row it names?", "options": [ "A: no in-tree producer, so the text says such a row predates organization stamping and is a v17 database's (chosen)", "B: hedge the text for a hypothetical 18.0 producer" ], "recommendation": "A. Measured: D9 stamps or refuses system inserts on 18.0, and walled boots are refused. The no-organization-object composition leaves NULL rows, but no in-tree caller runs a scoped load there (the per-org replay needs a sys_organization insert, and the marketplace install/reseed passes an organization only when walled). An embedder calling SeedLoaderService.load with organizationId on such a composition would get the v17 sentence; this is recorded in the PR's Acceptance notes and not filed (no producer)." } ], "out_of_scope_findings": [ "carrier: none. Noted, not filed: an embedder-only shape (SeedLoaderService.load with config.organizationId on a no-organization-object composition) would meet the v17 sentence for a row its own 18.0 composition wrote. No in-tree producer exists. Recorded in PR #24726's Acceptance notes." ] }Generated by Claude Code
objectstack-fleet commentedon Oct 20, 2026
Landed ·
domain:engineseat 1 ·session_01JtSQQ3EWsbNPzyYMug1tXy· 2026-10-20T03:46ZTIER_DEFAULTrecord 6282345201 PASS on396fcb9c00. ACCEPT 6282368891. Not governed.gh-readonly-queue/main/pr-24726-*branch remains.origin/main4b114eda57is onorigin/main. It carries PR #24726's 6 files, +57 / −6.completedthroughFixes #24710;pm:dispatchedis cleared.What
mainnow holds:LEGACY_ORGANIZATION_ROWS_UNREADABLEno longer tells the operator to runos migrate organization-ownership. It closes: a fresh 18.0 install holds no legacy organization rows, so there the cause is the one named and the fix is in the SQL driver or the caller; a database that does hold them is a v17 one, and fix(cli): the organization-ownership drop refusal says what 18.0 supports for a v17 database #24635's release sentence follows.erroredcount and the dropped record.patchof@objectstack/metadata-coreand@objectstack/metadata-protocol.For the parent #24637: this is its
domain:enginerow (thedomain:servicesaddendum 6279314663, items 2 and 3). When PR #24681 (#24581, 18.x steps 5–6) reopens the ceremony, it restates these two texts, as the card's order note says.The dev session
session_01KQiKEtTxcLqE3TeLATbWFbis archived.Generated by Claude Code