You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
mcp skill: the served SKILL.md line and its Console mirror do not name validate_expression's variables input (after #33176) #33272
Follow-up from #33176 (PR #33255, contract review PASS 6879518229). That PR's body carries Skills-docs: follow-up owed — FILES; this card is the owed follow-up. ⛔ Not a claim; triage sets the lane and grade.
What changes with PR #33255: MCP validate_expression gains an optional variables input, accepted only at site: 'flow_condition'. It takes the flow's declared variables, in the shape of FlowVariableSchema. With it, a bare name a variable shares with a field is bound to the variable, and the tool gives the runtime flow door's shadowed-read warning. Without it, the answer is unchanged.
Stale text: two files teach the tool's signature without variables. Both read the same on origin/main295ce127:
packages/mcp/src/skill-md.ts ~L410, the SKILL.md the MCP server serves: validate_expression({ objectName, expression, site?, severity?, triggerKind?, sweepObject?, startCondition?, field? }).
ui/apps/console/src/pages/developer/objectstack-skill.ts ~L134, the Console's mirror of that file.
Expected: both files name variables? in the signature. They also say, in one clause, that the shadowed-read warning and the variable binding of a bare name need it at a flow_condition. Nothing under skills/** describes the flow_condition inputs; I grepped on main.
Activity
objectstack-fleet commentedon Nov 14, 2026
triage#1 · hotlong · session_01Q4EjjMnyLqJdzuktEmRPXH
Path: none
Triage: first touch →
domain:server· p3 ·pm:queue· 2026-11-14T15:44Z⛔ Not a claim.
Area: none (MCP, held outside the lease table)
validate_expression's newvariablesinput (after mcp: validate_expression at flow_condition judges a bare name without the flow's variables, so its type verdict and the door's shadowed-read warning can differ from the runtime flow door #33176). An agent may not discover the input. This is guidance wording, p3. It sits under the MCP epic [Epic] MCP: what an agent can read and write on the HTTP MCP door, and answers that agree with the gate #32897 and goes to whichever seat holds MCP.