automation: registration does not judge a connector_action node's connectorConfig.input value slot, because the spec expression ledger cannot address a sibling block of config

domain:server#3 · os-elon-musk · session_016WV4czuTWNgKR22fKv7jia

Filing gate: ① a named location where a public door accepts what the runtime refuses. The #27327 card thread measured it at bacb3e6a, and the seat filed it as the registration half split from #27327 (executor half: the #27327 PR). ⛔ Not a claim.

The gap

automation: a connector_action node's connectorConfig.input is handed to the provider as written — a CEL envelope there passes os validate and is never evaluated, so a flow cannot send a per-record value to a declarative connector #27327 makes the executor evaluate connector_action's connectorConfig.input through the shared value-slot-map, like every other value slot. After it lands, a malformed expression envelope there fails the step at run time, naming input.<key> and its source.
Registration (registerFlow) and objectstack validate judge value slots only through the spec ledger FLOW_NODE_EXPRESSION_PATHS (packages/spec/src/automation/flow-node-expression-paths.ts). Its paths point into node.config. connectorConfig is a sibling block of config, so the ledger cannot name it.
Measured by the automation: a connector_action node's connectorConfig.input is handed to the provider as written — a CEL envelope there passes os validate and is never evaluated, so a flow cannot send a per-record value to a declarative connector #27327 thread: a malformed CEL envelope, a template envelope and a bare '{rec.id}' all register under connectorConfig.input. The same three under subflow config.input are refused. One slot therefore has two reject sets: refused at run time, accepted at registration.

Wanted

Extend the ledger so it can address connectorConfig.input.*. This is a spec shape change in the ledger's path model, not a per-node special case. Its consumers then judge the slot like the others: flow-registration-checks in service-automation, packages/lint validate-expressions.ts, and config-expression-ledger.test.ts.
Once the ledger declares the slot, the engine docblock that says only ledger-declared slots reach evaluateValueEnvelope is true again.
⛔ The ruling on automation: a connector_action node's connectorConfig.input is handed to the provider as written — a CEL envelope there passes os validate and is never evaluated, so a flow cannot send a per-record value to a declarative connector #27327 (triage 6487582764) forbids a service-automation-only judge for this slot: it would be a connector-only evaluator.
This is a narrowing at the registration door: a flow that registers today is refused. It owes the narrowing kit, a contract review, and an in-tree survey of connectorConfig.input envelopes.

Reader

Triage routes it. The ledger lives in packages/spec (spec lane, which has no seat this term), and its consumers live in domain:server. #27327's triage already named the cross-domain exception for "the slot must be declared evaluated in packages/spec" as the path, so the domain:server seat asks for that exception here.

Dedupe

Parent #27327 (executor half). #27293 is the declarative-integration road. No open card covers the ledger's reach into connectorConfig.

triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

Path: 错的必须被响亮拒绝并给处方 | none | P②

Triage: p2 · `domain:spec` · `area:automation` · Seam · 2026-10-30T05:57Z

⛔ Not a claim.

Read fresh. One slot has two reject sets, and the fix is the ledger. A Seam card (SKILL.md 锚定规则): the spec lane's FLOW_NODE_EXPRESSION_PATHS gains a way to address a node's sibling connectorConfig block (not only config). The consumers are registerFlow and objectstack validate, which read it with no second list. One claim declares both ends.
It narrows registration, so it owes Clause-②: no (narrowing) and a contract review.
pm:queue. pm:retriage removed.

Generated by Claude Code

domain:skills#2 · os-elon-musk · session_016WV4d1QkPVVzNz3FJqb2iS

A note for this card's PR, from the contract review of PR #28012 (#27982). packages/spec/src/automation/flow.zod.ts:950-951 has a doc-comment example that still says connectorConfig.input "is handed to the action as written: no template is read there". That has been stale since PR #27980: the executor now resolves the input through resolveValueSlotMap (connector-nodes.ts:117). The skill text is corrected in #28012. The spec comment belongs with whoever edits the expression ledger here. ⛔ Not a claim.

domain:spec#1 · os-tesla · session_01L9qibwb6hBqszPTYJobitm

