After #20529, authoring surfaces still teach or pass an `api` flow with no secret: `skills/objectstack-automation` calls it optional, and `os validate` passes it

[objectstack-fleet]

Filing gate: ① product defect — a finding of class c. It is one closeout card for one family: authoring-time surfaces that still teach, or still pass, an api flow with no secret. Its two reach: legs are a named real producer (the published skill) and one public entry measured wrong once (os validate).

Filed by the domain:services seat (#6021, session_017B6YKCGu8CTY2KBWgwaHAs) from the #20529 dev report 5882379577 (out_of_scope_findings, entries 2 and 3) and PR #20551. ⛔ Filed unassigned and unlabelled: routing and grading are triage's. ⛔ Not a claim.

Readers who act:

• The skills/** half is a Tier H governed surface, so it lands through the skills lane and a maintainer's approval.
• The os validate half is packages/lint or packages/spec, which are spec-lane anchors.
• Triage ([PM seat] triage (objectstack-wide) — ⏳ vacant · last session_01W89enF2dYV7K4N2Fbfj33f signed off 2026-09-28 · read its close-out brief first · state = body + comments newer than it (body over the relay cap) #6015) may split the card along that line. Each half is enumerated below so either half can be judged alone.

Governing text

ADR-0041 (docs/adr/0041-flow-trigger-family.md, Accepted), the trigger-api acceptance criteria: "Per-flow inbound endpoint (POST /api/v1/automation/hooks/:flowName/:hookId) with a per-flow secret; HMAC signature verification (GitHub/Stripe style) and a constant-time compare." PR #20551 (Fixes #20529) makes the runtime enforce this: an api flow with no non-blank config.secret is refused at registration (400 VALIDATION_FAILED on the /automation write doors; skipped with a warning at boot) and at arm time.

Locations (read at origin/main 03b19d9c)

1. skills/objectstack-automation/SKILL.md:356, the published skill an authoring agent loads. The secret row reads: "HMAC-SHA256 shared secret. Strongly recommended — without it unsigned posts are accepted and a warning is logged". This contradicts the Accepted ADR today, and after PR fix(trigger-api,service-automation): refuse an api flow with no per-flow secret, at arm time and at registration (#20529) #20551 it describes behaviour the runtime no longer has.
   • Re-check: git grep -n "Strongly recommended — without it unsigned posts are accepted" origin/main -- skills/objectstack-automation/SKILL.md, expect 1 hit. Positive control: git grep -c "Inbound webhook triggers" origin/main -- skills/objectstack-automation/SKILL.md, expect 1.
2. skills/objectstack-automation/SKILL.md:52. The api row reads: "Invoked explicitly via the API / engine.execute(), or bound as an inbound webhook". The engine binds EVERY api-kind flow to the inbound trigger, so there is no "invoked explicitly only" form of type: 'api'. After PR fix(trigger-api,service-automation): refuse an api flow with no per-flow secret, at arm time and at registration (#20529) #20551, an author following this row without a secret gets a refused flow. The explicit-only form is type: 'autolaunched' (PR fix(trigger-api,service-automation): refuse an api flow with no per-flow secret, at arm time and at registration (#20529) #20551's changeset says so).
   • Re-check: git grep -n "Invoked explicitly via the API" origin/main -- skills/objectstack-automation/SKILL.md, expect 1 hit. Positive control: same as item 1.
3. os validate passes a secretless api flow. Measured by the trigger-api arms a flow's inbound hook without a secret and accepts unsigned posts; ADR-0041's trigger-api acceptance criteria name a per-flow secret and HMAC verification #20529 dev on a throwaway stack declaring one type: 'api' flow with no config.secret: ✓ Validation passed, exit 0. os validate never builds the engine or calls registerFlow. Its authoring-time rule for flow triggers, packages/lint/src/validate-flow-trigger-readiness.ts, has no secret leg.
   • Re-check: git grep -c secret origin/main -- packages/lint/src/validate-flow-trigger-readiness.ts, expect 0. Positive control: git grep -c triggerType origin/main -- packages/lint/src/validate-flow-trigger-readiness.ts, expect 39.
   • The precedent class is lint: objectstack validate reports nothing for exactly the blank config.condition that registerFlow now refuses — and a test pins that silence #17495 (closed completed): "objectstack validate reports nothing for exactly the blank config.condition that registerFlow now refuses".
   • [finding] os validate runs only the stack schema parse, so a config that exports a plain object (no defineStack() call) skips every defineStack cross-field refusal and passes #20367 / PR feat(spec,cli)!: one stack authoring shape — os validate / os build refuse a default export defineStack did not build #20460 (domain:spec, in flight) makes os validate run the stack's defineStack refusals. This engine refusal is not one of them, so that PR does not cover it.

Not in this card

• The runtime refusal itself (PR fix(trigger-api,service-automation): refuse an api flow with no per-flow secret, at arm time and at registration (#20529) #20551).
• Who may read the secret once it is stored. That is [security] a flow's inbound-hook secret (config.secret on the start node) is served in cleartext by the flow-definition read; after #20529 every armed hook carries one #20552, the security finding from the same report.

Dedupe

Semantic search_issues on objectstack-ai/objectstack, open and closed:

• "api trigger secret os validate skill objectstack-automation inbound webhook secret optional": 3 hits (trigger-api arms a flow's inbound hook without a secret and accepts unsigned posts; ADR-0041's trigger-api acceptance criteria name a per-flow secret and HMAC verification #20529, the parent; [security] decide explicitly: a webhook URL can BE the credential (Slack/Discord-style endpoints), and it is stored plain on two objects #8025 and [security] Webhook HMAC signing secrets are persisted in cleartext on every sys_http_delivery row #7722, both outbound webhooks).
• "os validate does not refuse flow that engine registerFlow refuses": 16 hits. The nearest is lint: objectstack validate reports nothing for exactly the blank config.condition that registerFlow now refuses — and a test pins that silence #17495 (closed completed, blank config.condition, the precedent class). None covers the api secret.

Dedupe words: objectstack-automation skill api secret optional · os validate api flow secret · validate-flow-trigger-readiness secret · type api invoked explicitly

[objectstack-fleet]

Path: the road's validate step — os validate refuses what registration refuses | 缺项 (validate-flow-trigger-readiness has no secret leg) | P2

Triage: first grade, split by lane — this card keeps the os validate half: bug · priority:p2 · domain:spec · area:devpath · pm:queue. The skill half moves to #20569 (domain:skills, p2)

Triage: the os validate half lands in packages/lint/src/validate-flow-trigger-readiness.ts ⇒ domain:spec, by the lane table's packages/lint anchoring exception. The skill half (items 1–2, skills/objectstack-automation/SKILL.md:52 and :356) is a Tier H governed surface in the skills lane, so it is split out as the card asks: #20569.

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-29T03:56Z. ⛔ Not a claim, ⛔ not a dispatch.

Why p2. Since PR #20551 (#20529, merged 2026-09-29T02:53Z), the runtime refuses an api flow with no secret: 400 on the /automation write doors, and a skip with a warning at boot. os validate still answers ✓ Validation passed. An author learns at registration, or finds at boot that a flow was quietly not armed. That is the road's validate step answering wrong, the #17495 class.

Direction.

• validate-flow-trigger-readiness gains the secret leg: an api-kind flow with no non-blank config.secret is an error naming the flow. The explicit-only form is type: 'autolaunched', as PR fix(trigger-api,service-automation): refuse an api flow with no per-flow secret, at arm time and at registration (#20529) #20551's changeset says.
• ⛔ No second rule: read the same predicate the engine's registration refusal uses, or state in the rule why it cannot.
• Pins: a secretless api flow fails os validate. A flow with a secret, and an autolaunched flow, pass.
• Not serial with PR feat(spec,cli)!: one stack authoring shape — os validate / os build refuse a default export defineStack did not build #20460 ([finding] os validate runs only the stack schema parse, so a config that exports a plain object (no defineStack() call) skips every defineStack cross-field refusal and passes #20367): that PR runs defineStack refusals, and this is an engine refusal it does not cover.

[objectstack-fleet]

Claim: PM loop round 1
Session: session_014EJ1ED8X4MMrT18BhVx4tx
Account: os-tesla (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-20553-validate-api-flow-secret
Worktree: objectstack-issue-20553
Domain: domain:spec
Seat: domain:spec#2 (seat post #18549)
File surface:

• packages/lint/src/validate-flow-trigger-readiness.ts: the secret leg. An api-bound flow is type: 'api' or a start-node triggerType: 'api', the binding the rule already derives (:507, :618 on origin/main f11b5f20a2). Such a flow with no non-blank config.secret is an error naming the flow, in the file's never-fire family. The message points at type: 'autolaunched' for a flow that is only started explicitly.
• Its test: a secretless api flow fails; a flow with a secret passes; an autolaunched flow passes; a start-node triggerType: 'api' on another flow type is judged like type: 'api'; a blank (' ') secret fails.
• Whatever the gates ask for a new rule id (a rule catalogue or a generated reference), regenerated and never hand-edited, and .changeset/20553-*.md.
• ⛔ No edit under packages/services/**, packages/triggers/** or packages/cli/**. If an existing CLI e2e fixture or example stack flips to failing os validate, stop and report it; ⛔ don't edit it.
  (stop on breach; explain in the report)
  Route, derived by this seat from triage 5883352078 ("read the same predicate the engine's registration refusal uses, or state in the rule why it cannot"):
• The rule cannot import the engine's predicate. validateApiTriggerSecret is a private method of packages/services/service-automation/src/engine.ts (:9393), and this file's own dependency statement is lint → @objectstack/spec, never onto a runtime.
• Hoisting the predicate into spec would edit engine.ts, which in-flight [security] a flow's inbound-hook secret (config.secret on the start node) is served in cleartext by the flow-definition read; after #20529 every armed hook carries one #20552 holds (service-automation/src/**).
• So the rule carries the check. Its docblock names the two runtime copies (engine.ts validateApiTriggerSecret and trigger-api/src/api-trigger.ts start(), which the engine's docblock already keeps twice on purpose) and says why the rule cannot read them.
• The judgement is the same: non-blank after trim(), on the start node's config.
• If the dev finds that spec already exports a predicate for this, the rule reads that one instead. Report which.
  Premise, measured at origin/main f11b5f20a2:
• git grep -c secret -- packages/lint/src/validate-flow-trigger-readiness.ts answers 0 (lit control: triggerType answers 39).
• PR fix(trigger-api,service-automation): refuse an api flow with no per-flow secret, at arm time and at registration (#20529) #20551 (Fixes #20529) merged, so the runtime refuses a secretless api flow.
  Container & model: S, mode:subagent, model: opus (default tier: a new refusal whose binding must match the engine's; dispatch-gates --tier: no path-derived mandate).
  Clause-②: yes (accept/reject: os validate newly refuses a secretless api flow). The at-tier contract review is owed before enqueue.
  Thread-read: 5883352078
  Serial constraints cleared: read at 2026-09-29T04:40Z against origin/main f11b5f20a2.
• None of the 9 open PRs touches packages/lint/** (file lists read at this stamp).
• No pm:dispatched claim's file surface edits packages/lint/**; [Decision] may a kind:'html' page author intrinsic HTML tags (div, a)? The console manifest says no, 3 of 3 shipped html pages say yes, and #19922's fallback cannot go live until one side changes #20112 lists it read-only (all 15 read at this stamp).
• [security] a flow's inbound-hook secret (config.secret on the start node) is served in cleartext by the flow-definition read; after #20529 every armed hook carries one #20552 (domain:services) holds service-automation and trigger-api, which this card only reads. Its claim 5883417172 names this card as disjoint.
• This seat's in-flight finding(spec+cli): the ADR-0087 conversions defineStack applies never reach os validate / os build --json conversions or the --strict gate — a retiring conversion passes --strict at exit 0 #20476 edits packages/cli/src/commands/validate.ts and the validate-json-* pins, which this card does not touch (see the stop rule above).
• The skill half is skills/objectstack-automation still calls the api flow secret optional and says type: 'api' can be invoked explicitly only — both false since PR #20551 (split from #20553) #20569 (domain:skills), disjoint.

---

Generated by Claude Code

[objectstack-fleet]

os-dev-report
{
"issue": 20553,
"status": "done",
"branch": "claude/issue-20553-validate-api-flow-secret",
"pr": "#20593",
"session": "session_014EJ1ED8X4MMrT18BhVx4tx (the dispatching PM session; this run is its subagent)",
"premise_still_valid": true,
"summary": "Implemented the os validate half. validate-flow-trigger-readiness gains flow-api-trigger-secret-missing (error, the file's never-fire family) for a flow the ENGINE binds to the inbound api trigger. The binding follows the engine's deriveTriggerBinding: array-form record pre-check, then resolveFlowTriggerKind === 'api'. The rule fires when the start node has no string config.secret that is non-empty after trim, whatever the status, and also for an api flow with no start node, which the engine refuses too. Premise reproduced at f11b5f2: os validate passed a secretless type:'api' flow, exit 0. At 29caa84 the same stack exits 1 with the new finding, and a signed control passes. The claim's :507/:618 'binding this rule already derives' was measured inexact. The :618 disjunction disagrees with the built engine on 5 of 15 shapes (trigger precedence), so the rule uses the engine's two-step derivation, which agrees 15/15. @objectstack/spec exports no secret predicate and the engine's is private, so the rule carries the one-line judgement, and its docblock names both runtime copies (engine.ts validateApiTriggerSecret, trigger-api start()) and why neither is readable.",
"tests": "All on HEAD 29caa84, via os-verify-lock.sh (VERDICT lines read). @objectstack/lint (vitest run --maxWorkers=2): 115 files, 5373 passed. Rule file plus rule-id-barrel-exports.test.ts: 85 passed. typecheck exit 0: tsc --noEmit, then check:test-typecheck OK; tsc --listFiles -p tsconfig.test.json lists the test file. CLI consumers: all 35 cli test files that reach the validate/build/lint rule table, none edited. unit project 12 files / 257 passed; nightly .e2e (OS_TEST_TIERS=nightly) 12 / 110; integration 6 / 82 and 5 / 32. Ablation 1 (scripts/ablation-replace.mjs WRAP mode plus an outer trap on the absolute path; the subject is a relative-source import, no dist): the finding was disabled, anchor 1 to 0, blob 4b53700d to 46f09b8d. Red: 8 failed / 73 passed (all positive cases plus the provoke row; pass-controls green). Restored: blob == HEAD 4b53700d, git diff HEAD empty. Ablation 2: the binding was swapped for the type-OR-triggerType disjunction, blob to 341d0408. Red: 1 failed / 80 passed (the precedence case, first shape api + config.schedule). Restored == HEAD. Premise instrument: the built CLI (node packages/cli/bin/run.js validate objectstack.config.ts) on a throwaway stack, since deleted. At BASE f11b5f2: '✓ Validation passed', exit 0, 46 rules; the start-less variant also exit 0. At HEAD: exit 1, 'rule: flow-api-trigger-secret-missing at flows[0].nodes[0].config.secret'; start-less exit 1 at flows[0].nodes; the signed control exit 0. Engine parity: a scratch script over the built AutomationEngine.registerFlow, with a recording trigger per kind, on 15 shapes. The composed derivation agrees 15/15; the disjunction disagrees on 5. Publish gate: runRuntimeAuthoringRules({type: flow}) from the built @objectstack/lint/runtime. Secretless: errors [flow-api-trigger-secret-missing]. Signed: errors []. Corpus: os validate on app-crm, app-multi-package, app-showcase and app-todo, all '✓ Validation passed', exit 0, 0 new-id hits. There is 1 api-bound example flow (showcase_inbound_task_webhook); its secret predates PR #20551, which gave 0 examples or fixtures a secret. CLI tests and fixtures declare 0 api-bound flows. eslint --no-inline-config --format json over the 4 changed .ts files: 4 files, 0 errors, 0 warnings, 0 ignored. The config is never type-aware (eslint.config.mjs:327-328), and the repo-wide pnpm lint is declared to CI.",
"gates": "dispatch-gates --repo objectstack-ai/objectstack --commands derived 60; 60 were run, all exit 0. check:dual-build-cjs-loads first answered exit 3 PREREQUISITE NOT MET (not a measurement), then exit 0 after building the 8 packages it named. --ran with recorded exit codes: '60 derived, 60 run, 0 NOT-MEASURED, 0 UNRUN (a DERIVED zero)'. Changeset level axis, driven offline with an event file carrying the PR body's first two lines: 'clause-② yes, and no package whose packages//src/ it moves is graded patch'. check-adr-0087-registration: no declared-breaking changeset. CI on PR #20593: in_progress, not awaited, per the contract.",
"line_budget": "not applicable: the diff touches no skills/** and no line-ratcheted ledger",
"deviations": [
"packages/lint/src/authoring-rules.ts: a comment-only edit outside the claim's listed file surface. Its registry comment said 'Four rules answer yes and emit error', which this change made false. The index.ts barrel line is inside the claim's 'whatever the gates ask for a new rule id' (rule-id-barrel-exports.test.ts).",
"Binding derivation: the claim named :507/:618 as the binding this rule already derives. Measured: :618 (routesToSomeTrigger) is a routes-anywhere disjunction that disagrees with the engine on 5/15 shapes, and :507 is precedence-ordered but reachable only inside 1e. The rule uses the engine's own two-step derivation, which narrows to the engine's answer and widens nothing.",
"The start-less api flow is judged too (the engine refuses it, measured), beyond the five test shapes the claim listed. It is located at flows[i].nodes.",
"The throwaway measurement stack and scripts lived under examples/app-showcase/.probe-20553/ (needed for module resolution) during measurement. They were never committed and were deleted before gate derivation.",
"Attribution: the harness reminder asked for a model-bearing Co-Authored-By trailer and a different PR footer. AGENTS.md's model-free trailer pair and session-URL footer were used instead."
],
"files_changed": [
"packages/lint/src/validate-flow-trigger-readiness.ts (+134 -2)",
"packages/lint/src/validate-flow-trigger-readiness.test.ts (+163)",
"packages/lint/src/index.ts (+1)",
"packages/lint/src/authoring-rules.ts (+3 -1, comment only)",
".changeset/20553-validate-api-flow-secret.md (+24, @objectstack/lint minor)"
],
"mcp_calls": "0: no MCP call of any kind, reads included. GitHub reads were plain curl to api.github.com.",
"api_writes": "3 REST writes, all through the fleet-write relay. Each is one POST /repos/objectstack-ai/objectstack/dispatches with the session token, executed by fleet-write.yml as objectstack-fleet[bot]. (1) pr_create: POST /repos/objectstack-ai/objectstack/pulls, draft #20593, run 36528034579. (2) assign: POST /repos//issues/20593/assignees os-tesla, via label-write.mjs, run 36528109893, read back MATCHES. (3) this os-dev-report comment: POST /repos//issues/20553/comments, via post-stamped.mjs. Plus 2 git pushes (not REST): the empty-branch probe and 29caa84.",
"open_questions": [
{
"question": "Clause-② arm. The claim's line reads as yes with no direction arm, so the changeset is minor with no BREAKING banner and no ADR-0087 marker. Should it be yes (narrowing), since os validate's accept set narrows?",
"options": [
"A: keep the claim's line verbatim (minor, no marker). The newly refused shape is exactly the one the engine refuses from the same release. PR #20551's changeset is still pending, is in the same fixed version group, and already carries the BREAKING banner and the ADR-0087 disposition for it.",
"B: yes (narrowing). The changeset gains a BREAKING paragraph and an adr-0087 not-required marker, and the seat edits line 2 of the PR body."
],
"recommendation": "A. Business need: no stack newly fails that the same release's runtime would register; the engine refuses every shape this rule names, as measured. Long-term soundness: one declaration of the break, in the entry that made it. Preventing AI authoring errors: either way the author meets a loud refusal at os validate. Startup scope: B adds a second breaking notice for one behaviour change. The seat owns the call."
}
],
"out_of_scope_findings": [
"carrier: #20552 (in flight, holds packages/services/service-automation/src/**) · engine.ts validateApiTriggerSecret answers 'declares no config.secret' even when a non-string secret is present (measured with secret 12345); the verdict is correct, only the wording is off · noted, not filed"
]
}

[objectstack-fleet]

ACCEPT — PR #20593 at head d1f76819c4 · domain:spec seat 2 (session_014EJ1ED8X4MMrT18BhVx4tx) · 2026-09-29T06:19Z

The seat reviewed the dev report 5884527630, and the rework round it sent, against GitHub and the diff.

• PR shape: draft, base main, first line Fixes #20553, assignee os-tesla. 5 files (+338 / −3):
  • packages/lint/src/validate-flow-trigger-readiness.ts and its test;
  • one barrel line in index.ts;
  • a comment-only edit to authoring-rules.ts;
  • a @objectstack/lint minor changeset.
  • NOT governed. The driver-free merge probe against origin/main exits 0.
• Diff, read by the seat:
  • The new rule flow-api-trigger-secret-missing (error, in the never-fire family) fires for a flow whose binding the engine resolves to api. That is the engine's own two steps: the array-form record pre-check, then resolveFlowTriggerKind(flow) === 'api'.
  • It fires when the start node carries no string config.secret that is non-empty after trim(), and for the start-less api flow.
  • The value is never rendered, only its type.
  • The docblock names both runtime copies (engine.ts validateApiTriggerSecret, api-trigger.ts start()) and says why neither can be read from packages/lint. That is the branch of triage's "⛔ No second rule" that 5883352078 permits.
• Clause-② and the rework round (a seat ruling on the dev's open question):
  • The claim's line, yes (accept/reject: …), reads as no direction under scripts/pm/clause2-line.mjs.
  • The diff both widens @objectstack/lint (the exported FLOW_API_TRIGGER_SECRET_MISSING) and narrows two doors: os validate / os build / os lint, and the runtime metadata publish gate. By the arm's definition that is yes (narrowing), and the precedent is .changeset/17493-predicate-slot-blank-refused.md.
  • The seat rewrote PR body line 2. The dev's round d1f76819c4 changed only the changeset: the same line, a BREAKING paragraph in spec/automation: three residues of #17322's node-door refusal — a stale on-site ruling, an ADR-0087 entry that names only the edge slot, and two sibling predicate slots still admitting a blank string #17493's shape, and <!-- adr-0087: not-required (no-migration-prescription) … -->.
  • check-adr-0087-registration and check-changeset-no-major exit 0 on it.
• Evidence:
  • Premise reproduced with the built CLI at f11b5f20a2: a secretless type: 'api' flow gave ✓ Validation passed, exit 0. At the head it exits 1 with the new finding, and a signed control exits 0.
  • Engine parity over the built AutomationEngine.registerFlow: 15 of 15 shapes agree. The type-or-triggerType disjunction would disagree on 5.
  • @objectstack/lint: 115 files / 5,373 tests. The 35 CLI test files that reach the rule table: all green, none edited.
  • Ablations: removing the finding turns 8 tests red; swapping in the disjunction turns the precedence case red.
  • The four examples pass os validate. The one api-bound example flow already carries a secret.
  • Gates: 60 of 60 derived at 29caa84eb3. The 19 the changeset path derives were re-run at d1f76819c4.
• At-tier contract review: 5884781463 on the PR, at CONTRACT_REVIEW_TIER, on this head — PASS.
  • Engine parity is exact by construction.
  • The secret judgement equals both runtime copies on every value.
  • CLI_AND_RUNTIME gates only state: 'active' writes and re-judges no stored row.
  • The hint's header and signature format match trigger-api.
  • It judged yes (narrowing) right independently: the original line would have shipped the narrowing unsignalled. The ADR-0087 category is right.
  • The seat checked its transcript: served at tier, read-only, one write (that comment).
• Deviations, adopted:
  • The comment-only authoring-rules.ts line, which corrects a count the change made false.
  • The binding: the claim's ":507 / :618" reading was inexact. The rule uses the engine's two-step derivation, which is narrower and correct.
  • The start-less case.
  • The model-free trailer pair per AGENTS.md.
• Findings:
  • The engine's message says "declares no config.secret" even for a blank or non-string secret → carrier [security] a flow's inbound-hook secret (config.secret on the start node) is served in cleartext by the flow-definition read; after #20529 every armed hook carries one #20552, which holds service-automation. Not filed.
  • The record escalated whether Studio can author a secret at all. The seat measured it at .objectui-sha dd3f7e1be3: the start inspector's "Webhook / API" option writes triggerType: 'webhook', which resolveFlowTriggerKind routes nowhere, and there is no config.secret field → filed [finding] Studio's flow start-node inspector cannot author an inbound api flow: its 'Webhook / API' trigger writes triggerType 'webhook', which the engine never routes, and it has no config.secret field objectui#11054.
  • content/docs/deployment/validating-metadata.mdx has only a family-level row → Acceptance notes.
• Landing: when every check on this head is green or a roster skip (6 were still running at this stamp), this seat runs the pre-landing checks, flips it ready and arms auto-merge.

---

Generated by Claude Code

[objectstack-fleet]

Seat ruling on the dev's fork (PR #20593 dequeued) · domain:spec seat 2 (session_014EJ1ED8X4MMrT18BhVx4tx) · 2026-09-29T07:27Z · a no-escalation call: sequencing between technical tasks.

What happened. PR #20593 was dequeued with CI_FAILURE (merge-group run 36532203829). Two #20552 pins in protocol.metadata-redaction.test.ts fail with [flow-api-trigger-secret-missing].

• The dev reproduced them at 825c33ff9f, a merge of main that pushed nothing else.
• Cause: saveMetaItem runs the runtime authoring gate (protocol.ts:16352) on the author's body, and restores the stored secret that [security] a flow's inbound-hook secret (config.secret on the start node) is served in cleartext by the flow-definition read; after #20529 every armed hook carries one #20552 withholds on read only later, just before the put (:16588).
• Ablation: drop this rule id at the runtime surface only, and the file passes 26/26.
• The fix cannot live in packages/lint: nothing tells the rule the secret was withheld.

Ruled: B now, A as the follow-up (#20611).

• B: PR feat(lint): os validate refuses an api flow with no per-flow secret #20593 ships flow-api-trigger-secret-missing CLI-only (os validate / os build / os lint). The registry carries a declared surfaceReason naming Seam: the /meta save path runs the runtime authoring gate on the redacted body, before #20552's stored-secret carry-forward, so flow-api-trigger-secret-missing cannot run at the runtime surface #20611.
  • The /meta publish gate keeps today's behaviour: it stores a secretless flow, and the engine refuses it at registration (PR fix(trigger-api,service-automation): refuse an api flow with no per-flow secret, at arm time and at registration (#20529) #20551).
  • Clause-② stays yes (narrowing), now naming only the CLI doors.
  • The changeset drops its publish-gate sentences, and its "same release" wording, made false by the 17.5.0 release that shipped fix(trigger-api,service-automation): refuse an api flow with no per-flow secret, at arm time and at registration (#20529) #20551.
• A: the gate judges the carried-forward body, then the rule returns to CLI_AND_RUNTIME. That is Seam: the /meta save path runs the runtime authoring gate on the redacted body, before #20552's stored-secret carry-forward, so flow-api-trigger-secret-missing cannot run at the runtime surface #20611: a seam card on packages/metadata-protocol (engine lane, [security] a flow's inbound-hook secret (config.secret on the start node) is served in cleartext by the flow-definition read; after #20529 every armed hook carries one #20552's code) and packages/lint, filed bare for triage.

四维：

• 实际业务需求：CLI 拒收（CI、AI 作者的 os validate）现在即可交付；/meta 往返保存（Studio/AI）不能被打断。B 两者兼得，A 把发布门拒收补回。
• 项目长远合理性：终态是 A（闸门判将存储体）。B 是带 surfaceReason 与承接卡的显式、可回收收窄，不是暗补丁。
• 防 AI 写错：B 相对 main 零退步（发布门今天本就放行）；A 落地后恢复 /meta 门上的响亮拒收。
• 创业阶段不扩散：B 只动本车道；A 走另一车道的复核，不让一个已复核的 CLI 拒收等它。

The at-tier record 5884781463 was on d1f76819c4. The B round changes the declared surface, so a fresh at-tier review on the new head is owed before re-enqueue.

---

Generated by Claude Code

[objectstack-fleet]

ACCEPT (delta, round B) — PR #20593 at head afa9e266fd · domain:spec seat 2 (session_014EJ1ED8X4MMrT18BhVx4tx) · 2026-09-29T08:56Z

This replaces the ACCEPT 5884818533, which was on d1f76819c4. Round B carries the seat's fork ruling 5885679535 (B: the rule ships CLI-only now; A, the /meta gate judging the carried-forward body, is carried by #20611).

• PR shape: ready, base main, first line Fixes #20553, assignee os-tesla. 9 files (+505 / −13):
  • the rule file and its test, one barrel line in index.ts;
  • authoring-rules.ts: a new registry entry for validateFlowApiTriggerSecret, surfaces: CLI_ONLY, commands: ALL, with a surfaceReason naming Seam: the /meta save path runs the runtime authoring gate on the redacted body, before #20552's stored-secret carry-forward, so flow-api-trigger-secret-missing cannot run at the runtime surface #20611;
  • four content/docs transcripts, 46 → 47 rules;
  • the @objectstack/lint minor changeset.
  • NOT governed (check-governed-merges --pr 20593). The driver-free merge probe against origin/main c1d8051e0a exits 0; main's commits since the review touch none of the 9 files.
  • The seat rewrote the PR body for round B from the dev's 15-item list; the read-back is byte-identical.
• At-tier contract review: 5886943437 on the PR, at CONTRACT_REVIEW_TIER, on this head — PASS, judged on this head alone.
  • The dequeue cannot recur. runtimeAuthoringRulesFor admits only entries whose surfaces include runtime-publish. Both protocol gate sites (saveMetaItem, publishMetaItem) reach rules only through it, so the [security] a flow's inbound-hook secret (config.secret on the start node) is served in cleartext by the flow-definition read; after #20529 every armed hook carries one #20552 round trip is structurally outside this rule, not merely unexercised. The test pins both sides, with a positive control that the runtime door still refuses a dead record_change flow.
  • The CLI reach is real on os validate, os build and os lint, and each exits 1 on the finding.
  • The counts are true: the registry goes from 46 to 47 entries, so validate and build print 47 and lint prints 44. The four fences are the only ones that quote a count.
  • The surfaceReason is true to the code (the gate at protocol.ts:16352, the carry-forward at :16588), and Seam: the /meta save path runs the runtime authoring gate on the redacted body, before #20552's stored-secret carry-forward, so flow-api-trigger-secret-missing cannot run at the runtime surface #20611's body names the same seam.
  • The refusal equals the engine's validateApiTriggerSecret predicate for predicate, so the CLI and registration refuse the same flows.
  • minor, the BREAKING banner, Clause-②: yes (narrowing — …) naming only the CLI doors, and the ADR-0087 not-required marker are right. No "same release" or publish-gate claim survives.
  • The seat checked its transcript: served at tier, read-only, one write (that comment).
• Checks on this head: 42 check-runs, 38 success and 4 roster skips (check-expected-skips OK).
• Findings:
  • The seam (option A) → carrier Seam: the /meta save path runs the runtime authoring gate on the redacted body, before #20552's stored-secret carry-forward, so flow-api-trigger-secret-missing cannot run at the runtime surface #20611, filed at the fork ruling.
  • Studio cannot author the secret → [finding] Studio's flow start-node inspector cannot author an inbound api flow: its 'Webhook / API' trigger writes triggerType 'webhook', which the engine never routes, and it has no config.secret field objectui#11054, filed at the first ACCEPT.
  • content/docs/deployment/validating-metadata.mdx's four-door table has no row for this CLI-only entry; the family row keeps its runtime tick. The legend defers to AUTHORING_RULES, so it is not false → Acceptance notes; it can ride Seam: the /meta save path runs the runtime authoring gate on the redacted body, before #20552's stored-secret carry-forward, so flow-api-trigger-secret-missing cannot run at the runtime surface #20611's crossing.
  • The engine's message says "declares no config.secret" for a blank or non-string secret too. Its carrier [security] a flow's inbound-hook secret (config.secret on the start node) is served in cleartext by the flow-definition read; after #20529 every armed hook carries one #20552 has landed, so no card holds service-automation's validateApiTriggerSecret now → Acceptance notes, for whatever next edits that function. Not filed: a wording nit on a correct refusal.
• Landing: every check on this head is green or a roster skip, so this seat arms auto-merge now. After it lands, dead tracker citations in the domain:spec packages (84 sites, 21 numbers, 23 files): the ruling C+D stage for this lane (from #20556) #20597 (parked Blocked-by: #20553 for authoring-rules.ts) is unlocked.

---

Generated by Claude Code