Repository navigation
cloud-connection: bind/start, bind/poll and unbind admit any signed-in user (no Setup Access check), and GET /status serves the approving account's email and organization id to anonymous callers #24148
Description
Filing gate: ① a product defect, filed under the exception for a defect that may leak data, with reach measured first. Filed by domain:devx seat 2 (#20163) · os-sales · session_016PVjjuVPte5XEJvaQx1E4t, from the out-of-scope findings of #24066 (PR #24147).
- Reader: the
domain:cliseat, inpackages/cloud-connection/src/cloud-connection-plugin.ts, at thestatus,bind/start,bind/pollandunbindhandlers. - Dedupe:
search_issueson objectstack-ai/objectstack for "cloud-connection unbind bind permission any signed-in user setup access status anonymous account_email" gave 1 hit, cloud-connection: the marketplace-install route supplies notenancyPosturetoresolveAuthzContext— an ex-member's org-stamped API key is admitted #15353 (closed), which covers the install route's tenancy posture and not these four routes. None of the opencloud-connectioncards (cloud-connection: the marketplace reseed door handsapplySideEffectsthe raw ledger entry, so it reloads translations a conversion strips (a pre-17.4 per-appsettingsgroup) that install and rehydrate load converted #24040, cloud-connection: the "Installed Apps" entry opens Setup Packages filtered to Source = marketplace (ruling B on #23892; after the objectui card lands and the pin moves) #23933) covers them either.
Reach
Measured by the #24066 dev on a dev boot of examples/app-showcase at main 9ffe8af09, against a stand-in control plane. Detail withheld pending maintainer. The maintainer's disclosure ruling (2026-08-18, recorded on #9387) says no reproduction for an authentication or authorization hole is published anywhere on GitHub. The reproduction stays with the filing seat and the dev's session. Redacted by the triage seat (session_01AavokzJ5DndAwitDXvKy4U).
Why
resolveSessionreturns only the session's user, and the three write handlers check only that a session exists. The/installhandler's comment says the same thing: "TODO: tighten to an explicit env-admin role check".- The console's Cloud Connection panel sits on the Setup page, which
setup.accessgates. The routes behind it are not gated the same way. - The
statushandler is session-less on purpose (.changeset/pre/23190-auth-gate-cli-sites.md), so that a probe can tell whether the plugin is mounted. But it passes the control plane'sdata.connectionthrough verbatim, so the approving account's email and the organization id reach anyone.
Done when
bind/start,bind/pollandunbindrefuse a signed-in caller who lacks the permission that gates the Cloud Connection page (setup.access, or an explicit environment-admin check if the seat rules that the better fit), with a 403 whose code names it.- An anonymous or unprivileged
GET /statusanswers at mostbound,runtimeIdandprovider. Theconnectiondetails (account_email,organization_id, name) are served only to a caller who passes the same check. The objectui panel's "Approved by" row keeps working for an admin. - Tests pin each refusal and the narrowed anonymous status, and an ablation shows each test fails without its check.
- The same PR updates
content/docs/deployment/cloud-connection.mdx(docs: no page tells a self-hosted operator how to connect their ObjectOS server to ObjectStack Cloud (Setup → Cloud Connection → Connect, then approve in the cloud account) #24066): the#before-you-startsentence about which caller may connect, and the#referencetable'sstatusrow.
Generated by Claude Code
Activity
objectstack-fleet commentedon Oct 17, 2026
Triage: first grade,
priority:p1·target:v18·area:access·pm:queue· the filer'ssecurity·domain:clistand · body redacted · triage seat ·session_01AavokzJ5DndAwitDXvKy4U· 2026-10-17T05:04ZTriage seat (objectstack-wide, seat post #6015). ⛔ Not a claim, ⛔ not a dispatch.
6229784606) carried a reproduction for an authorization hole. The maintainer's disclosure ruling (2026-08-18, skills: five principle gaps the #9296 wave exposed in checklist-test / checklist-author / dogfood-verification #9387) forbids that anywhere on GitHub. Existence stays published; the recipe is withheld pending the maintainer. Earlier revisions remain in the edit history, and only a repository admin can delete them.target:v18: a signed-in caller without the Setup permission can change the server's cloud connection, and an anonymous read returns the approving account's details. It is a permission boundary, and 18.0 cannot ship with it.origin/main:packages/cloud-connection/src/cloud-connection-plugin.tsgates the three write handlers onresolveSessionalone, and/installstill says "TODO: tighten to an explicit env-admin role check".setup.access), or an explicit environment-admin check if the seat rules that the better fit. Each refusal is an ablated pin. Anonymousstatusnarrows tobound/runtimeId/provider. Because this is a permission boundary, the PR gets security review before landing.Generated by Claude Code
objectstack-fleet commentedon Oct 17, 2026
Claim: PM loop round 1, serial, p1/p2 only (the maintainer to this seat, verbatim 「串行派发，只处理 p1 p2」; #24131's PR #24161 waits only in the merge queue, and #24137 went to the decision box at
6231683182). Label order read in this act: #24148 is the nexttarget:v18p1 bug. #24148: the cloud-connection write routes refuse a signed-in caller withoutsetup.access, and an anonymous or unprivilegedGET /statusanswers onlybound,runtimeIdandprovider· 2026-10-17T08:25ZSession:
session_01BVm1pAXVXQ3PjC42j1kPFfAccount:
os-sales(the seat's linked user asGET /useranswers it; always the card's assignee)Branch:
claude/issue-24148-cloud-connection-setup-gateWorktree:
objectstack-issue-24148Domain:
domain:cliSeat:
domain:cli#1(seat post #6024)File surface (read on
origin/main52c04b360; line numbers move; stop on a breach and explain it in the report):packages/cloud-connection/src/cloud-connection-plugin.ts: thestatus,bind/start,bind/pollandunbindhandlers only, and the shared session read they use (resolveSession, about:250).packages/cloud-connection/src/. One.changeset/24148-*.md.content/docs/deployment/cloud-connection.mdx: the#before-you-startsentence about which caller may connect, and the#referencetable'sstatusrow (the card's done-condition)./installhandler (its posture was ruled on cloud-connection: the marketplace-install route supplies notenancyPosturetoresolveAuthzContext— an ex-member's org-stamped API key is admitted #15353; itsTODO: tightenis reported, not changed here); theinstall-localdoor; objectui's panel; everypackages/specedit (thedomain:specseat's); the auth gate that keepsstatussession-less on purpose (.changeset/pre/23190-auth-gate-cli-sites.md).Container & model:
M(four handlers on one permission boundary, plus a narrowed anonymous read),mode:subagent,model: TIER_DEFAULT(dispatch-gates --tier: no path-derived mandate)Clause-②: no
Basis for the Clause-② line: a NARROWING. Signed-in callers without
setup.accesslose three write routes they reached before, and anonymousGET /statusloses theconnectiondetails. Nothing refused becomes accepted. It carriesClause-②: no (narrowing)line-initial in the PR body and the changeset, and the PR owes oneCONTRACT_REVIEW_TIERreview of record before the queue. That review doubles as the security review triage requires before landing (6229951531).Responsibility:
packages/cloud-connection's cloud-connection routes (this lane) |setup.accessalready gates the Setup app the console's Cloud Connection panel sits on (packages/platform-objects/src/apps/setup.app.ts:47), but the routes behind the panel check only that a session exists | any signed-in user of the environment, for the three write routes, and anyone at all, forstatus'sconnectiondetails; the existence is measured by the docs: no page tells a self-hosted operator how to connect their ObjectOS server to ObjectStack Cloud (Setup → Cloud Connection → Connect, then approve in the cloud account) #24066 dev and the detail is withheld under the maintainer's disclosure ruling (skills: five principle gaps the #9296 wave exposed in checklist-test / checklist-author / dogfood-verification #9387)Thread-read: 6229951531
Serial constraints cleared: the 4 open PRs read in this act; none edits
packages/cloud-connection/. No openpm:dispatchedclaim declares those files. cloud-connection: the marketplace reseed door handsapplySideEffectsthe raw ledger entry, so it reloads translations a conversion strips (a pre-17.4 per-appsettingsgroup) that install and rehydrate load converted #24040 (p2target:v18) and cloud-connection: the "Installed Apps" entry opens Setup Packages filtered to Source = marketplace (ruling B on #23892; after the objectui card lands and the pin moves) #23933 (p2) are the lane's other cloud-connection cards, inpm:queueand not in flight.cloud-connection.mdxcame with docs(deployment): Cloud Connection operator page — connect a self-hosted server to ObjectStack Cloud #24147 (PR, merged as2889760a5).The seat's ruling on the one choice triage left it
Triage: "the check is the permission that gates the Cloud Connection page (
setup.access), or an explicit environment-admin check if the seat rules that the better fit" (6229951531). Ruled:setup.access. The console's panel sits on the Setup app, which declaresrequiredPermissions: ['setup.access'](packages/platform-objects/src/apps/setup.app.ts:47). Gating the routes on the same permission means the API refuses exactly who the page refuses, and no new role concept is introduced. The check goes through the platform's existing server-side permission read, ⛔ not a re-spelled one. The refusal is a403whose code names it.⛔ Disclosure (the maintainer's ruling of 2026-08-18, recorded on #9387, carried by triage): no reproduction appears in the PR body, the report, or any comment. Existence and the pins only.
objectstack-fleet commentedon Oct 17, 2026
os-dev-report
{
"issue": 24148,
"status": "done",
"branch": "claude/issue-24148-cloud-connection-setup-gate",
"pr": "#24167",
"session": "session_01BVm1pAXVXQ3PjC42j1kPFf — this run's harness-stamped id (subagent = parent's)",
"premise_still_valid": true,
"summary": "Claim verified first: the newest Claim (6231718544) names branch claude/issue-24148-cloud-connection-setup-gate, and no own claim was posted. In packages/cloud-connection/src/cloud-connection-plugin.ts, bind/start, bind/poll and unbind now refuse a signed-in caller without setup.access with 403 PERMISSION_DENIED. That is the standard-catalog member, so nothing was minted and packages/spec is untouched. The message names the capability, and the refusal comes after the existing 401 / ADR-0069 403 and before any control-plane call or credential touch. GET /status still answers every caller 200 and never refuses. It serves only bound/runtimeId/provider unless the caller holds setup.access; a holder also gets environmentId and connection. On a permission-store outage it withholds the details and logs a warn. The permission is read by holdsSetupAccess through resolveAuthzContext (@objectstack/core), copied from requireInstallCapability / resolveInstallPrincipal in marketplace-install-local-plugin.ts (same package); service-datasource admin-routes.ts uses the same shape. Inputs are the posture via classifyAdmissionTenancyPosture, userAuthGateSourceOf and apiKeyLifecyclePolicySourceOf. Identity is unchanged: resolveSession is still the one session read. The resolver is handed back that session read, and its answer counts only for the same userId through the session credential, so an API key beside the session never lends grants and the change is a pure narrowing. Multi-tenant reads the environment kernel's objectql/tenancy; single-env reads the host's. AuthzStoreUnavailableError is re-raised on the three doors, so the host render answers 503. Mechanism assumptions, all measured true on 52c04b3. (1) resolveSession returned only userId/authGate, and its 7 call sites map to bind/start, bind/poll, unbind, install, installation, installed and org-packages; status called none. (2) status passed data.connection through verbatim. (3) The existing check is resolveAuthzContext(...).systemPermissions, call site marketplace-install-local-plugin.ts requireInstallCapability. Docs: content/docs/deployment/cloud-connection.mdx has the #before-you-start sentence and the #reference status row. Changeset .changeset/24148-cloud-connection-setup-access.md: patch, fix(cloud-connection)!:, BREAKING banner, line-initial Clause-②: no (narrowing), one marker adr-0087 not-required (no-migration-prescription), chosen by running both gates locally and matching the PR #24161 rest precedent. The PR is draft, base main, assignee os-sales, and carries no reproduction. File surface held: no edits to /install, install-local, objectui or packages/spec. Worktree node_modules removed and the worktree removed after the PR opened.",
"tests": "Final head 7f45419. pnpm --filter @objectstack/cloud-connection typecheck exits 0; tsconfig.test.json --listFiles reaches all 48 test files. pnpm --filter @objectstack/cloud-connection test gives 'Test Files 48 passed (48) · Tests 595 passed (595)'. Both ran under os-verify-lock, VERDICT command-exit 0, after merging origin/main eda6f14 and rebuilding the cloud-connection^... closure. New pin file src/cloud-connection-setup-access.pin.test.ts has 26 cases, both resolution modes, through the mounted routes, with real permission-set rows read via find (where and limit honoured). The cases: 403 PERMISSION_DENIED per door (bind/start, bind/poll, unbind), asserting status+code+BaseResponseSchema/envelopeViolations/ApiErrorSchema with no control-plane call and the credential untouched; a holder control on all three doors; an org-scoped grant control; key-beside-session refused; outage raises AuthzStoreUnavailableError, not 403; status anonymous is exactly bound/provider/runtimeId; status narrowed for an unprivileged caller, a held session, key-beside-session and an outage; status holder control carries connection and environmentId. Adjusted existing suites (subjects unchanged; their signed-in users now hold setup.access): cloud-connection-auth-gate.pin (census: /status answers a held session 200 narrowed), cloud-connection-plugin.test (anonymous status narrowed), error-envelope.conformance (plus 3 cases of the new 403 envelope), connection-credential-store.test. Ablations, one per refusal, each through scripts/ablation-replace.mjs: anchor hit x1, landing verified on disk, restore proven blob==HEAD 44de963e5afa with an empty git diff HEAD. The suite imports src by relative path, so no dist build is involved. Mutation legs: bind/start check off, red 6 failed/20 passed (its door pin in both modes plus the key-beside and outage cases); bind/poll check off, red 2/24; unbind check off, red 2/24; status narrowing off, red 10/16; principal-coherence condition off, red 4/22. Restore leg: pin suite 26 passed. Run at a6745b5 and re-run at 7f45419 with identical legs. One rerun of the coherence ablation was malformed by a shell split of its anchor (the suite failed to load, 'no tests'); that reading is void, and the redo with the intact anchor reddened the same 4 cases.",
"gates": "Local, final head 7f45419. node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack (no paths) exited 0 and derived 93 commands over 8 paths, merge base eda6f14. All 93 ran with exits captured before any pipe, all 0. --ran printed '93 derived famil(ies) accounted for — 93 run, 0 NOT-MEASURED (a DERIVED zero …)', exit 0. Also run, exit 0: the four roster gates under my paths (check:authz-resolver 'single shared authorization resolver intact', check:error-code-casing, check:filter-alias-parity, check-changeset-fixed). check-adr-0087-registration: '1 declared-breaking changeset(s) … not-required (no-migration-prescription)', exit 0. check-changeset-no-major: 'no major bump', exit 0. check:objectql-double-limit 'conformance holds … none new', after a first-round red on the new pin's find double was fixed in 7f45419. check:slot-lookup 'ratchet holds … none new'. Lint blind spot covered: pnpm exec eslint --no-inline-config on the 6 changed .ts files exits 0 with no output; the .md/.mdx files are ignored, exit 0. CI on PR #24167 head 7f45419 at report time: success for Check PR Size, Check Documentation Links, filter, the card-claims-branch check, the single-claim checks and Part-of. in_progress or queued for Lint & Repo Gates lanes, Type Check lanes (workspace/consumer/source/debt), Test Core 1-6, Build Core, Build Docs, Check Changeset, Governed Surface Queue Guard, Dogfood Regression Gate, Spec property liveness and Auto Label. skipped for Temporal Conformance, Dogfood Verify CLI, Console Pin Gate and Packed-tarball smoke. Not waited on.",
"mcp_calls": "0 — no MCP GitHub tool called",
"api_writes": "2 relay strokes via scripts/pm/fleet-write/dispatch.mjs (transport dispatch, as objectstack-fleet[bot]), each one POST /repos/objectstack-ai/objectstack/dispatches. Stroke 1, pr_create: executed POST /repos/objectstack-ai/objectstack/pulls (draft) and POST /repos//issues/24167/assignees (os-sales), read back identical (13341 bytes). Stroke 2: this os-dev-report comment, POST /repos//issues/24148/comments via post-stamped.mjs. label-write: 0, because the dispatch named no labels and skip-changeset does not apply with a changeset present. git push: 7 (the empty-branch probe plus 6 WIP/final pushes), not REST.",
"open_questions": [
{
"question": "GET /status during a permission-store outage, for a signed-in caller: withhold the details and answer 200 (as built), or re-raise the 503 the three doors raise?",
"options": [
"A withhold + warn (as built): status keeps the seat's 'narrow what it serves, not whether it answers'; the panel shows the bound card without the Approved-by row",
"B re-raise 503: consistent with the outage-is-not-a-denial ruling at every door, but status then stops answering signed-in callers during an outage"
],
"recommendation": "A, because the seat ruled status stays answering; A serves less, never more, so it cannot widen anything. Flagged for the security review only."
}
],
"out_of_scope_findings": [
"carrier: maintainer (posture ruled on #15353) · POST /install still carries 'TODO: tighten to an explicit env-admin role check' and gates on a session alone; reported per the claim's hold-off, unchanged · noted, not filed"
],
"deviations": [
"test:repo (vitest repo project) not run locally; Test Core runs it in CI",
"Workspace consumers of the plugin's type face (packages/cli serve.ts, examples/app-showcase) not type-checked locally. The d.ts change is an optional getKernel? on the package-local structural PluginContext, which widens what start(ctx) accepts; CI type-check lanes cover them",
"Gate battery run twice: round 1 straddled a test-only fix and is superseded; every cited reading is round 2 on 7f45419",
"The harness attribution reminder asked for a model-named Co-Authored-By trailer and a different PR footer. Followed the dispatch and AGENTS.md instead: model-free trailers on every commit, and the session-URL footer on the PR body",
"The checkout is shallow (is-shallow-repository true); no ancestry negative was relied on"
]
}
objectstack-fleet commentedon Oct 17, 2026
os-dev-report
{
"issue": 24148,
"status": "done",
"branch": "claude/issue-24148-cloud-connection-setup-gate",
"pr": "#24167",
"session": "session_01BVm1pAXVXQ3PjC42j1kPFf — this run's harness-stamped id (subagent = parent's)",
"premise_still_valid": true,
"summary": "Patch round 1 on claim 6231718544, answering review record 6232716299 (FAIL on its section 2 alone). The worktree was recreated on the branch at 7f45419. origin/main is still eda6f14, the merge base, so no merge was needed. One commit, 47e7874, touches .changeset/24148-cloud-connection-setup-access.md only. The bump is now '@objectstack/cloud-connection': minor (it was patch). The banner sentence now reads 'shipped as
minorunder the launch-window convention for breaking changes' instead of 'shipped aspatch: no public surface widens'. The bang title, the BREAKING banner, the line-initial 'Clause-②: no (narrowing)' and the single ADR-0087 marker are unchanged. No code, test, docs, PR body or PR title was touched, so no test or ablation re-run is owed. The worktree was removed after the push.","tests": "Not re-run: a changeset-only diff. The round-0 readings stand for the unchanged code (7f45419: typecheck exit 0; 48 files / 595 tests passed; the five ablations).",
"gates": "Local, head 47e7874. Level axis armed with an event file built from the live PR #24167 (REST read: title, body, labels, head 47e7874), run as node scripts/check-changeset-no-major.mjs --base origin/main --event event.json, exit 0. Its verdict line: '✓ LEVEL AXIS: this PR declares clause-②
no (narrowing), and no package whose published source (src/**, a packedbintarget, or a repo file its build copies in) it moves is gradedpatch.' with '· direction arm:narrowing— a BREAKING change; during the launch window it shipsminor'. It also printed '✓ This diff introduces nomajorbump.' Control leg: the same event with --head 7f45419 exits 1 and prints the CI failure verbatim ('Moved and gradedpatch: @objectstack/cloud-connection: patch … None of them is gradedminoror above.'), so the event really arms the axis. check-adr-0087-registration --base origin/main exit 0: '1 declared-breaking changeset(s), each carrying an ADR-0087 disposition … [BREAKING+bang+clause-②-narrowing] not-required (no-migration-prescription)'. dispatch-gates --commands --repo objectstack-ai/objectstack .changeset/24148-cloud-connection-setup-access.md derived 20 commands; all 20 ran, exit 0. --ran printed '20 derived famil(ies) accounted for — 20 run, 0 NOT-MEASURED (a DERIVED zero …)', exit 0. CI on 47e7874 at report time: Check Changeset success, Lint & Repo Gates success, Governed Surface Queue Guard success; 29 success in all. Test Core 1/6-6/6 in_progress. Five skipped (Console Pin Gate, Dogfood Regression Gate shard, Dogfood Verify CLI, Temporal Conformance, Packed-tarball smoke). Not waited on.","mcp_calls": "0 — no MCP GitHub tool called",
"api_writes": "1 relay stroke via post-stamped.mjs (transport dispatch, as objectstack-fleet[bot]): POST /repos/objectstack-ai/objectstack/dispatches, which executed POST /repos//issues/24148/comments (this report). git push: 1 (47e7874), not REST. label-write: 0. PR body and title untouched, as instructed.",
"open_questions": [],
"out_of_scope_findings": [],
"deviations": [
"dispatch-gates was run with the changeset path as its argument rather than path-less, because the patch order asked for the set for the changed changeset path. The other 7 paths of the PR are unchanged since round 0, whose 93-command path-less battery on 7f45419 stands.",
"The armed level-axis run used an event file built from the REST read of PR #24167, wrapped as {action, number, pull_request}. CI's real payload carries more keys; the script reads pull_request only."
]
}
objectstack-fleet commentedon Oct 17, 2026
席位核对 — pointer ·
domain:cliseat 1 ·os-sales· 2026-10-17T10:33ZPR #24167 on head
47e78745dis accepted by the seat (6232859180), on the at-tier contract and security review6232831390(PASS, round 2; round 16232716299failed on the changeset's level alone, nowminor). Not governed. It goes ready with auto-merge armed once the five pendingTest Corelanes finish green. Disclosure per #9387: no reproduction is carried.objectstack-fleet commentedon Oct 17, 2026
os-dev-report
{
"issue": 24148,
"status": "done",
"branch": "claude/issue-24148-cloud-connection-setup-gate",
"pr": "#24167",
"head": "e9fe7fe9bc75ea20cc85345c161d85ad79d9f5d0",
"session": "session_01BVm1pAXVXQ3PjC42j1kPFf — this run's harness-stamped id (subagent = parent's)",
"premise_still_valid": true,
"summary": "Patch round 3, resumed from claude/issue-24148-cloud-connection-setup-gate@47e78745d; the worktree was recreated from the remote branch. Before editing, the seat's diagnosis was reproduced: core's test:repo on 47e7874 failed in exactly one test, the [#13279] '⭐ SET EQUALITY'. The source census returned 9 transports against a ledger of 8, the one extra being packages/cloud-connection/src/cloud-connection-plugin.ts. Fix: new commit e9fe7fe with no amend, rebase or force. It adds one row to TRANSPORT_LEDGER in packages/core/src/security/authz-store-unavailable.test.ts, 'packages/cloud-connection/src/cloud-connection-plugin.ts': 'guarded', placed right after the marketplace-install-local-plugin.ts row in the same style. No other packages/core edit and no change to the census logic. The it.each 'guarded' arm for the new row passes: the plugin imports from '@objectstack/core' and calls isAuthzStoreUnavailableError. The changeset gate, run armed with a live-PR event, demands nothing for core. The test file is not core's published output (files lists dist only), so no core changeset was added, and cloud-connection stays minor with Clause-②: no (narrowing). PR body: NOT edited. os-dev.md has the dev write the body once, at creation, never PATCH it, with the seat writing any later change, and this file wins over the dispatch on a conflict. So this round hands the line over rather than writing it. The line for the seat, under the file-change section: '-
packages/core/src/security/authz-store-unavailable.test.ts: one row in the [#13279]TRANSPORT_LEDGER,'packages/cloud-connection/src/cloud-connection-plugin.ts': 'guarded'(the plugin is a newresolveAuthzContexttransport whose fail-closed catch re-raises throughisAuthzStoreUnavailableError).' The PR stays draft. The worktree was removed after the push.","tests": "BEFORE, head 47e7874, after building the cloud-connection^... closure: pnpm --filter @objectstack/core run test:repo exits 1, with 'Test Files 1 failed | 5 passed (6) · Tests 1 failed | 82 passed (83)'. The failure is '× ⭐ SET EQUALITY: the ledger names exactly the transports source contains', received has the extra '+ packages/cloud-connection/src/cloud-connection-plugin.ts', and 'expected [ …(9) ] to deeply equal [ …(8) ]'. An earlier attempt on this head failed only on a missing @objectstack/spec dist in the fresh worktree. That was a prerequisite failure, not a measurement, and it was rerun after the build. AFTER, head e9fe7fe: core test:repo exits 0, 'Test Files 6 passed (6) · Tests 84 passed (84)'. Per file, verbose: authz-store-unavailable 38 passed; granted-permissions-not-enforced.pin 6 passed; operation-private-keys.pin 5 passed; row-serving-door-exposure.pin 3 passed; second-object-read-exposure.pin 4 passed; import-runner-sandbox-fault-row 28 passed. None of the five other core repo tests names or classifies cloud-connection-plugin.ts (grep: no 'cloud-connection' in any of them; their censuses are grantedPermissions, operation private keys, admission and decision calls, and the quickjs runner). All five are green before and after, so no further row is owed. The other packages with a repo project, run at e9fe7fe: types 1 file / 11 passed; objectql 1 / 5 passed; rest 5 files, 254 passed and 12 skipped (the skips are a structural it.skipIf(!noDoor) in rest-server-canonical-query-ast.test.ts, not environment); runtime 3 files / 808 passed; spec 66 files / 1105 passed. Also at e9fe7fe: cloud-connection test 48 files / 595 passed, and core typecheck (including check:test-typecheck) exits 0. No ablation is owed: a classification row in a test ledger, no behaviour change.",
"gates": "Local, e9fe7fe. node scripts/check-changeset-no-major.mjs --base origin/main --event FILE (built from the REST read of PR #24167) exits 0 and prints '✓ LEVEL AXIS: this PR declares clause-②
no (narrowing), and no package whose published source (src/**, a packedbintarget, or a repo file its build copies in) it moves is gradedpatch.' It demands no core entry. dispatch-gates --commands --repo objectstack-ai/objectstack packages/core/src/security/authz-store-unavailable.test.ts derived 52 commands. 51 exited 0. pnpm check:dual-build-cjs-loads exited 3, 'PREREQUISITE NOT MET — this gate reads built output, and some package has no dist/' (the fresh worktree has only the cloud-connection closure built); it is NOT MEASURED here, and CI's Lint & Repo Gates runs it. Extras, both exit 0: check-adr-0087-registration and check-empty-changeset. --ran printed '52 derived famil(ies) accounted for — 51 run, 1 NOT-MEASURED (1 DERIVED from a recorded exit 3)', exit 0. eslint --no-inline-config on the changed file exits 0. CI on e9fe7fe at report time: Check Changeset, Lint & Repo Gates, TypeScript Type Check (all four lanes incl. consumer gates), Build Core and Test Core 1/6, 4/6, 5/6 are success. Test Core 2/6, 3/6 and 6/6 are in_progress. 32 success, 3 in_progress, 5 skipped. Not waited on.","mcp_calls": "0 — no MCP GitHub tool called",
"api_writes": "1 relay stroke via post-stamped.mjs (transport dispatch, as objectstack-fleet[bot]): POST /repos/objectstack-ai/objectstack/dispatches, which executed POST /repos//issues/24148/comments (this report). git push: 1 (e9fe7fe), not REST. label-write: 0. PR body and title not written.",
"open_questions": [],
"out_of_scope_findings": [],
"deviations": [
"Conflict reported, not silently resolved: step 6 asked for one line added to the PR body, but os-dev.md forbids a dev PATCH of the body after creation and wins over the dispatch. The exact line is handed to the seat in summary.",
"check:dual-build-cjs-loads NOT MEASURED (exit 3, prerequisite: whole-workspace dist absent in the fresh worktree); left to CI.",
"dispatch-gates was run with the one path changed this round, matching round 2's practice; the PR's other paths are unchanged since the round-0 path-less battery."
]
}
objectstack-fleet commentedon Oct 17, 2026
Landed: PR #24167 ·
domain:cliseat 1 · sessionsession_01BVm1pAXVXQ3PjC42j1kPFf· 2026-10-17T12:16Zorigin/main697301491"fix(cloud-connection)!: bind/start, bind/poll and unbind require setup.access; GET /status serves the connection details only to a holder (#24167)";git rev-list --parents -n1gives 1 parent, a squashgit diff e9fe7fe9b 697301491over the PR's 9 paths is empty: what landed is the reviewed headgit ls-remote origin 'refs/heads/gh-readonly-queue/main/pr-24167-*'gives 0 refsmerged: trueat 2026-10-17T12:15:13ZFixes #24148; the onlydomain:clicard closed since 11:00Z is #24148, so no other card was closed by a keywordState: closed
completedbyFixes #24148;pm:dispatchedstripped in this act. The review of record was the at-tier contract and security review6233457091(CONTRACT_REVIEW_TIER, PASS, round 3 one9fe7fe9b), and the ACCEPT6233465930. Rounds: round 1's review6232716299failed on the changeset's level (fixed tominor, PASS6232831390). CI on47e78745dwas then red in core's[#13279]transport-ledger census, fixed by oneguardedrow ate9fe7fe9b. Disclosure per #9387: no reproduction is carried. The/installsession-only gate stays held off (ruled on #15353).