lsm / HyperNeo / 31140459860 / 9

40%

dev: 40%

push

github

feat: MCP parity for goal schedule editing + Forge policy (#2384)

* feat(space): in-place recurring goal schedule editing + Forge policy MCP parity

Close the UI↔MCP edit-parity gap for goal check-in schedules and Forge scope
policy. Recurring goal cadence (cron + timezone) can now be edited in place
through update_goal / spaceGoal.update / the UI dialog without recreating the
goal, preserving identity, activeTaskId, pendingNextRun, history, and Forge
linkage. The stale pending fire job is cancelled and a fresh one enqueued
atomically; paused goals validate config now and apply it on resume. Add/remove
schedule semantics are defined. update_forge_scope now supports policy_patch
(deep-merge via mergeEvolutionPolicy, matching the UI) and episode_judge_provider.

* test(space): regression tests for goal schedule editing + Forge policy parity

Cover the parity gap end-to-end: in-place cron update (twice daily → hourly)
preserving identity/activeTaskId/pendingNextRun/history with exactly one new
fire job; timezone recompute; paused-schedule edit + resume cadence; add/remove
schedule; schedule edit while a task is active; invalid-cron rejection; omit =
no change. MCP update_goal schedule edits + cross-space rejection, and
update_forge_scope policy_patch deep-merge + episode judge provider. Web dialog
schedule pre-fill and conditional payload. Adds job_queue to the tools test DB.

* docs(space): add Goal/Forge UI↔MCP parity matrix

Document the UI↔MCP edit-parity contract, the schedule-edit and policy_patch
changes, semantics, and deferred follow-up parity groups.

* fix(space): address review — atomic goal updates, Forge validation parity, audit cadence

P1: wrap updateGoal mutations in a transaction so a status change + invalid
cron rolls back the schedule pause instead of silently disabling check-ins.
Honor deleteSchedule's CAS result on schedule removal (fail rather than orphan
an active schedule that lost the pending-job race). Route update_forge_scope... (continued)

1776 of 37141 branches covered (4.78%)

Branch coverage included in aggregate %.

6149 of 46108 relevant lines covered (13.34%)

3.58 hits per line