Skip to content

QA run · studio-authoring.org-override-registry-gate (1/1) · 6bf16849 · 2026-10-16 · 1 PASS / 0 PARTIAL / 0 FAIL / 0 BLOCKED / 0 NOT-RUN #24075

Closed

Description

@objectstack-fleet

Run record for the re-run #24036 (half B) asks for after revising this item. Runner: an os-dev subagent dispatched by the domain:devx seat 2 PM (session session_016PVjjuVPte5XEJvaQx1E4t). Protocol: .claude/skills/checklist-test/SKILL.md + docs/qa/platform-checklist/RUNNER.md. Executed sequentially (no subagent tool in this runner).

Environment fingerprint

  • framework: 6bf16849bdab557aadecf49c09a3e0cd39bc8c30, the tip of branch claude/issue-24036-ledger-b at run time. Its product tree is origin/main c91af8ed6; the branch adds docs/qa/platform-checklist/areas/*.json only. Built with pnpm install --frozen-lockfile and turbo run build (75/75 tasks).
  • .objectui-sha: f8267df93aba8fb09cc1cc0692eadc0c8c5a5e56 (no browser leg in this item).
  • boot: OS_PORT=41911 objectstack dev --ui --seed-admin -p 41911 -d file:(run dir)/probe/data.db from examples/app-showcase, its own port and file DB (the CLI also provisioned the sibling data.telemetry.db), stopped by its own process-group id afterwards.
  • persona(s): the seeded admin (admin@objectos.ai), identity proven with GET /api/v1/auth/get-session before the first cell
  • timestamps: 2026-10-16, 23:29Z to 23:30Z

Scope

Selector studio-authoring.org-override-registry-gate resolves to 1 runnable item: studio-authoring.org-override-registry-gate at revision 3, P1, surface api. No planned or blocked-hidden item.

Per-clause verdicts

# clause (short) verdict evidence
0 object overlay refused 403 pass PUT /api/v1/meta/object/showcase_task (served item, label changed) 403, code NOT_OVERRIDABLE. Field variant: PUT /meta/field/showcase_task.title 403 NOT_OVERRIDABLE
1 view overlay accepted and wins at read pass PUT /meta/view/showcase_task.grid (label "QA Overlay Grid B") 200 "Saved customization overlay (env-wide, state=active)"; GET serves label "QA Overlay Grid B"
2 job create refused 403 pass PUT /meta/job/qa_probe_job 403 NOT_CREATABLE
3 new object accepted while overlay refused pass PUT /meta/object/qa_org_probe (new, sharingModel private) 200 state active, in the same run as the 403 on showcase_task. Dashboard variant: a new dashboard 200
4 delete overlay resets pass DELETE /meta/view/showcase_task.grid 200 reset:true; the GET is byte-identical to the pre-overlay base (envelope keys aside); a second DELETE 200 reset:false "already at artifact default"

Automated pins run (RUNNER rule 6)

  • packages/objectql/src/overlay-precedence.test.ts (automated.ref): 1 file, 26 passed, vitest run --maxWorkers=1 under the shared verify lock.

Reproduction rules

No clause scored fail, so none is owed. No authentication or authorization hole was found; nothing here is withheld under the RUNNER rule-2 carve-out.

Derived item verdict

studio-authoring.org-override-registry-gate r3: pass (5 pass of 5 clauses).

  • Registry read first (step 0, GET /api/v1/meta/types entries): object overlay false / create true; field overlay false / create false; job false / false; view true / true; dashboard true / true.
  • Revised variant field (create LOCKED): PUT /meta/field/showcase_task.qa_zz_probe (a new name) 403 NOT_CREATABLE, and the follow-up GET is 404 — the variant now holds as written.

Checklist-accuracy findings and fixture gaps from this run close out on #24036.


Generated by Claude Code

Activity

  1. objectstack-fleet commented on Oct 17, 2026

    @objectstack-fleet
    ContributorAuthor

    Close-out (domain:devx seat 2): every clause PASS; nothing to extract. Ruling C on #24127 (maintainer): a verification re-run of a ledger edit no longer carries a qa-run record, and the existing ones close out now. The revised item studio-authoring.org-override-registry-gate landed with #24141 (9ffe8af094), Part of #24036; its history row names #24036.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions