A personal assistant that lives on your desktop, remembers what matters, and can use your Mac for you.
TypeScript
docs(odd): record T28e and the memory recall fix (L85)
Alan Buscagliac3e451255aec
diff --git a/odd/tasks/gentle-dot.md b/odd/tasks/gentle-dot.mdindex 6fd2f1e..a87f33a 100644--- a/odd/tasks/gentle-dot.md+++ b/odd/tasks/gentle-dot.md@@ -72,7 +72,7 @@ Branch: `feat/gentle-dot` · Delivery strategy: `single-pr` (user choice, L7; fo- Acceptance: the UI hides "New conversation" and the conversations list (the code and protocol stay, behind a flag, so they can return), and the header shows the assistant instead of a conversation title. The chat feels endless: the daemon rotates the underlying session transparently when it grows past a threshold (default 20 MB or 10 compactions), starting a fresh session seeded with a handoff summary, and the UI shows the previous session's recent messages above a subtle "Earlier messages" divider. The UI loads only recent messages, with "Show earlier" for more. Engram stays the durable memory, so compaction detail loss does not lose decisions.- **S23 — Use the user's global Engram, always in project `gentle-dot`.** User (L39): "y que pasa con engram? veo que no usa el engram total puede ser ? el global qiuero decir, estaria bueno que use el global y que siempre escriba en un proyecto llamado gentle-dots", then "gentle-dot perdon".- - Acceptance: the engine's memory talks to the user's global Engram (the default server, port 7437, data dir `~/.engram`) instead of a private one, and every memory the assistant saves or searches is scoped to the project `gentle-dot`, whatever the workspace. The rest of the engine's HOME stays isolated (S12). The assistant no longer starts its own Engram server (which also removes the orphaned-server advisory from L31). If the global Engram is not running, the engine's memory plugin may start it as it does for Gentle Shell, with the user's data dir.+ - Acceptance: the engine's memory talks to the user's global Engram (the default server, port 7437, data dir `~/.engram`) instead of a private one, and every memory the assistant saves goes to the project `gentle-dot`, whatever the workspace; searches and recall cover the user's whole memory (all projects) (corrected in L85: the user asked that it always *writes* to gentle-dot). The rest of the engine's HOME stays isolated (S12). The assistant no longer starts its own Engram server (which also removes the orphaned-server advisory from L31). If the global Engram is not running, the engine's memory plugin may start it as it does for Gentle Shell, with the user's data dir.- Mechanism (to verify in the implementation): `ENGRAM_DATA_DIR=<real ~/.engram>` in the child env so the plugin's instance-id check matches the global server; the project forced through the plugin's supported override (Engram has `ENGRAM_PROJECT` / `process_override`; check that gentle-engram honors it), or a workspace whose detected project is `gentle-dot` as the fallback.- **S24 — Computer control (last item).** User (L43): "un item mas al final de todo, que haga como codex y que permitas controlar tu computadora, que pueda manejar tus aplicaciones y tal".@@ -146,7 +146,7 @@ Branch: `feat/gentle-dot` · Delivery strategy: `single-pr` (user choice, L7; fo| T28b | S29.1, S29.5 (daemon) | delegated writer, parallel with T28a (surface `packages/daemon/**`) | done | `ea52273`; RED 7 failing → GREEN; parent re-ran pnpm test 440 | Bundled daemon build, runtime-aware paths, Engram resolution, relocatable pi wrapper || T28c | S29.1, S29.4 | delegated writer (context backstop) | done | see L83; parent re-ran pnpm test 454 | `scripts/package/stage-runtime.mjs` per target; clean-HOME smoke, read-only tree smoke, size || T28d | S29.1, S29.2, S29.4 | delegated writer, parallel with T28f | done | `546aa92` | Tauri macOS resources + DMG + `pnpm package:mac`; launch from /Applications copy |-| T28e | S29.2 | inline; user consented (L84) | in progress | `5ec1d25` script; DR comparison running | Self-signed identity; compare the designated requirement across two builds |+| T28e | S29.2 | inline; user consented (L84) | done | `5ec1d25`; two signed builds both `certificate leaf = H"4611e0a8…"`, verify ok | Self-signed identity; compare the designated requirement across two builds || T28f | S29.3 | delegated writer, parallel with T28d | in progress | — | Linux .deb (arm64, amd64) and Arch PKGBUILD in containers; clean install smoke || T28g | S29.4 | last | pending | — | docs/install.md; Hyprland snippets point at /usr/bin/gentle-dot || T22 | S18 (hardening, L47 B1/B2) | delegated writer | done (accepted with documented gaps, L52) | `8651bba`; parent re-ran 328 tests + typecheck | Option A: authoritative in-memory connector state with revert, credential reads blocked, path-independent bash checks, full approval preview, redirect manual, private Engram stop, onboarding overlap fix |@@ -241,4 +241,5 @@ Environment notes: Node v24.14.1 and pnpm are present. `cargo` is on PATH but `r- **L82 (2026-10-09):** T28a done (`84a38a4`). T28b done: `build:runtime` (esbuild ESM bundle of daemon + protocol, engine external, lockfile-exact `package.json`, relocatable `bin/pi`), runtime-mode UI/engine/pi paths, Engram resolution passed as `ENGRAM_BIN`, `--self-check`; smoke: `bin/pi --version` → 1.0.4 from a hand-built runtime. Advisory: the login-shell lookup for Engram runs synchronously with a 5 s timeout at daemon start. T28c launched; its smoke must use a private Engram on a temp port so it never touches the user's 7437 server or ~/.engram.- **L83 (2026-10-09):** T28c done: `pnpm package:runtime --target darwin-arm64` stages 346.4 MB (408 MB on disk: daemon/node_modules ~267 MB, Node ~128 MB, Engram 20 MB) in 11 s with cache; Node 24.14.1 and Engram 3.2.1 (latest release; the user's is a dev pseudo-version) checksum-verified; refuses non-host targets. Clean-HOME smoke (`scripts/package/smoke-runtime.mjs`): idle in 23.1 s, private Engram on a temp port from `<rt>/bin/engram`, first-run npm install of the companions, 0 runtime files changed. Read-only smoke: idle, 0 changes, no EACCES/EPERM (risk R1 cleared). Fix: the engine gets a private TMPDIR when none is set (jiti cached in shared /tmp/jiti). Notes for later: transitive deps resolved by npm at staging; `.nvmrc` says only "24"; the engine log says "Gentle AI sends anonymous usage metrics" (privacy/white-label to review); size trims possible (esbuild ~21 MB, @shikijs/cli 17.6 MB). Scratch removed.- **L84 (2026-10-09):** T28d done (`546aa92`): `pnpm package:mac` → `Gentle Dot_0.1.0_aarch64.dmg` 111.2 MB (app 368 MiB); runtime injected with `tauri build --config` (a resource in tauri.macos.conf.json would be copied on every cargo build and fail without a staged runtime); nested Mach-O signed inside-out except `gentle-ai`, whose sha256 gentle-pi checks; codesign --verify --deep --strict valid; mounted-DMG copy smoke idle in 23.1 s and read-only smoke ok, 0 runtime changes; ad-hoc DR changed between builds (57c5… → 43e0…). Biome now ignores `build/` and `.cache/`. Quarantine/Gatekeeper on a downloaded DMG still needs a real second Mac. User consented to T28e ("Sí, crealo"): identity "Gentle Dot Local Signing" created in the login keychain; the trust step was not needed (codesign signs with the untrusted identity and the DR reads `certificate leaf = H"4611e0a8…"`), so the script skips it. Two signed builds running to compare the DR.-- **Next step:** T28e DR comparison, T28f, then T28g docs; grant both permissions, take a screenshot (the Dot must be absent), click and type in a harmless app, a risky "Send" confirmation, ⌥⇧Esc panic, a blocked app (System Settings), and `screencapture -x /tmp/t.png` from the agent's bash must fail (R1); the community tester runs docs/linux-testing.md when the user shares it; T23/S25 before any public release.+- **L85 (2026-10-09):** T28e proven: two release builds signed with "Gentle Dot Local Signing" both have `designated => identifier "dev.gentleman.gentle-dot" and certificate leaf = H"4611e0a8b9c71afb97cafdbf79dccf4816d80e6b"`, codesign verify ok, DMG 116,354,516 bytes. The user saw many keychain prompts on the first signed run (each of 8 nested signatures asks); fixed by "Permitir siempre" once. User (screenshot, the assistant saying its memory search is limited to Gentle Dot): "porque esto? si tiene access a la memoria global?". Cause: `identity.md` also scoped searches to `gentle-dot`, beyond S23's "siempre escriba". Fixed: save to gentle-dot, search with `all_projects: true` (RED 2 failing → GREEN, pnpm test 478).+- **Next step:** T28f, then T28g docs; grant both permissions, take a screenshot (the Dot must be absent), click and type in a harmless app, a risky "Send" confirmation, ⌥⇧Esc panic, a blocked app (System Settings), and `screencapture -x /tmp/t.png` from the agent's bash must fail (R1); the community tester runs docs/linux-testing.md when the user shares it; T23/S25 before any public release.