Skip to content

A personal assistant that lives on your desktop, remembers what matters, and can use your Mac for you.

TypeScript

ci(macos): verify bundled engine and staged runtime

maicololiveras3c001afbbcf6
diff --git a/.github/workflows/macos.yml b/.github/workflows/macos.yml
new file mode 100644
index 0000000..03e619b
--- /dev/null
+++ b/.github/workflows/macos.yml
@@ -0,0 +1,61 @@
+# Native engine/runtime checks, not a signed desktop release or a model/GUI test.
+name: macOS
+
+on:
+ push:
+ pull_request:
+ workflow_dispatch:
+
+permissions:
+ contents: read
+
+concurrency:
+ group: macos-${{ github.workflow }}-${{ github.ref }}
+ cancel-in-progress: true
+
+jobs:
+ engine-runtime:
+ name: Engine and staged runtime
+ runs-on: macos-latest
+ timeout-minutes: 30
+ defaults:
+ run:
+ shell: bash
+ steps:
+ - uses: actions/checkout@v7
+ with:
+ persist-credentials: false
+ # Reads pnpm 11.5.0 from the repository's packageManager declaration.
+ - uses: pnpm/action-setup@v4
+ - uses: actions/setup-node@v6
+ with:
+ node-version: 24
+
+ # Keep lifecycle scripts enabled; pnpm-workspace.yaml allows esbuild and gentle-pi.
+ - name: Install dependencies
+ run: pnpm install --frozen-lockfile --ignore-scripts=false
+
+ - name: Typecheck
+ run: pnpm typecheck
+ - name: Full Vitest suite
+ run: pnpm test
+ - name: Build UI
+ run: pnpm build
+
+ - name: Stage native runtime
+ run: |
+ set -euo pipefail
+ test "$(node -p 'process.platform')" = darwin
+ case "$(node -p 'process.arch')" in
+ arm64) target=darwin-arm64 ;;
+ x64) target=darwin-x64 ;;
+ *) echo "Unsupported macOS Node architecture" >&2; exit 1 ;;
+ esac
+ # The stager validates host/target support before downloads. Currently arm64 only;
+ # an x64 runner must fail explicitly until the existing stager supports that target.
+ # It builds the daemon and UI, verifies downloads, and records runtime versions.
+ node scripts/package/stage-runtime.mjs --target "$target" --out "$RUNNER_TEMP/gentle-dot-runtime"
+
+ # Isolated HOME, engine idle, clean stop, and an unchanged read-only runtime copy.
+ - name: Smoke staged runtime
+ run: node scripts/package/smoke-runtime.mjs --runtime "$RUNNER_TEMP/gentle-dot-runtime" --read-only --timeout 240
diff --git a/odd/tasks/update-engine-stable.md b/odd/tasks/update-engine-stable.md
new file mode 100644
index 0000000..e029e2f
--- /dev/null
+++ b/odd/tasks/update-engine-stable.md
@@ -0,0 +1,40 @@
+# Update the bundled engine to stable releases
+Branch: `chore/update-engine-stable`, from `origin/main` at `3f0a25a`. Delivery: ask-on-risk; separate dependency and macOS CI work units (~150 authored lines, excluding generated lockfile).
+Checks: pnpm 11.5.0, Vitest, TypeScript, UI build, independent verification; Risk: item 5 (runtime dependencies).
+
+## Specs
+S1. "mira el proyecto a ver si es el mismo dionde estas y si no lo clonas"
+S2. "luego en mainm vas a mirar la ultima version estable de gentle-shell"
+S3. "y la propiia de gentle-dot la vas a actualizar para que use lo ultimo de gentle-shell y su gentle-pi y pi y demas"
+S4. "debes hacer ell ci para probarlo en mac"
+S5. "mira que podemos limpiar en M para poder hacer ese push"
+S6. "si dale" (authorization for the two named .next folders with their servers stopped).
+
+## Tasks
+T1 | S1-S3 | inline continuation after unavailable writer | pending | Pins, lockfile and packaging expectations aligned in d56ae1a; frozen install passed, compatibility unresolved.
+T2 | S3 | inline checks | pending | Local full suite failed (93 failed, 841 passed, 50 skipped; 3 errors). Native macOS CI will establish platform evidence; baseline causality remains unknown.
+T3 | S1-S3 | independent verify + native review | blocked | Independent verifier timed out at startup and returned no verdict; await human disposition of unavailable verification and failing checks. Native review not started, no commit.
+T4 | S4 | delegated (context backstop) | done (local preparation) | Added .github/workflows/macos.yml; YAML and structural checks pass; separate CI work-unit commit pending.
+T5 | S4 | remote execution | in_progress | GitHub authentication/push permission and commit identity confirmed; dependency candidate d56ae1a created, preparing CI candidate and authorized push.
+T6 | S5 | inline read-only audit | done | Audited M: without deletion: 449776 files, zero errors; identified two generated .next folders (424+385 MiB).
+T7 | S6 | inline scoped cleanup | done | Removed only inactive website .next, verified absent and 388 MiB free. WhatsApp .next preserved because a project process was active; no process stopped. Further cleanup unnecessary for current push.
+
+## Log
+L1. Original request: "sabes clona este repo https://github.com/Gentleman-Programming/gentle-dot.git en M_/Dev/personal y mira que version de gentle-shell tiene po detras y se deb hacer que use la ultima en main"
+L2. Correction: "no lo que quiero es mira el proyecto a ver si es el mismo dionde estas y si no lo clonas luego en mainm vas a mirar la ultima version estable de gentle-shell y la propiia de gentle-dot la vas a actualizar para que use lo ultimo de gentle-shell y su gentle-pi y pi y demas"
+L3. Existing clone is gentle-dot-local on feat/windows-native-independent, clean at 65bac17. Parent working directory belongs to an unrelated enclosing Git root; registering the nested clone as a same-clone worktree was rejected. Created a clean worktree inside the session project, gentle-dot-main, based on fetched origin/main (3f0a25a), without touching the Windows branch. Independent-repository subagent access was granted through the host prompt.
+L4. Primary sources: npm latest tags report gentle-pi 4.6.0 and Pi 1.5.0. https://github.com/Gentleman-Programming/gentle-shell/releases/tag/v4.6.0 identifies the stable bundled distribution as 4.6.0-1.5.0 and its Gentle AI runtime as 4.3.1. There is no separate gentle-shell npm package (registry returns E404); its launcher ships in gentle-pi. Main currently pins gentle-pi 4.3.0 and pi-ai/pi-coding-agent/pi-mcp/pi-tui 1.4.0.
+L5. This is a dependency metadata update, not a newly specified behavioral rule: no meaningful RED test. Existing engine integration tests, package/runtime tests, typecheck and UI build will check compatibility. No unrelated dependency refresh, installed-user environment upgrade, push, merge or release is authorized.
+L6. Installation attempt failed at gentle-pi postinstall: Windows cmd could not find node, although bash and where.exe resolve C:\Program Files\nodejs\node.exe. Inherited PATH contains repeated entries and is excessively long; next scoped attempt will use a minimal process-local tool PATH, not modify user/system settings. Failed add updated lockfile but left package.json at old pins. The runtime context backstop fired: delegate the remaining bounded dependency update and self-checks to one writer. Existing runtime-build tests hardcode old actual dependency versions; update only those expectations, not synthetic parser fixtures.
+L7. Writer mw2yau6d-2-kr81 timed out during startup after four minutes, delivered no findings and made no edits. User requested: "Review the delivered subagent output and continue." Writer is unavailable and was not retried. Parent reconciled the partial lockfile with daemon pins and updated only actual runtime manifest expectations, including the new pi-schema 1.5.0 transitive sibling. Process-local PATH attempts exposed npm's configured PowerShell launch; a direct Node spawn using uppercase PATH and native forward-slash paths successfully executed powershell.exe. The corrected installation attempt is running; no user/system environment changed. Native assessment requires explicit untracked selection before native risk is available; item 5 escalation independently requires verification.
+L8. User added: "debes hacer ell ci para probarlo en mac". Repository main has only .github/workflows/windows.yml; native macOS CI is a new in-scope delivery. Reuse stage-runtime.mjs and smoke-runtime.mjs rather than inventing a probe; tests on Windows cannot prove a macOS runtime. Preparing CI is authorized; publishing a branch and remote execution still require explicit publication authorization. The existing Windows-only branch remains untouched.
+L9. User selected "Publicar la rama y ejecutar CI" in response to "¿Autorizás publicar chore/update-engine-stable en Gentleman-Programming/gentle-dot y ejecutar su CI de macOS, sin merge ni release?" Publication and CI are now authorized. gh api repos/Gentleman-Programming/gentle-dot returned 401 Bad credentials. Authentication must be restored before remote execution can be proven; no token was requested or exposed.
+L10. Frozen pnpm 11.5.0 install succeeded with normal lifecycle scripts, installing Gentle AI 4.3.1. Local TypeScript build (tsc -b) and UI production build passed. Focused Vitest: 76 passed, 6 failed, 9 skipped (91); failures are three Windows chmod assertions, one slash-path assertion, one auth timeout and one isolation teardown timeout. Baseline causality not established; no tests weakened. Runtime manifest expectations remain skipped without the native Windows addon. Direct public helper probe passed: all eight direct/transitive Pi packages at 1.5.0, gentle-pi 4.6.0, jiti/ws unchanged; pi-schema is included in runtime overrides. Full local suite is running.
+L11. CI writer completed T4/S4: native macos-latest, read-only permissions, 30-minute timeout, Node24/repo pnpm, frozen lifecycle-enabled install, typecheck/full tests/UI build, native staging and isolated read-only runtime smoke. Writer YAML/structural checks and diff checks passed; parent independently parsed YAML and asserted triggers, runner, permissions and smoke step. GitHub's current public runner docs explicitly list macos-latest and macos-15 as ARM64, compatible with existing darwin-arm64 stager. No macOS run has occurred. Independent verifier was launched once for dependency and CI risk (item5).
+L12. Final local full Vitest result: exit1, 35 failed files /47 passed /9 skipped (91); 93 failed tests /841 passed /50 skipped (984); 3 errors; 299.76 seconds. This does not establish macOS compatibility or regression causality. No tests were weakened and no unrelated fixes were attempted. Independent verifier mw2zyk15-4-zvcp timed out during startup after four minutes, produced no verdict and was not retried. Work remains uncommitted/unpublished; native review was not started on this incomplete candidate. Needs human intervention: restore GitHub authentication to obtain the requested actual macOS evidence; independent verification remains unavailable. No merge/release authorized.
+L13. User removed Env:GITHUB_TOKEN and Env:GH_TOKEN in PowerShell and reported gh auth status authenticated via keyring as Maicololiveras with repo/workflow scopes, then requested "sigue". Resume preserves the already-authorized branch publication and macOS CI. Parent is checking access with token overrides removed only for the child process; no credentials are displayed or changed. Candidate commits/push are for obtaining CI evidence, not a claim of passing checks or approval. The previous verifier remains unavailable, not retried.
+L14. Repaired child-scoped GitHub authentication confirmed repo maintain/push permissions. Git could not create index.lock because M: had only272KiB free. Attempted cleanup only session-generated root node_modules in this worktree; rm failed ENOTEMPTY and left dependencies partially removed, then another Git attempt still failed disk-full. No source was removed, no commit created. Durable task file could not be updated safely then; memory observations3653/3654 recorded the incident.
+L15. User asked "mira que podemos limpiar en M para poder hacer ese push". Read-only full drive audit:138s,449776 files,zero errors,5406 links skipped, system/recycle directories excluded. Migrado_C dominates82.5GiB including VMs and downloads; those and personal data were not changed. Two verified Next.js generated folders offered: M:/Dev/Personal/praxisgenai-agentes/apps/praxisgenai-agente-whatsapp/.next424MiB and M:/Dev/Personal/pagina-web-ingenierias-aliadas/apps/web/.next385MiB. User replied "si dale" to deleting only those with servers stopped and resuming push.
+L16. Process safety check preserved WhatsApp .next due to an active project Node process. No process was stopped. Deleted only the authorized inactive website .next; verified it absent, WhatsApp build still present, and free space increased from1MiB to388MiB. This suffices for current Git work; no broader cleanup attempted.
+L17. Git add now succeeded and dependency changes are staged. Commit failed with "Author identity unknown" and "unable to auto-detect email address". No global/repository Git author configuration was invented or modified. Await user choice of commit identity; branch still has no new commit/push.
+L18. User selected "Usar mi cuenta GitHub y correo privado noreply" for these commit commands only. GitHub user API confirmed public identity; used command-scoped user.name/user.email with its standard GitHub noreply address, not persistent Git configuration. Dependency candidate commit d56ae1a00592f4e20a8653e05ead70dfa66b524e created (27 authored lines excluding lockfile). Initial native committed-only assessment still refused ambient untracked files; normalize intended workflow/task tracking in index before assessment. No review approval or functional pass claimed.