#1199 stage 14: validation refuses what submit and run used to refuse late #1215

Activity

1. dkackman

   added

   owner:testerTester's turn to actTester's turn to act

   status:fixed-pending-verifyImplementer fixed, awaiting tester verificationImplementer fixed, awaiting tester verification

   stageA child issue: one stage of a featureA child issue: one stage of a feature

   target:lem

   on Nov 7, 2026
2. dkackman

   marked this as blocking on Nov 7, 2026

   • Long-form media: one playbook, measured levers, quality-first defaults for pieces longer than one clip #1199
3. dkackman commented on Nov 7, 2026

   

   dkackman

   on Nov 7, 2026

   OwnerAuthor

   More actions

   Verified by tester claude-opus-5-5 (provider anthropic) against lem develop @ 85bcd33, workspace bench.

   There are no pending: #1215 cases in any regression-suite-*.md, so the acceptance was the stage's own "Observe over MCP" and its acceptance intent.

   Validate and submit agree on an argument that needs coercion (templates/text-to-sound-effect):

   • steps: 0.5 (the variable is an integer by its default). validate_workflow returns valid:false at arguments.steps: "steps 0.5 would be realized as 0: this variable is typed integer by its default; declare its default as a float (e.g. 0.0) to accept fractional values". run_workflow with the same arguments refuses with the identical message. Nothing was queued.
   • steps: "abc". Validate and run_workflow both refuse with "Cannot convert variable 'steps' value 'abc' to type int". Nothing was queued.
   • steps: 20.0, duration: "3". Validate passes (valid:true), and checks both arguments, so a whole float and a numeric string still coerce.

   An oversize animatic is refused at validate (templates/animatic, boards asset:bench/board_{1,2,3}.png at 960x544, soundtrack asset:bench/narrator.wav):

   • durations [100,100,100], fps 60. Validate refuses at steps[0].task.arguments.images: "18000 frames of 960x544 (26.3 GiB), over the 4 GiB in-memory frame budget, which holds 2741 frames ... lower 'fps' to 9 or below ...". The message names the budget and a lower fps.
   • Boundary check: fps 9 (2700 frames) gives valid:true. fps 10 (3000 frames, 4.4 GiB) is refused with the same message. The suggested fps really does fit.
   • fps 10 through run_workflow is refused with the identical message, so submit agrees.
   • durations [600,600,600], fps 60. Both the 600 s clip limit and the 36000-frame limit are reported at once.

   The list variables (boards, durations) were accepted as written in every call.

   I did not separately exercise the 'Image' object is not subscriptable variables-pass fix. No call this session reached that path.
4. dkackman

   added

   status:verifiedTester confirmed the fix via a real MCP callTester confirmed the fix via a real MCP call

   and removed

   status:fixed-pending-verifyImplementer fixed, awaiting tester verificationImplementer fixed, awaiting tester verification

   on Nov 7, 2026
5. dkackman

   closed this as completedon Nov 7, 2026