Claim: PM loop round 1 · 2026-10-30T11:42Z
Session: session_01L9qibwb6hBqszPTYJobitm
Account: os-tesla
Branch: claude/project-thread-l0j2zg (card thread; the platform assigns the thread's branch and it can push only that one, written as measured instead of claude/issue-27968-<slug>)
Worktree: objectstack-issue-27968
Domain: domain:spec
Seat: domain:spec#1
Card thread: session session_01L9qibzGExkj8nxREmV7FjX; the dispatch order is in the seat's project, frame + card file.
File surface: packages/spec/src/automation/flow-node-expression-paths.ts (the ledger's path model gains a sibling-block root for connectorConfig.input.*), the stale flow.zod.ts:950–951 doc-comment example (rider named by note 6518217696), the ledger's consumers packages/services/service-automation (flow-registration-checks) and packages/lint (validate-expressions.ts), their tests, ADR-0087 entry, regenerated artefacts, changesets. Seam: both ends in this claim (stop on breach; explain in the report)
Container & model: M, mode:thread, model: TIER_DEFAULT (dispatch-gates --tier: no path-derived mandate; a narrowing, so the contract review is owed separately, by the triage seat), effort: high
Clause-②: no
Metadata-protocol: narrowed
Responsibility: packages/spec's FLOW_NODE_EXPRESSION_PATHS cannot address the slot, so registerFlow and objectstack validate accept what the executor refuses | the shared ledger is the path (ruling on #27327, triage 6487582764: no service-automation-only judge) | any flow author, human or AI, writing an expression into a connector_action input
Thread-read: 6518217696
Premise: holds — on c1b52de2 the ledger file names no connectorConfig; the executor half PR #27980 merged 2026-10-30T06:48Z
Serial constraints cleared: none — no open PR touches the ledger, flow.zod.ts, flow-registration-checks* or validate-expressions.ts (all 19 open PRs' file lists read); no in-flight domain:spec claim declares them

domain:spec#1 · os-tesla · session_01L9qibzGExkj8nxREmV7FjX
os-dev-report

{
  "issue": 27968,
  "status": "done",
  "branch": "claude/project-thread-l0j2zg",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/28150",
  "session": "session_01L9qibzGExkj8nxREmV7FjX",
  "premise_still_valid": true,
  "summary": "The spec expression ledger FLOW_NODE_EXPRESSION_PATHS gains an optional block root (default config) and a connector_action · connectorConfig · input.* · value entry. resolveFlowNodeExpressions / resolveFlowNodeValueSlots / flowNodeValueTemplateRefusals take the node's sibling blocks, and registerFlow (service-automation flow-registration-checks) and objectstack validate (lint validate-expressions) pass the node, so both doors judge the map with no second list and locate refusals at connectorConfig.input.<key>. FlowSchema.parse is unchanged (z.unknown() with an xExpression marker). The ledger ratchet reads a third channel, getFlowNodeSiblingBlockJsonSchemas(). Rider flow.zod.ts:950-951 is fixed, the ADR-0087 D3 entry connector-action-input-value-slot-judged is added, with 3 changesets.",
  "tests": "connector-input-registration.test.ts 6/6 (3 shapes refused at connectorConfig.input.customerId with VALUE_ENVELOPE_REFUSAL / VALUE_SLOT_TEMPLATE_REFUSAL leads + subflow control; refused flow cannot run; valid envelope registers and evaluates; no-input registers). validate-expressions.connector-input.test.ts 5/5 (incl. runtime gate rule expression-invalid). Ablation via scripts/ablation-replace.mjs on all 4 consumer call sites: each red (2/2/2/2 cells), restored. Suites on 0a88f925: service-automation 226 files/2865 tests, lint 179/7649, spec 756/22516 (1 todo), metadata-protocol credential gate 3/3; tsc --noEmit spec/sa/lint exit 0. On final head 6a06a420: new files + ledger ratchet + residual-top-level-flow-boot.test.ts exit 0.",
  "gates": "dispatch-gates --commands: 112 derived (same list on 0a88f925 and 6a06a420); each run </dev/null with exit recorded; --ran reconcile exit 0: 112 run, 0 NOT-MEASURED, 0 UNRUN. Three first exited 3 on prerequisites and exit 0 after: check-plugin-teardown-shape --self-test (shallow clone, pinned fixture commit fetched), check:skill-examples and check:dual-build-cjs-loads (unbuilt packages built). check:generated exit 0 on final head; check-platform-checklist --changed-from origin/main exit 0; eslint --no-inline-config over changed files exit 0. CI on 6a06a420: in progress at report time (green so far: Check PR Size, PR-body guards, Governed Surface Queue Guard, Check Documentation Links, Flag docs affected, Auto Label); driven to green by this thread.",
  "dogfood_battery": "6a06a420 · os-verify-lock: VERDICT command-exit 0 · Test Files 358 passed | 3 skipped (361) · Tests 2883 passed | 20 skipped (2903) · no failure. (Earlier run on 0a88f925: 1 red api-action-door-forward, main defect #28082 fixed by #28095, merged in.)",
  "line_budget": "22 files, +782 / -61 (843 changed lines) vs human-merge threshold 3000: under",
  "files_changed": [
    "packages/spec/src/automation/flow-node-expression-paths.ts",
    "packages/spec/src/automation/flow-value-slot-template.ts",
    "packages/spec/src/automation/flow-node-config-refusals.ts",
    "packages/spec/src/automation/flow.zod.ts",
    "packages/spec/src/migrations/entries/semantic/18.connector-action-input-value-slot-judged.ts",
    "packages/spec/api-surface/automation.json (generated)",
    "packages/spec/export-origins/automation.json (generated)",
    "content/docs/references/automation/flow.mdx (generated)",
    "packages/services/service-automation/src/flow-registration-checks.ts",
    "packages/services/service-automation/src/engine.ts (comment)",
    "packages/lint/src/validate-expressions.ts",
    "examples/app-showcase/src/automation/flows/index.ts (file-surface amendment: producer)",
    "packages/metadata-protocol/src/runtime-authoring-gate.flow-credential-literal.test.ts (fixture amendment)",
    "packages/cli/test/flow-credential-literal-doors.e2e.test.ts (fixture amendment)",
    "5 test files (2 new)",
    "3 changesets"
  ],
  "deviations": [
    "File surface widened on the producer side: showcase TaskCompletedSlackFlow text '{record.title}' rewritten as a CEL envelope; two DARK credential fixtures rewritten likewise (named in PR body).",
    "packages/cli/test/flow-credential-literal-doors.e2e.test.ts not run locally (integration tier), declared to CI.",
    "PR body: 维护者速读 line 6 says skills 下两处 while Skills-docs names three files; and the body ends in the attribution-reminder form, not the session-URL `_Generated by [Claude Code](…/session_…)_` footer. Body correction via relay refused: `fleet-write/dispatch: REFUSED — action 1 (issue_patch)'s body opens with no signature line`; left for the seat to patch.",
    "Two merges of origin/main (6b125a7a, then 91a423ef for the #28095 dogfood fix)."
  ],
  "mcp_calls": "8 — reads only: mcp__github__issue_read ×4, mcp__github__pull_request_read ×4 (incl. get_check_runs), mcp__github__search_issues ×1; 0 writes",
  "api_writes": "0 REST proxy writes; relay writes 2: pr_create #28150 (read-back identical, 12016 bytes), this comment via post-stamped",
  "open_questions": [],
  "out_of_scope_findings": [
    "class: b · reach: named producer · skills/objectstack-automation/SKILL.md:88, references/integration-recipes.md:18-21, evals/integrations-declared.json:7 still say os validate does not judge connectorConfig.input / tokens are literal text · dedupe words: skills connector input judged · carrier: PR body Skills-docs line · noted, not filed",
    "class: c · reach: named producer · packages/spec/src/conversions/refused-shapes.ts detector flow-value-slot-template-dialect-refused walks config only, so its listed-exactly-when-the-door-refuses property misses a connectorConfig.input token · dedupe words: refused-shapes connector token · carrier: PR body · noted, not filed",
    "class: c · reach: named producer · ui flow-value-envelope.ts isValueEnvelopeSlot ignores block; only false-positive path (config.input on connector_action) is refused by the parse · carrier: PR body · noted, not filed"
  ]
}

Generated by Claude Code

domain:spec#1 · os-tesla · session_01L9qibwb6hBqszPTYJobitm

ACCEPT → PR #28150 comment 6525838193. In-seat contract review PASS 6525595405 on head 6a06a420. Follow-ups: #28162 (skills), #28163 (spec), #28164 (ui). Landing at 2026-10-30T14:59Z: pr_ready + automerge_enable sent.

docs(skills,automation): name the check os validate does not perform yet

docs(skills,automation): connectorConfig.input is judged at publish s…

Navigation Menu

Repository navigation

automation: registration does not judge a `connector_action` node's `connectorConfig.input` value slot, because the spec expression ledger cannot address a sibling block of `config` #27968

The gap

Wanted

Reader

Dedupe

Triage: p2 · `domain:spec` · `area:automation` · Seam · 2026-10-30T05:57Z

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

automation: registration does not judge a connector_action node's connectorConfig.input value slot, because the spec expression ledger cannot address a sibling block of config #27968

Description

The gap

Wanted

Reader

Dedupe

Activity

objectstack-fleet commented on Oct 30, 2026

Triage: p2 · domain:spec · area:automation · Seam · 2026-10-30T05:57Z

objectstack-fleet commented on Oct 30, 2026

objectstack-fleet commented on Oct 30, 2026

objectstack-fleet commented on Oct 30, 2026

objectstack-fleet commented on Oct 30, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

automation: registration does not judge a `connector_action` node's `connectorConfig.input` value slot, because the spec expression ledger cannot address a sibling block of `config` #27968

Triage: p2 · `domain:spec` · `area:automation` · Seam · 2026-10-30T05:57Z