Skip to content

[02/06] feat(core): add functions exec sandbox runtime - #4

Draft
HeavenllyDemon wants to merge 1 commit into
feat/functions-exec-01-foundationsfrom
feat/functions-exec-02-runtime
Draft

[02/06] feat(core): add functions exec sandbox runtime#4
HeavenllyDemon wants to merge 1 commit into
feat/functions-exec-01-foundationsfrom
feat/functions-exec-02-runtime

Conversation

@HeavenllyDemon

Copy link
Copy Markdown
Member

Second PR in the ordered functions.exec stack; targets #3. Adds a private macOS Seatbelt worker runtime, exact dev/compiled CLI worker dispatch, and focused protocol/runtime tests. No model-visible tool registration, daemon wiring, nested dispatch, provider, or protocol/client surface is introduced.

Verification:

  • Core functions-exec tests (23 pass)
  • compiled CLI worker-route smoke test (1 pass)
  • CLI TypeScript check
  • compiled CLI build
  • git diff --check

Core TypeScript still reports only the six pre-existing approvals.test.ts diagnostics. A nested Seatbelt execution cannot run inside the enclosing host sandbox, so the generated profile is unit-tested and the worker route is tested separately.

@HeavenllyDemon
HeavenllyDemon force-pushed the feat/functions-exec-01-foundations branch from bf1b550 to 13c96f1 Compare August 18, 2026 13:15
@HeavenllyDemon
HeavenllyDemon force-pushed the feat/functions-exec-02-runtime branch from 1ddf672 to 24fa831 Compare August 18, 2026 13:15
@HeavenllyDemon HeavenllyDemon changed the title [02/05] feat(core): add functions exec sandbox runtime [02/06] feat(core): add functions exec sandbox runtime Aug 18, 2026
HeavenllyDemon added a commit that referenced this pull request Aug 20, 2026
USER LIVE-GATE FIX #4, research half: does LOK paint an infinite grid
past a spreadsheet's used range, the way Excel/Calc's own UI does?
Answered empirically against our real vendored LOK pin, not assumed —
OfficeHelperLiveTests.testGateXlsxTilesPastTheUsedRangeEmpiricalInfinite
GridProbe requests gate.xlsx tiles at the used-range edge and ~20 tiles
beyond it: both come back as a clean, gridded, non-blank canvas (PNG
dump), unchanged all the way out. paintPartTile genuinely renders empty
cells there; nothing needed faking client-side.

Implementation: OfficeTileCanvasView.effectiveExtentTwips extends the
scrollable bound by 2 extra screens per axis, for spreadsheets only
(isSpreadsheet, read once from the open document's type — presentations/
documents have real fixed page bounds and were never probed for this).
One computed property feeds BOTH the scroll clamp (clampedOriginX/Y) and
performSubscribe's churn-audit skip-check
(officeClampViewportToDocumentExtent's call site) so they cannot disagree
— the trap being guarded against: if scrolling reached further than the
skip-check's own clamp, the margin would be scrollable but its tiles
would never actually get requested (placeholders forever, just moved past
the new margin instead of past sizeTwips).

That widened skip-check interacts with fix #3's whole-document residency
sweep at a small, fully-resident spreadsheet's own edge: the fixed
subscribeMarginPoints overscan now genuinely touches real, never-
prefetched margin tiles, so a resident document's post-fill scroll near
its edge now costs exactly one further subscribe (a one-time margin
warm), not the prior zero. testResidentDocumentIsPrefetchedWholeIn...
NoFurtherRequests is amended (not weakened) into a two-phase pin proving
exactly that: one warm, then genuine silence once the touched slice is
also cached — the "no chatter for zero benefit" invariant's spirit holds,
only its letter moved.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant