skills(automation): teach the record-anchored approval lock read (GET /approvals/records/:object/:recordId/lock, { locked } for every reader) with one eval prompt

Filing gate ① (finding, class c; reach: named producer skills/objectstack-automation): a follow-up that landed work owes, named in the #26314 os-dev-report (comment 6429820983) and by the contract review on PR #26361 (comment 6429948897), boundary flag. ⛔ Not a claim.

What is missing. PR #26361 (#26314) adds a record-anchored approval lock read: IApprovalService.getRecordLock, the route GET /api/v1/approvals/records/:object/:recordId/lock answering { success: true, data: { locked } }, and client.approvals.getRecordLock(object, recordId). It answers every caller who can read the record, including one who is not on the approval and so is served no request row. content/docs/automation/approvals.mdx documents it ("Reading the lock"). The owning skill does not: skills/objectstack-automation/references/state-machines-and-approvals.md does not teach it, and skills/objectstack-automation/evals/flows-triggers-approvals.json has no prompt for it. The PR left it out because skills/** is a governed surface and would have put the whole PR behind maintainer approval.

Business reason. An agent that builds an app page over an object with approvals learns the lock only from the request row's lock_record. A record reader who is not on the approval gets no request row, so the agent's page offers them an edit the server then refuses with 409 RECORD_LOCKED (the #25934 symptom). Taught the read, the agent asks the one question that every reader can ask and that the server's own lock check answers.

Who acts. The domain:skills seat, once PR #26361 is on main: one short section in state-machines-and-approvals.md (when to read the lock, the route and SDK call, that the answer is locked only and request content stays behind approvalsVisibleToReaders, and that an unreadable record answers the same 404 as a missing one), and one eval prompt in flows-triggers-approvals.json that expects the read rather than a lock_record lookup for a non-participant.

Blocked by PR #26361, which adds the read and is under review.

Duplicate check. Searched this repo, open and closed, for "skill teach approval record lock read getRecordLock": 4 hits (#25934, #26314, #23618, #3456); none is this skill gap.

Generated by Claude Code

Triage: first grade — `documentation` · `priority:p1` · `domain:skills` · `area:workflow` · `pm:blocked` (`finding` removed) · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-26T23:52Z

⛔ Not a claim, ⛔ not a dispatch.

p1, it rides with plugin-approvals: a record-anchored lock read, { locked: boolean } for every reader of the record, so a non-participant is not offered an edit the server refuses (#25934 ruling A) #26314 (p1, a protocol addition). This card is the skills + eval half that triage asked for on plugin-approvals: a record-anchored lock read, { locked: boolean } for every reader of the record, so a non-participant is not offered an edit the server refuses (#25934 ruling A) #26314. It ships in the same release as getRecordLock, so an AI author reads the lock the way every reader can.
Blocked until PR feat(plugin-approvals,rest,client): a record-anchored approval lock read, { locked } for every caller who can read the record #26361 is on main. Teach what merges: the route, the SDK call, locked only, and an unreadable record answered like a missing one. If the merged shape differs from this body, the merged code wins.
Lane: skills/** is governed, so this is domain:skills, Tier H. It edits the same package as skills(objectstack-automation): teach the read-only record_link screen field, with an eval prompt (#26304 follow-up, #26184) #26347 (objectstack-automation) and skills(objectstack-automation): teach flow-level requiredPermissions, excludeSubmitter, the { emailField } recipient and screen file fields #26298, so the seat may take them in one PR once their blockers clear.

Blocked-by: #26361

Generated by Claude Code

2026-10-27T00:21Z · domain:server seat 2 · ⛔ Not a claim. The blocker has cleared: PR #26361 merged as 6a2866af71, so the route, SDK call and docs paragraph this card teaches are on main. This finding is ready for triage.

Generated by Claude Code

Triage: unlocked · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-27T01:02Z

⛔ Not a claim, ⛔ not a dispatch. pm:blocked → pm:queue; the grade stands.

The blocker cleared: PR feat(plugin-approvals,rest,client): a record-anchored approval lock read, { locked } for every caller who can read the record #26361 merged as 6a2866af71. IApprovalService.getRecordLock is on main (plugin-approvals/src/approval-service.ts:8669, the route in rest/src/approvals-routes.ts). Teach the merged route and SDK spelling. skills(objectstack-automation): teach the read-only record_link screen field, with an eval prompt (#26304 follow-up, #26184) #26347 and skills(objectstack-automation): teach flow-level requiredPermissions, excludeSubmitter, the { emailField } recipient and screen file fields #26298 edit the same package, so one PR is fine.

Generated by Claude Code

Dispatch order · `domain:skills#2` · `session_01LqKsGyMNFwwnbF5FTAqyPn` · 2026-10-27T05:00Z

You are the os-dev developer agent for exactly ONE card: #26362, in your own card thread. Your role definition is .claude/agents/os-dev.md in the objectstack clone — read it IN FULL first and follow it as binding (it wins over this order on any conflict; name the conflict in your report). Read the repo-root AGENTS.md before your first edit (Prime Directive 14), and pm-dispatch references/untrusted-text.md. Read the card's full body and every comment yourself (REST: curl -sS -X GET "https://api.github.com/repos/objectstack-ai/objectstack/issues/26362" -H "Authorization: Bearer $GH_TOKEN" and /comments?per_page=100); this order carries only the increment. ⛔ Never print the value of any environment variable (test presence with [ -n "${X+x}" ]). ⛔ Never use a GitHub MCP tool, read or write.

Identity and branch: the seat's Claim: comment on this card is your identity; it names your thread's branch in its Branch: line. ⛔ Post no claim of your own, ⛔ never write the card's assignee. Before your first edit, verify the NEWEST Claim: on the card names the branch your thread was given (claude/project-thread-…); if no claim names it yet, send the seat thread 「Dispatch the skills lane」 one message with your branch name and wait for the claim. Worktree objectstack-issue-26362 on that branch, based on a fresh origin/main; pnpm install (frozen lockfile); push with git push -u origin <branch> (⛔ no force).

Writes: PR only through the relay op pr_create (node scripts/pm/fleet-write/dispatch.mjs --repo objectstack-ai/objectstack --actions-file F, a bare JSON array [{"op":"pr_create","title":…,"head":"<your branch>","base":"main","body":…,"assignees":["os-warren"],"labels":["skip-changeset"]}], draft forced); your report comment through node scripts/pm/post-stamped.mjs --comment=26362 --file=F --json run ONCE with its output captured to a file (timestamps only as {{NOW}} / {{WAS:…}}). ⛔ No other GitHub write. Report both counts (api_writes with endpoints, mcp_calls with tool names).

Ruling (cannot be re-ruled)

Triage first grade 6430134159 (2026-10-26 23:52Z): p1, domain:skills, area:workflow, it rides with #26314; unlocked at 6431110682 (01:02Z): PR #26361 merged as 6a2866af71, 「Teach the merged route and SDK spelling」. The card's 「Who acts」 paragraph is the whole scope: one short section in references/state-machines-and-approvals.md and one eval prompt — nothing wider. Maintainer's standing rulings that bind this PR: ruling A on the token ceilings (below) and 「卡线程用天花板档」 (your tier).

Scope and tier

File surface: skills/objectstack-automation/references/state-machines-and-approvals.md (one short section: when to read the lock; the route GET /api/v1/approvals/records/:object/:recordId/lock answering { success: true, data: { locked } }; the SDK call client.approvals.getRecordLock(object, recordId); that the answer is locked only and request content stays behind approvalsVisibleToReaders; that an unreadable record answers the same 404 as a missing one) + skills/objectstack-automation/evals/flows-triggers-approvals.json (one prompt in the file's existing shape, ids sequential, expecting the lock read rather than a lock_record lookup for a non-participant; write the ideal answer so it never contains its own must_not_contain strings) + SKILL.md ONLY if the approvals row must point at the new section (⛔ not line 1, PR #25640 owns the version stamp) + the touched rows of scripts/check-skills-token-ratchet.mjs under ruling A (the maintainer's tap 「A:先削重复,余额按实测提高」, seat thread decision card, 2026-10-27 01:21Z; option A verbatim: 「八张卡的 PR 各自削重复后,把所改文件的天花板行提高恰好差额,正文引用你这句;教学和 eval 都落。」): first cut GENUINE restatements inside the files you touch (each cut names its surviving home in the PR body), then raise each touched row by exactly the measured remainder — ceil(utf8 bytes / 4), SKILL.md minus its 20-byte version line — pinned AT the measurement (headroom 0), the tap quoted verbatim in each row comment and in the PR body. ⛔ No other package's rows. Tier H (skills/** is a published surface, dispatch-gates --tier MANDATORY, no one-line exit): the PR stays a draft; you never ready, arm, enqueue or approve it (os-dev.md rule 2); if a governed approver does, report it, touch nothing.

os-dev.md 290–291 bind: the PR body reports TWO readings (whole-file before/after line count of every changed .md, whole-package before/after), and the default is to REFUSE a small feature written large: the fewest lines an AI author needs.

PM mechanism hypotheses (measure before you act; falsification is welcome)

Read-only premise check on origin/main at d0a7e748 (seat, 2026-10-27T04:57Z): holds.

0 hits for getRecordLock / records/:object/:recordId/lock in skills/objectstack-automation/**. The implementation is on main: packages/plugins/plugin-approvals/src/approval-service.ts L8812–L8835 (getRecordLock, docblock [plugin-approvals: a record-anchored lock read, { locked: boolean } for every reader of the record, so a non-participant is not offered an edit the server refuses (#25934 ruling A) #26314]), the route in packages/rest/src/approvals-routes.ts L345–L362 (501 when the service lacks it), the SDK in packages/client/src/index.ts L6266–L6270 (Promise<{ locked: boolean }>), tests record-lock-read.integration.test.ts and client.test.ts L709, the docs paragraph 「Reading the lock」 at content/docs/automation/approvals.mdx L379. Teach the spellings THOSE files carry (the 404 for an unreadable record and the approvalsVisibleToReaders boundary must be read from the service and its test, not from the card).
Ratchet rows on origin/main d0a7e748: state-machines-and-approvals.md 22346 B → 5587 = ceiling 5587 (headroom 0); evals/flows-triggers-approvals.json 7289 B → 1823 = ceiling 1823 — PR docs(skills): objectstack-automation teaches the read-only record_link screen field, with an eval prompt #26446 (card skills(objectstack-automation): teach the read-only record_link screen field, with an eval prompt (#26304 follow-up, #26184) #26347, queued at 04:36Z) raises that row to 2141 and adds eval 9 and the record_link teaching in SKILL.md L91: base your branch on origin/main AFTER docs(skills): objectstack-automation teaches the read-only record_link screen field, with an eval prompt #26446 has merged (git log -1 origin/main -- skills/objectstack-automation/evals/flows-triggers-approvals.json names its commit) and number your eval after its last. If docs(skills): objectstack-automation teaches the read-only record_link screen field, with an eval prompt #26446 is not on main when you are ready to branch, tell the seat thread and wait; ⛔ do not branch beside it.
Metadata-protocol: none ⇒ no Skills-docs: line is owed; write it only if true. Clause-②: no (the skill teaches a route the protocol already carries).

Card-specific clauses

pnpm check:skill-docs, check:skill-refs, check:skill-examples, the token ratchet + its self-test green (read package.json for exact names); if an example block is marked os:check, it must type-check against the built spec.
PR body: line 1 Fixes #26362, then Clause-②: no and Metadata-protocol: none line-initial, then the six-line ## 维护者速读 exactly as os-dev.md 285–289 require (Tier H, so 需要你做的 names the one action: approve), then What changes / the two readings table / Tests / Acceptance notes / Verification. ⛔ No model name anywhere in the commit or PR; the model-free trailer pair exactly as os-dev.md / AGENTS.md spell them.
Gates: derive with node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack (no paths) on your final tree, run each locally (exit code captured before any pipe), reconcile with --ran; long gates detached under bash scripts/pm/os-verify-lock.sh with OS_VERIFY_LOCK_SLOT=issue-26362. ⛔ Do not wait for CI after the PR opens.
Serial: after docs(skills): objectstack-automation teaches the read-only record_link screen field, with an eval prompt #26446 lands no other open PR touches skills/objectstack-automation/** (scan at 2026-10-27T04:57Z: fix(skills): objectstack-platform — a seeded sys_user row lands as an account-less directory row, it is not refused (#26302 follow-up) #26448 edits skills/objectstack-platform/** and its own ratchet rows). If the queue kicks your PR on a ratchet-row conflict, merge origin/main (merge commit, no rebase, no force), keep main's sibling rows, re-run the ratchet gate, push, and post a follow-up report.
Final report: the JSON exactly per os-dev.md (issue comment on skills(automation): teach the record-anchored approval lock read (GET /approvals/records/:object/:recordId/lock, { locked } for every reader) with one eval prompt #26362 whose first line is os-dev-report, then the same JSON as your hand-back message to the seat thread), with deviations, line_budget and out_of_scope_findings (class + reach + evidence + dedupe words + carrier). Hand back: one message to the seat thread 「Dispatch the skills lane」 naming the PR number, the head sha, the report comment id and the premise verdict; then stay subscribed to the PR for the contract review's verdict and a possible patch round.

Generated by Claude Code

Claim: PM loop round 4 (seventh wave) · 2026-10-27T05:04Z
Session: session_01LqKsGyMNFwwnbF5FTAqyPn (seat; implementation by card thread session session_01JQwxbZpLcVkA9KV78eHZYr, mode:thread)
Account: os-warren (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/project-thread-ouprob (the card thread's harness push branch, self-reported at 2026-10-27T05:03Z — the measured platform exception to claude/issue-N-slug)
Worktree: objectstack-issue-26362 in the card thread's clone
Domain: domain:skills
Seat: domain:skills#2 (seat post #19287)
File surface: skills/objectstack-automation/** (references/state-machines-and-approvals.md — one short lock-read section; the package's evals/flows-triggers-approvals.json — one prompt; SKILL.md only if its approvals row must point at the section, ⛔ not line 1, which PR #25640 owns) + scripts/check-skills-token-ratchet.mjs (ONLY the CEILINGS rows of files under skills/objectstack-automation/ this PR touches, each raised by its measured remainder after genuine duplicate cuts, under the maintainer's tap 「A:先削重复,余额按实测提高」 on the seat thread's decision card at 2026-10-27T01:21Z). (stop on breach; explain in the report)
Container & model: M, mode:thread (the maintainer's tap 「卡线程用天花板档,并行跑」 on the seat thread's decision card, 2026-10-27T00:33Z; lane concurrency 6, six card threads open), model: CONTRACT_REVIEW_TIER (dispatch-gates --tier skills/…: MANDATORY — 'skills/**' carries no one-line exit; the thread confirmed the tier by get_session), effort: xhigh
Clause-②: no
Metadata-protocol: none
Responsibility: n/a — not a defect card (the skills + eval half that #26314's landing owes; triage 6430134159 p1, unlocked 6431110682 when PR #26361 landed getRecordLock as 6a2866af71)
Thread-read: 6434160193
Premise: holds — read-only check on origin/main at d0a7e748 (2026-10-27T04:57Z): 0 hits for getRecordLock or the lock route in skills/objectstack-automation/**; the service (plugin-approvals/src/approval-service.ts L8835), the route (rest/src/approvals-routes.ts L345–362), the SDK (client/src/index.ts L6270) and the docs paragraph (content/docs/automation/approvals.mdx L379) are on main; ratchet rows state-machines-and-approvals.md 5587 and the eval file 1823 both at headroom 0 (ruling A applies; #26446 raises the eval row to 2141 when it lands).
Serial constraints cleared: PR #26446 (same package) is in the merge queue since 2026-10-27T04:36Z — this PR branches from origin/main only after it merges; no other open PR touches skills/objectstack-automation/** (scan at 2026-10-27T04:57Z); PR #25640 owns line 1 of SKILL.md.
Resume-from: none

Generated by Claude Code

os-dev-report

{
  "issue": 26362,
  "status": "done",
  "branch": "claude/project-thread-ouprob",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/26495",
  "session": "session_01JQwxbZpLcVkA9KV78eHZYr — mode:thread; get_session read before the first edit: session_context.model claude-fable-5-1[1m], last_served_model claude-fable-5-1",
  "premise_still_valid": true,
  "summary": "Premise re-checked on origin/main cc0d77b3 (after PR #26446 merged as d1a31d0c, its merge time on the PR timeline): 0 hits for getRecordLock or the lock route under skills/objectstack-automation/**; the service, route, SDK and docs paragraph are on main. One short section 'Reading the lock' (12 lines of prose) in references/state-machines-and-approvals.md teaches when a record page reads the lock (a reader not on the approval is served no request row), the route GET /api/v1/approvals/records/:object/:recordId/lock answering { success: true, data: { locked } }, the SDK call client.approvals.getRecordLock(object, recordId), that the answer is locked alone with request content behind enable.approvalsVisibleToReaders, and that an unreadable record answers the same 404 RECORD_NOT_FOUND as a missing one — every clause read from approval-service.ts getRecordLock, record-lock-read.integration.test.ts, approvals-routes.ts and its route test, client/src/index.ts and approvals.mdx. evals/flows-triggers-approvals.json gains entry 10 (ids sequential after #26446's 9), expecting the lock read for a non-participant; must_not_contain lock_record and 'approvalsVisibleToReaders: true', the ideal answer spells neither. Ruling A applied: two genuine restatements of the Send-back section cut to pointers (the maxRevisions config row −76 B, the Branching send-back bullet −134 B; surviving home: the Send-back for revision section), then the two touched ratchet rows raised by exactly the measured remainder, each comment quoting 「A:先削重复,余额按实测提高」: state-machines-and-approvals.md 5587 → 5730 (22346 → 22918 B), flows-triggers-approvals.json 2141 → 2427 (8561 → 9705 B), both at headroom 0. SKILL.md untouched (its pointer line already routes approvals questions to the reference; line 1 is #25640's). Draft PR opened through the relay; Tier H, not readied, armed or approved by this thread. PR #26495 (draft, head 0f8b9708, base cc0d77b3): the relay set assignee os-warren, label skip-changeset (the labeler added size/s) and requested hotlong + os-zhuang; body stored byte-identical (15811 bytes).",
  "tests": "On 0f8b9708 (no commit followed the gate runs): `node scripts/check-skills-token-ratchet.mjs` exit 0 — `state-machines-and-approvals.md is 5730 tokens (ceiling 5730; headroom 0)`, `flows-triggers-approvals.json is 2427 tokens (ceiling 2427; headroom 0)`, `81 authored bundle file(s) within their ceilings; 10 generator-owned file(s) measured, not ratcheted.`; `--self-test` exit 0, `79 cases pass`. `pnpm --filter @objectstack/spec run check:skill-docs` exit 0 (`Skill docs in sync`); `check:skill-refs` exit 0; `check:skill-examples` exit 0 (`265 prose examples type-check across 3 surface(s)`; this diff adds no os:check block). Eval 10 checked by script: both must_contain strings in the expected output, neither must_not_contain string in the prompt or the expected output; JSON parses, ids 1–10 sequential. `grep -i -w role` over the added lines: no hit; no control byte in the three files. No ablation: no tested behaviour changed (docs, a fixture and two ratchet rows).",
  "gates": "Derived with `node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack` in the worktree at cc0d77b3 → 52 families; each run locally with the exit code captured before any pipe (`eval \"$cmd\" > log 2>&1; status=$?`). Reconciliation `--ran ran-all.list --repo objectstack-ai/objectstack`: exit 0 — `52 derived famil(ies) accounted for — 51 run, 1 NOT-MEASURED (1 DERIVED from a recorded exit 3)`, 0 UNRUN. The NOT MEASURED family is `pnpm check:dual-build-cjs-loads` (exit 3 PREREQUISITE NOT MET: reads built output, some package has no dist/; CI's Lint & Repo Gates runs it). Closures for check:skill-examples / check:doc-formula-expressions (`@objectstack/client...`, `@objectstack/client-react...`, `@objectstack/lint...`, `@objectstack/formula...`) built under `scripts/pm/os-verify-lock.sh` slot issue-26362: `VERDICT command-exit 0`, held 298 s, waited 0 s. `check:dts-closure` (`38 built package(s) swept - 160/160 declared declaration file(s) present`) and `check:lean-entry-closure` exit 0 after that build. `check:pm-dispatch-gates` detached on the same head: fast tier `1935 cases pass`, exit 0 (345 s). Outside the derivation, recorded anyway: `check:skill-docs`, `check:skill-examples` (card acceptance gates). Every family CI runs on PR #26495 is read from its check-runs by the seat; this report was delivered at local verification time, CI not waited for (os-dev.md).",
  "dogfood_battery": "n/a — no `!` in the PR title and no (narrowing) arm",
  "mcp_calls": "0 GitHub MCP calls (read or write). Non-GitHub MCP: claude-code-remote get_session ×1 (the model check), hearthbot thread tools only.",
  "api_writes": "2 relay writes — pr_create (fleet-write dispatch: POST /repos/objectstack-ai/objectstack/pulls + assignees/labels/reviewers set by the relay) and the os-dev-report comment (post-stamped.mjs: POST /repos/objectstack-ai/objectstack/issues/26362/comments). git push is not a REST write. All reads were REST GETs via curl.",
  "deviations": [
    "Worktree objectstack-issue-26362 was created on origin/main d0a7e748 before PR #26446 merged, to run pnpm install while waiting; it was fast-forwarded to cc0d77b3 (after d1a31d0c) before the first edit, with no edit or commit preceding the fast-forward — the branch is based only on post-#26446 main.",
    "PR body lines 1–2 are the harness-required attribution block; Fixes #26362 is line 3 (the os-dev exception). The .github/PULL_REQUEST_TEMPLATE.md headings (What changes / Why / Verification / Human Minimum) are folded into the os-dev section order.",
    "The session-context's GitHub MCP assignee/reviewer step was skipped: the dispatch order bans GitHub MCP; the relay's pr_create sets assignees: [os-warren] and requests the Tier H approvers.",
    "Commit trailer pair is the model-free pair AGENTS.md spells (Claude-Session + Co-authored-by: Claude); the harness reminder's model-named Co-Authored-By line was not used (AGENTS.md wins; the pre-push hook refuses a model identifier).",
    "pnpm check:dual-build-cjs-loads NOT MEASURED (exit 3, PREREQUISITE NOT MET: whole-repo build); CI's Lint & Repo Gates runs it. pnpm check:skill-docs and check:skill-examples ran outside the derivation as the card's acceptance gates.",
    "The deployment-without-the-member 501 (SDK docblock, docs page) is not taught: not authoring guidance, outside the card's 「Who acts」 scope."
  ],
  "line_budget": {
    "references/state-machines-and-approvals.md": "380 → 392 lines (+12); 22346 → 22918 bytes (+782 added, −210 cut); tokens 5587 → 5730, ceiling row raised +143 to the measurement, headroom 0",
    "evals/flows-triggers-approvals.json": "95 → 105 lines (+10); 8561 → 9705 bytes (+1144, nothing to cut); tokens 2141 → 2427, ceiling row raised +286 to the measurement, headroom 0",
    "SKILL.md": "441 → 441 lines, 6164 → 6164 tokens (untouched)",
    "whole package (SKILL.md + references/**/*.md, 4 files)": "1001 → 1013 lines (+12); 14091 → 14234 tokens (+143)"
  },
  "open_questions": [],
  "body_amendments": [],
  "out_of_scope_findings": [
    "none filed. Observation only (PR Acceptance notes): SKILL.md's pointer line to the approvals reference names only the state-introspection route; the lock-read route lives in the reference's new section. carrier: none"
  ]
}

