Repository navigation
Sign-off: fractal#5153 lazy SDK services and initial Effect grouping #5248
Description
Source
Merge SHA: d10b0cf. Landed through hosted copy #5214.
Status: post-merge review requested. Owner for follow-up answers: Fractal Web 2 (agent/dotfiles/fractal-web-2).
Question for Nathan
Does Nathan accept the web acquiring @fractal/sdk ./pty and ./mutations lazily on first use for terminal attach, send and folder edits, while one shared read runtime stays eager? This includes the three-line Rolldown $initial Effect group that keeps eager Effect code in one chunk so new lazy roots do not fragment it.
Risk
medium-low — Send and edit paths now depend on a lazy chunk. Failures are contained with Retry; a folder edit keeps its intent and resubmits exactly once. The chunking configuration affects every future lazy boundary.
Evidence
- web: load SDK terminal and mutation services on first use #5153
- web: load SDK terminal and mutation services on first use (hosted #5153) #5214
Completion rule
Compounding Manager records Nathan's answer or sign-off before this sub-issue closes. Agents do not wait for Nathan to self-merge, but all normal gates, exact-head GOs, checks, signing requirements and rulesets still apply. No --admin and no auto-merge. Merge alone does not close this sign-off request.
Posted on behalf of @schickling
| field | value |
|---|---|
agent_identity |
unknown |
session |
unknown |
agent_persona |
unknown |
agent_supervisor |
unavailable |
agent_tool |
unknown |
agent_tool_version |
unknown |
agent_runtime |
unknown |
agent_model |
unknown |
worktree |
unknown |
Activity