@lightcone-ai/daemon 0.22.0 → 0.22.1

package/mcp-servers/official/media-tools/index.js

@@ -267,9 +267,9 @@ server.tool(
 
 // ── compose_video_v2 (migrated from chat-bridge) ──────────────────────────
 // Tool-level enforcement of the standard chain: TTS-bearing segments require
-// plan_video_segments to have run earlier in this session. Without it manual
-// dwell/duration math has repeatedly produced misaligned subtitles, silent
-// tails, and re-records (Task #25/#26 trial).
+// plan_video_segments to have run earlier in this session. Without it,
+// hand-written dwell/duration math has repeatedly produced misaligned
+// subtitles, silent tails, and full re-records in production runs.
 server.tool(
   'compose_video_v2',
   'Compose video(s) from a list of segments using ffmpeg. Each segment has a visual source (image / scroll / '

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lightcone-ai/daemon",
-  "version": "0.22.0",
+  "version": "0.22.1",
   "type": "module",
   "main": "src/index.js",
   "bin": {

package/src/_vendor/video/recorder/plan-executor.js

@@ -329,6 +329,15 @@ function paramsForAtom(atomName, phase, fallbackFromY) {
 }
 
 // Phase fields → macro params. Macros validate their own inputs.
+// Number(null) === 0 (a JS gotcha) — guard explicitly so a normalize step
+// that fills missing fields with `null` (see normalizeSectionAsPhase) doesn't
+// trick `Number.isFinite` into accepting a phantom zero.
+function optionalFiniteNumber(value) {
+  if (value == null) return undefined;
+  const n = Number(value);
+  return Number.isFinite(n) ? n : undefined;
+}
+
 function paramsForMacro(macroName, phase, fallbackFromY) {
   const durationMs = resolveDurationMs(phase, null);
   const targetY = resolveTargetY(phase, null);
@@ -337,8 +346,8 @@ function paramsForMacro(macroName, phase, fallbackFromY) {
     target_y: targetY,
     duration_ms: durationMs,
     from_y: fromY,
-    transition_ms: Number.isFinite(Number(phase.transition_ms)) ? Number(phase.transition_ms) : undefined,
-    transition_ratio: Number.isFinite(Number(phase.transition_ratio)) ? Number(phase.transition_ratio) : undefined,
+    transition_ms: optionalFiniteNumber(phase.transition_ms),
+    transition_ratio: optionalFiniteNumber(phase.transition_ratio),
     transition_curve: phase.transition_curve,
     amplitude_px: phase.amplitude_px,
     oscillate_period_ms: phase.oscillate_period_ms,

package/src/tools/record-url-narration.js

@@ -87,10 +87,11 @@ function assertPipelineCompliance(plan) {
 // would show 投递入口 / 二维码 / contact info, which violates the recruitment
 // content policy (see fragments.md frag.short.recruitment_url_mode_policy).
 //
-// Discovered after Task #25 v1 ended up dwelling on FunPlus's QR/投递 area:
-// the agent's plan declared target_y=2180 with dwell_ms=8500 without checking
-// what content lived at that pixel position. This is a prompt-level rule
-// that's been ignored often enough that we enforce it at the tool layer.
+// Origin: in production runs the agent's plan repeatedly declared a target_y
+// without checking what content lived at that pixel position, and ended up
+// dwelling on QR codes / 投递 entries / 联系方式. The prompt-level rule
+// requiring `target_y_content_label` has been ignored often enough that we
+// enforce it at the tool layer instead.
 const FORBIDDEN_REGION_PATTERNS = [
   /二维码/, /扫码/, /扫一扫/,
   /投递入口/, /投递方式/, /投递通道/, /投递渠道/, /报名入口/, /报名方式/,

package/src/upload-job-manager.js

@@ -36,10 +36,10 @@ export const PART_RETRY_BASE_MS = 1_000;             // 1s, 3s, 9s
 export const TERMINAL_JOB_TTL_MS = 7 * 24 * 3600 * 1000;     // sweep done/dead_letter after 7 days
 export const HOUSEKEEPING_INTERVAL_MS = 6 * 3600 * 1000;     // run housekeeping every 6h
 // Per-PUT timeout — Node's fetch has no overall request timeout. Without this
-// a stalled COS connection wedges the chunk loop forever (observed during the
-// first Task #25 upload: chunk 1 PUT hung 7+ minutes with no progress, no
-// error). 5 minutes covers slow networks for an 8MB chunk (~25kB/s floor)
-// while still letting failures surface to the chunk-level retry loop.
+// a stalled COS connection wedges the chunk loop forever (observed in
+// production: a chunk PUT hung 7+ minutes with no progress and no error).
+// 5 minutes covers slow networks for an 8MB chunk (~25kB/s floor) while
+// still letting failures surface to the chunk-level retry loop.
 export const PUT_REQUEST_TIMEOUT_MS = 5 * 60 * 1000;
 
 function nowIso() { return new Date().toISOString(); }