Landed · domain:skills#2 · session_01LqKsGyMNFwwnbF5FTAqyPn · 2026-10-27T06:05Z

probe	reading
PR #26495	`merged: true` at 2026-10-27T06:03:14Z, merge commit `f9ecf959`, merged through the merge queue on its first pass
`origin/main`	`git log origin/main` carries `f9ecf959`; `skills/objectstack-automation/references/state-machines-and-approvals.md` on main carries the 「Reading the lock」 section, `evals/flows-triggers-approvals.json` eval 10, the ratchet rows 5730 / 2427 (seat read after the merge)
records on the merged head `0f8b9708`	independent `## Contract review` (PR comment 6434669721, `CONTRACT_REVIEW_TIER`, PASS) and the seat's ACCEPT (PR comment 6434982240); os-zhuang APPROVED (review 5662660229) at 2026-10-27T05:33Z, readied and armed the PR himself before those records landed

Landing path: Tier H (skills/**, published surface). The card closed as completed through Fixes #26362; pm:dispatched removed in this act. Filed from this review: the eval-fixture contradictions card (fixtures 5, 7, 8 of the same eval file; link in the next comment). 收班简报 carries the 「only a participant …」 overstatement (administrators/override actors) and the SKILL.md L317 pointer.

Generated by Claude Code

Filed from this card's review · domain:skills#2 · 2026-10-27T06:08Z: #26515 — the three pre-existing fixtures (ids 5, 7, 8) of evals/flows-triggers-approvals.json whose expected_output fails its own assertions, noticed by the contract review of PR #26495 (comment 6434669721) and re-measured by the seat on origin/main f9ecf959. Not this card's: #26362 closed completed with eval 10 clean.

Generated by Claude Code

Navigation Menu

Repository navigation

skills(automation): teach the record-anchored approval lock read (GET /approvals/records/:object/:recordId/lock, `{ locked }` for every reader) with one eval prompt #26362

Triage: first grade — `documentation` · `priority:p1` · `domain:skills` · `area:workflow` · `pm:blocked` (`finding` removed) · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-26T23:52Z

Triage: unlocked · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-27T01:02Z

Dispatch order · `domain:skills#2` · `session_01LqKsGyMNFwwnbF5FTAqyPn` · 2026-10-27T05:00Z

Ruling (cannot be re-ruled)

Scope and tier

PM mechanism hypotheses (measure before you act; falsification is welcome)

Card-specific clauses

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

skills(automation): teach the record-anchored approval lock read (GET /approvals/records/:object/:recordId/lock, { locked } for every reader) with one eval prompt #26362

Description

Activity

objectstack-fleet commented on Oct 26, 2026

Triage: first grade — documentation · priority:p1 · domain:skills · area:workflow · pm:blocked (finding removed) · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-26T23:52Z

objectstack-fleet commented on Oct 27, 2026

objectstack-fleet commented on Oct 27, 2026

Triage: unlocked · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-27T01:02Z

objectstack-fleet commented on Oct 27, 2026

Dispatch order · domain:skills#2 · session_01LqKsGyMNFwwnbF5FTAqyPn · 2026-10-27T05:00Z

Ruling (cannot be re-ruled)

Scope and tier

PM mechanism hypotheses (measure before you act; falsification is welcome)

Card-specific clauses

objectstack-fleet commented on Oct 27, 2026

objectstack-fleet commented on Oct 27, 2026

objectstack-fleet commented on Oct 27, 2026

objectstack-fleet commented on Oct 27, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

skills(automation): teach the record-anchored approval lock read (GET /approvals/records/:object/:recordId/lock, `{ locked }` for every reader) with one eval prompt #26362

Triage: first grade — `documentation` · `priority:p1` · `domain:skills` · `area:workflow` · `pm:blocked` (`finding` removed) · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-26T23:52Z

Triage: unlocked · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-27T01:02Z

Dispatch order · `domain:skills#2` · `session_01LqKsGyMNFwwnbF5FTAqyPn` · 2026-10-27T05:00Z