@moxuli/moremote 0.1.5 → 0.1.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (38) hide show
  1. package/README.md +40 -15
  2. package/dist/cli.js +2 -1
  3. package/dist/cloud-client.d.ts +10 -1
  4. package/dist/cloud-client.js +43 -3
  5. package/dist/event-publication.d.ts +6 -0
  6. package/dist/event-publication.js +48 -0
  7. package/dist/journal.d.ts +3 -0
  8. package/dist/journal.js +7 -1
  9. package/dist/limits.d.ts +1 -0
  10. package/dist/limits.js +1 -1
  11. package/dist/live-activity.d.ts +60 -0
  12. package/dist/live-activity.js +131 -0
  13. package/dist/live-directory.d.ts +16 -0
  14. package/dist/live-directory.js +78 -0
  15. package/dist/local-enrollment.d.ts +1 -1
  16. package/dist/local-enrollment.js +1 -1
  17. package/dist/notification-preview.d.ts +29 -0
  18. package/dist/notification-preview.js +75 -0
  19. package/dist/official-client.d.ts +71 -0
  20. package/dist/official-client.js +63 -12
  21. package/dist/runtime.d.ts +2 -1
  22. package/dist/runtime.js +14 -13
  23. package/docs/STATE.md +70 -503
  24. package/docs/configuration.md +21 -1
  25. package/docs/journal/2026-11-14-state-before-0.1.6-part-1.md +400 -0
  26. package/docs/journal/2026-11-14-state-before-0.1.6-part-2.md +115 -0
  27. package/docs/journal/2026-11-15-custom-origin-release.md +35 -0
  28. package/docs/journal/2026-11-15-informative-notifications-and-settings.md +41 -0
  29. package/docs/journal/2026-11-15-remote-activity-local-acceptance.md +85 -0
  30. package/docs/plans/2026-11-10-notification-delivery.md +8 -0
  31. package/docs/plans/2026-11-14-custom-api-origin.md +69 -0
  32. package/docs/plans/2026-11-15-remote-activity-and-shared-events.md +99 -0
  33. package/docs/specs/01-architecture.md +3 -2
  34. package/docs/specs/02-encrypted-delivery.md +25 -0
  35. package/docs/specs/03-api-contract.md +47 -6
  36. package/docs/specs/05-endpoint-and-lifecycle.md +9 -1
  37. package/package.json +2 -2
  38. package/vectors/remote-activity-v2.json +30 -0
@@ -0,0 +1,400 @@
1
+ # Current state — 2026-11-14
2
+
3
+ ## Released0.1.5 — 2026-11-14
4
+
5
+ Owner-authorized tagv0.1.5 targets `ba8a428b63562cdd4b258cd79f7a8251af067dbd`.
6
+ GitHub CI43567209765 passes complete checks and real packaged upgrade/rollback
7
+ on Windows, Linux and macOS. Release43567215583 succeeds through the existing
8
+ scoped-secret npm/provenance and GitHub publication workflow. Anonymous registry
9
+ readback confirms version/latest0.1.5. The public npm and GitHub tarballs are
10
+ byte-identical, match registry SHA512 and GitHub SHA256SUMS, and the isolated
11
+ public installation reports0.1.5. Tarball:137104bytes, SHA256
12
+ `8ad64844cab23dea5c0295e6e9b7ef3d4f0e88785c517ec182c783bdd23147dd`.
13
+
14
+ Cloudflare retains only notifications and explicit notification replies/approvals.
15
+ Deleted activity interests, optional surface lane, widget fingerprints and quota
16
+ reads. `/state` contains verified daemon identity and exact current bound requests
17
+ only. Accepted source reads retain pending requests outside bounded discovery;
18
+ resolution/replacement/reconnect fences prevent stale resurrection. Publish only
19
+ semantic changes, one final clear, and near-expiry pending hydration. Unknown
20
+ ACK retries keep original bytes and cannot replay user actions.
21
+
22
+ Fresh full `npm run check` passes237 behavioral tests, types and compilation.
23
+ Real SDK and real runtime subprocess consumers verify preserved notification
24
+ question/approval encoding,3s control cadence, normal/outage pause fences,
25
+ immutable lost acknowledgements, drain/receipt ownership and zero idle surface or
26
+ directory calls. Projection tests first exposed leaked title/host/usage fields
27
+ and silently dropped oversized requests; all now pass. Read-only independent
28
+ review found no remaining authority/replay blocker. The initial local aliased
29
+ frontend smoke exceeded its10second budget during concurrent builds; the exact
30
+ preserved frontend subsequently ran in0.58seconds, and the complete unchanged
31
+ upgrade/rollback smoke passed. No timeout or production behavior was relaxed.
32
+ No everyday service, installed runtime or production host session was changed.
33
+ The previous0.1.4 publication below remains historical.
34
+
35
+ ## Released0.1.4 — 2026-11-13
36
+
37
+ - Owner-authorizedv0.1.4 targets tested sourcea5615b6. Final local251/251,
38
+ typecheck/build and independent source reviews pass. HostedCI43389151913 passes
39
+ complete checks/identity/real upgrade and rollback on Linux, macOS and Windows.
40
+ - Release43390548675 succeeds through existing-secret npm/provenance and GitHub
41
+ publication. Independent public reads confirm version/latest0.1.4; downloaded
42
+ npm/GitHub bytes match SHA1/SHA512, GitHubSHA256SUMS and the exact local artifact.
43
+ SHA256: `c0e56b6ce596216fea6b2e546fc153c3833bafebc4c5ecf271d18b6a2d4e5151`.
44
+ - No everyday service, ordinary official conversation or production cloud change.
45
+ Earlier unreleased/acceptance entries below are historical checkpoints; these
46
+ verified publication facts supersede their former release status.
47
+
48
+ - Pending questions/approvals now use a stable current-occurrence clock, not an
49
+ older task-completion clock. Actual SDK delayed-current/snapshot regressions
50
+ first reproduce resolution/replacement resurrection, then the observation fence
51
+ prevents journal, binding and notification renewal. Actual same-batch SDK reply
52
+ consumers also reproduce caller-continuation resurrection before repair: adapter
53
+ journal ownership removes duplicate synchronization, source fingerprints prevent
54
+ old request text acquiring a replacement binding, and crypto rechecks currentness.
55
+ Cached question/approval consumers fail before exact occurrence capture/drain
56
+ binding, then notifications10/10 pass without old clocks consuming new IDs.
57
+ Final unchanged-input full check passes251/251,typecheck and build. Independent
58
+ Stage A closes both lifecycle blockers; final quality re-review and hosted
59
+ three-platform verification remain pending before immutable publication.
60
+ - Quality review catches observed in-place mutation followed by valid rename;
61
+ both real regressions fail before the pre-retry guard, then resource24/24 pass.
62
+ Hosted40e1b73 passes Linux/macOS but Windows rejects test-injected replacement
63
+ with a live handle. Tests now verify real refusal, complete original contents
64
+ and identity, then actual post-close replacement and strict unsafe-file refusal;
65
+ no production error guard or platform coverage is removed. Narrow review passes.
66
+
67
+ - Ordinary config rename is now distinguished from an unsafe resource: at most
68
+ three reopen attempts, independent descriptor/path validation, retired handles
69
+ discarded, strict no-follow/user/private-mode/link/byte/encoding checks retained.
70
+ Same-inode content changes remain rejected. Real rename regressions reproduce
71
+ the failure before repair, then22resource consumers and the original2runtime
72
+ cases pass. Final unchanged-input full check passes235/235,typecheck and build.
73
+ Stage A narrow review passes; independent quality/security review and fresh
74
+ hosted three-platform verification remain in progress before publication.
75
+
76
+ - Hosted1df64e0 exercises all new behaviors successfully on Windows, but its
77
+ new cache fixture removes the directory before closing SQLite. Combine cleanup
78
+ into one ordered close-then-remove hook; preserve all behavior assertions and
79
+ rerun the full matrix on the corrected test source. Production code is unchanged.
80
+
81
+ - Corrected8e4e065 Windows cleanup passes; macOS then rejects signaling an
82
+ already stopped wrapper's old process group. Preserve independent lock/control/
83
+ supervisor/exit assertions and skip redundant group signaling only after those
84
+ shutdown proofs. All4actual local lifecycle consumers pass; narrow review agrees.
85
+
86
+ - Exact tagv0.1.3 and its successful three-platform CI43380589650 are retained.
87
+ Release43381419784 fails its full check before packaging/publication: concurrent
88
+ normal runtime config replacement triggers FOREIGN_RESOURCE_LIMIT in a read.
89
+ Publish and GitHub Release steps are skipped; no0.1.3 package is submitted.
90
+ Preserve that immutable failed tag and prepare0.1.4 after a deterministic repair.
91
+
92
+ - First hosted run43378427840 correctly rejects three cross-environment fixture
93
+ defects: inherited config/service paths, unsupported Windows POSIX-mode equality,
94
+ and an unbound synthetic Paseo home whose local mismatch check had accidentally
95
+ contacted the ordinary daemon read-only. Bind the exact fixture home and require
96
+ its real handshake, no cloud calls, unchanged config and private-output absence.
97
+ - Stricter pending-endpoint controls return409 before activation. Runtime now
98
+ activates only after official identity and original expiry/revocation checks;
99
+ no command/state lane exists in that cycle, and the next cycle validates controls.
100
+ Shared origin quota fences and fixed activation proof remain intact. Independent
101
+ narrow review finds no blocker. Final unchanged-input full check passes221/221
102
+ and build; hosted portability/packaged smoke are being rerun on this exact delta.
103
+
104
+ - Integrated51942a0 and reviewed the final enrollment/setup and packaging delta.
105
+ Exact public0.1.2 archive bytes now live in the test fixtures with verified npm
106
+ SHA1/SHA512 and matching recorded GitHub SHA256, independent of workstation caches.
107
+ - Final full check passes typecheck,221/221 tests and build. Three actual retained
108
+ public0.1.2 migration consumers pass. Real packaged activation/failed-start
109
+ rollback/retained frontend and clean shutdown pass; no everyday service is installed.
110
+ - Release validation accepts additive capability metadata while retaining the
111
+ strict1/1/1 protocol tuple and exact source/package capability equality.
112
+ Constructor-scoped fixture isolation removes inherited operator credentials;
113
+ the smoke retries only read-only unproven-stage probes under its live owned supervisor.
114
+ - Independent Stage A and Stage B reviews find no remaining scoped blocker.
115
+ Main integration, hosted checks, immutable npm/GitHub publication and independent
116
+ registry receipt remain pending. The production cloud remains unchanged.
117
+
118
+ ## Scope
119
+
120
+ Owner-approved notification/scoped delivery; local native surfaces are app-owned; Apache-2.0. Standalone Node24 companion targeting inspected official SDK/protocol0.15.3. Existing iOS protocol-vector floor is independent and unchanged. OpenUI and broader system extensions remain outside this scope.
121
+
122
+ ## Unreleased single-pairing enrollment — source0.1.3, locally accepted
123
+
124
+ - Official Paseo pairing is the only normal user pairing. Explicit
125
+ `setup --yes` prepares the optional owned CLI service; a connected native
126
+ client exchanges the existing per-phone offer through official authenticated
127
+ file APIs. No second QR, pasted invitation, terminal command or new relay
128
+ configuration is required in the app.
129
+ - Discovery is private and bounded; original request identity/expiry, canonical
130
+ offer and cloud-create bytes are durable before network I/O. Activation and
131
+ expiry remove the private handoff. Revocation, retained active phones, custom
132
+ origin, daemon pinning and managed-update opt-out remain authoritative.
133
+ - Confirmed review findings are fixed: duplicate runtime startup never rewrites
134
+ configuration; setup prepares packages before acquiring shared runtime
135
+ ownership, then holds it across load/authenticate/save. A concurrent runtime
136
+ either wins before config loading or is refused. Config readers/writers share
137
+ the524288-byte encoded bound; old managed0.1.2 setup selects a verified
138
+ enrollment-capable current package instead of silently enabling old code.
139
+ - Optional admission performs at most one cloud-create attempt per cycle with
140
+ its own3-second deadline. Unknown results retain exact retry bytes. No cloud
141
+ endpoint, recursive dispatch, polling budget or production deployment changes.
142
+ - Node24.13.0 typecheck passes. The final six-file selection passes37/38;
143
+ its remaining source-setup assertion incorrectly demanded absence of an
144
+ internal managed directory. That implementation-detail assertion is removed,
145
+ while actual package-manager refusal and service-entry checks remain. The
146
+ corrected consumer passes independently and the compiled build passes.
147
+ Both new setup/runtime interleavings failed before the ownership correction.
148
+ - Actual unmodified official Paseo0.15.4 and the native transport exchange the
149
+ canonical offer, verify the real native claim and unchanged activation proof,
150
+ and remove exact private request/response files. One cloud-create body and
151
+ zero official agents are observed. The cloud is a local in-process test
152
+ double; this is not production, physical-device or APNs acceptance.
153
+ - Independent-context source re-review closes the scoped native/CLI findings.
154
+ The weaker same-provider route is explicit; unavailable external native
155
+ reviews are not approvals. Temporary probe code/state are removed, with
156
+ redacted receipts retained outside the repository.
157
+ - Source0.1.3 remains unpublished. Public0.1.2, shared production and existing
158
+ official data are unchanged. No npm tag, TestFlight upload or phone install
159
+ is implied.
160
+
161
+ ## Unreleased Share-first onboarding delta — locally verified
162
+
163
+ - Approved cross-repository plan: MoRemote
164
+ `docs/plans/2026-11-13-share-first-onboarding.md`; CLI ownership is source,
165
+ focused consumers and public docs only. No publication or deployment.
166
+ - Explicit `pair` opts in to cloud, uses the production endpoint only when no
167
+ origin exists, and reuses existing official listen/credential discovery.
168
+ Origin validation, daemon pinning, custom targets/origins and retained
169
+ pair authority remain intact. Plain load/check/status remain passive.
170
+ - Task snapshots carry genuine provider and ISO-8601 creation time alongside
171
+ last-user time, through existing bounded projection and authenticated state.
172
+ Widget equality includes the new meaningful metadata. No assistant-update
173
+ substitution for user recency.
174
+ - Added actual CLI enrollment consumers with a synthetic official WebSocket
175
+ and isolated relay, passive diagnostics/custom authority/invalid-origin and
176
+ daemon-pin cases; added real-SDK encrypted task metadata consumers.
177
+ - Node24.13.0 typecheck, 22 focused pair-onboarding/task-projection/activity/CLI
178
+ consumers, and compiled build pass. The actual SDK/HTTP boundary exercises
179
+ passive diagnostics, authenticated enrollment, custom authority and encrypted
180
+ metadata without production enrollment or official-file changes.
181
+ - Independent read-only review `run-20261113030053-9f69faa3` approves the scoped
182
+ implementation. The same-provider fallback is explicit; this is not physical
183
+ acceptance or a new package release. Public0.1.2 and its cached receiver remain
184
+ unchanged.
185
+
186
+ ## Native service acceptance — 2026-11-12
187
+
188
+ - Actual Ubuntu26.04/Node24.13.0/systemd259 user-service acceptance passes:
189
+ install/start, authenticated status, QA0.1.1 → synthetic9000.0.2 activation,
190
+ failed9000.0.3 startup rollback, normal stop/uninstall and independent absence
191
+ of the unit, definition and live runtime. No cloud or real official daemon I/O.
192
+ - Initial Windows QA exposed missing native-import BOM and current-reader BOM
193
+ handling. Fresh-context specification review then found that persisting a BOM
194
+ breaks unchanged public0.1.1 runtimes, despite the current/current QA success.
195
+ - The current installer keeps persistent ownership XML BOM-free. Only a private
196
+ transient import outside shared state has a BOM; it is removed before `/Run`
197
+ and on `/Create` failure. Retained0.1.1 consumers remain usable for bootstrap
198
+ and rollback without a storage migration.
199
+ - Both new consumer regressions first failed. All20focused lifecycle/resource
200
+ consumers, typecheck and build then pass. The frozen reader matches the
201
+ independently downloaded public0.1.1 module bytes.
202
+ - The new actual Windows Task Scheduler journey passes in183.86seconds:
203
+ unchanged registry0.1.1 bootstrap → current synthetic9000.0.2 → deliberately
204
+ failed9000.0.3 → recovered9000.0.2, then normal stop/uninstall. Task,
205
+ definition, control endpoint and live supervisor/runtime are independently absent.
206
+ - Fresh-context specification and quality re-review close the scoped blocker.
207
+ This is the explicitly weaker same-provider fallback, not cross-vendor approval.
208
+ Earlier168.23second QA acceptance and unavailable provider reviews remain
209
+ historical evidence in [[2026-11-11-native-service-acceptance]].
210
+ - The candidate is unpublished QA bytes, not a public-to-public release. No real
211
+ official host, paid provider, cloud operation or everyday login service is used.
212
+ - The shared production cloud remains persistently enabled under the owner's
213
+ later decision; these isolated native tests neither use nor disable it. Older
214
+ temporary-window shutdown receipts below are historical, not current policy.
215
+
216
+ ## Released0.1.2 — 2026-11-12
217
+
218
+ - Package and lock root identities select0.1.2; no dependency or compatibility
219
+ tuple changes. Owner-approved tagv0.1.2 targets739c76008ea583fa86bfb023dafaa17a3ea9adf4.
220
+ - The combined check passes typecheck and180/181 tests. Its remaining legacy-wire
221
+ case incorrectly requires an extra read for an old event that may be coalesced.
222
+ The test now drains the actual wire and retains the phone-visible no-new-notice
223
+ and unchanged-ciphertext assertions without demanding that incidental RPC.
224
+ - Both actual SDK wire variants then pass2/2. Build, real packaged activation/
225
+ failed-start rollback/aliased frontend/clean stop, release identity validation
226
+ and deterministic0.1.2 packaging pass. These overlapping runs are not a new
227
+ single green full-suite result.
228
+ - Hosted CI43227228037 passes full check/build, release validation and real
229
+ packaged upgrade on Ubuntu24.04, macOS15 and Windows2025.
230
+ Automatic Release43232455123 passes check/build, upgrade smoke, deterministic
231
+ packaging, existing-secret npm publication/provenance and GitHub Release.
232
+ - Anonymous registry reads independently confirm version/latest0.1.2 after
233
+ asynchronous processing; publication is never repeated. Downloaded GitHub
234
+ bytes match SHA256SUMS and npm SHA1/SHA512 integrity. Archive SHA256:
235
+ `845fd98470964303a6a86dc696e64c47ac1e7b1ce90b59cd730cdec56d64f9bb`.
236
+ - Actual public0.1.1 installation/retained supervisor discovers and downloads
237
+ public0.1.2 through its unchanged normal background scheduler, not a custom
238
+ fetcher, direct queue, altered package or fake clock. Exact authenticated
239
+ status becomes0.1.2; bootstrap/previous remain0.1.1; retained frontend returns
240
+ 0.1.2; normal stop exits0 and all owned processes/files are removed, in80.12s.
241
+ No login service, real official connection or cloud operation occurs.
242
+ An initial fixture prepopulates an unowned state directory and is correctly
243
+ rejected before any process starts; initialization is corrected outside the
244
+ managed state, preserving strict ownership. Its exact failed fixture is removed.
245
+ - Production device reply/approval and remote activity/widget delivery still
246
+ require their separate acceptance; the release does not claim those gates.
247
+ - Release: https://github.com/moxuli/moremote-cli/releases/tag/v0.1.2
248
+
249
+ ## Released activity/widget integration — production acceptance open
250
+
251
+ - Published install identity is **`@moxuli/moremote`0.1.2**; command/runtime
252
+ remains `moremote-cli`, with existing per-platform service identities.
253
+ Activity/widget changes are included; physical production acceptance remains open.
254
+ - Implemented locally: authenticated encrypted per-task interests and activity
255
+ state, an owned optional2s host lane with250ms exact fallback reads, meaningful
256
+ keyed widget fingerprints on existing snapshot publication, and normal-only
257
+ quota pauses that preserve eligible terminal recovery. Commands/controls do
258
+ not await activity work; shutdown/drain joins it before SDK/journal close.
259
+ - Limits/expiry/error/dataflow truth lives in [[configuration]] and
260
+ [[specs/03-api-contract#Opt-in task activities and widget reloads]].
261
+ Interest expiry is at most8h (8 per pair); state at most600s, fresh acknowledged
262
+ renewal around8min. Unknown admissions retain exact bytes. Widget registration
263
+ expires24h with native renewal around12h. Missing tasks never imply finish.
264
+ - Integration-owner-reported evidence: CLI typecheck and57 tests across
265
+ `tests/activity.test.ts`, `tests/cloud-retry.test.ts` and
266
+ `tests/runtime-receipt.test.ts` passed. This is targeted local evidence, not
267
+ a newly green full suite, released artifact, or physical/device acceptance.
268
+ - Next gates: independent integration review and owner verification of the final
269
+ delta; authorized native Live Activity/widget rendering, stale/offline and
270
+ token replacement/expiry acceptance; separately authorized live cloud/APNs
271
+ delivery. APNs200 is provider admission, not delivery. Historical alert proof
272
+ below does not cover either new surface.
273
+ - A later owner-approved bounded physical acceptance observed all four attention
274
+ kinds through the actual official mock → companion → cloud → sandbox APNs path.
275
+ Duplicate completion and premature request-resolution bugs were exposed and
276
+ corrected locally; this is not real paid-model or production-service evidence.
277
+ - The request lifecycle and canonical terminal-identity corrections pass13focused
278
+ consumers plus typecheck. A later reverse-order wire regression first failed
279
+ both SDK variants, then both passed with typecheck after observation-order
280
+ fencing. Independent same-provider review reports no blocker; the preferred
281
+ cross-vendor provider was unavailable.
282
+ - Earlier bounded sandbox windows restored disabled service and production
283
+ provider secrets. The later November12 owner decision now keeps the existing
284
+ production service enabled; no temporary watchdog or sandbox swap is allowed.
285
+ Genuine device reply/approval receipts and remote ActivityKit/WidgetKit
286
+ acceptance remain open. No real-work session or new release is implied.
287
+ - Fresh local end-to-end action acceptance passes against the unchanged official
288
+ development mock, production runtime, real Pages/Worker/SQLite and a compiled
289
+ unchanged native Kit/CryptoKit slice. Exact send and bound plan denial each
290
+ execute once and produce authenticated accepted/resolved receipts; initial and
291
+ post-settlement identical retries cannot redispatch or change receipts. Both
292
+ SQLite journals retain exactly two settled operations. This is not physical
293
+ locked-notification UI or whole native-package acceptance. Earlier observer and
294
+ incidental-prose harness failures were corrected without product exceptions.
295
+
296
+ ## Native macOS service continuation — partial acceptance
297
+
298
+ The current compiled source controller passed real launchd install/start/status/
299
+ stop/uninstall against the published0.1.1 managed runtime in an unused, isolated
300
+ per-user registration. A concurrent graceful-drain control-closure failure was
301
+ reproduced and corrected with an authoritative ownership-retirement barrier.
302
+ 22 focused shutdown/frontend/control/CLI regressions, typecheck and build pass.
303
+ The final registration, plist and owned state were removed; cloud stayed disabled
304
+ and no official connection or real-work session was used.
305
+
306
+ See [native service evidence](plans/2026-11-11-native-service-acceptance.md).
307
+ Independent review closed a reproduced replacement-owner race with fresh post-probe
308
+ supervisor/runtime liveness checks. The November12 continuation below additionally
309
+ accepts native macOS upgrade/rollback with a real published bootstrap and synthetic
310
+ candidates. The November12 native Linux/Windows gates also pass as recorded above;
311
+ a next immutable public release and public-to-public delivery remain open.
312
+ Published0.1.1 does not contain the later source corrections.
313
+
314
+ ## Packaged rollback continuation — 2026-11-12
315
+
316
+ The local macOS packaged smoke now exercises production `queueUpdate` and the
317
+ retained supervisor with three real npm-installed synthetic package versions:
318
+ 9000.0.1→9000.0.2 succeeds; compatible9000.0.3 exits before runtime readiness,
319
+ and the supervisor returns to9000.0.2. Authenticated status confirms the recovered
320
+ version. Bootstrap/previous remain9000.0.1, failed9000.0.3 is recorded, and
321
+ pending/activating are absent. The retained aliased frontend and final clean
322
+ shutdown also pass. Only disposable failed-candidate package bytes are altered.
323
+
324
+ `npm run build` passes. The first expanded smoke stops during fixture setup
325
+ because its new import accidentally omitted `managedEntry`; no supervisor starts.
326
+ After restoring that import, the exact smoke passes in133.54seconds, including
327
+ owned-process/file cleanup. This is not a newly green full unit suite or new
328
+ hosted-platform result. That smoke installs no native login service and changes no
329
+ official daemon, cloud, real session or public package. The separate installed
330
+ macOS journey is recorded below; Linux/Windows observations remain open.
331
+
332
+ ## Installed macOS upgrade continuation — 2026-11-12
333
+
334
+ An actual launchd test exposes raw-path ownership rejection after macOS resolves
335
+ `/tmp` to `/private/tmp`. Canonical parent aliases now require ordinary leaves,
336
+ equal device/inode and equal real paths; leaf symlinks and foreign files remain
337
+ rejected. All10service-lifecycle consumers, typecheck and build pass; independent
338
+ OpenCode review finds no blocker. Distinct hard links/bind mounts remain refused.
339
+
340
+ The real installed-service journey passes in181.29seconds: verified public0.1.1
341
+ bootstrap, current9000.0.2 synthetic activation, failed9000.0.3 startup, recovery
342
+ to9000.0.2, then normal stop/uninstall with registration/plist/owned successful-run
343
+ files removed. An earlier fixture missed the required client-ID prefix; that
344
+ `INVALID_CONFIG` startup failure is not a product defect. First-run cleanup safely
345
+ used its independently established canonical definition before the product fix.
346
+ No real official connection or cloud operation occurred. Details and remaining
347
+ public-release/platform limits: [native service evidence](plans/2026-11-11-native-service-acceptance.md).
348
+
349
+
350
+ ## Approved identity cutover — locally verified
351
+
352
+ The owner approved the complete rename to **MoRemote CLI** on 2026-11-10:
353
+ repository/command `moremote-cli`, current public npm `@moxuli/moremote`, entry `bin/moremote-cli.js`,
354
+ `MOREMOTE_CLI_HOME`, state `MoRemoteCLI` on macOS/Windows and `moremote-cli`
355
+ on Linux, and services `com.moremote.cli` / `moremote-cli.service` / `MoRemoteCLI`.
356
+ Ownership/runtime/client/managed-package identities move together.
357
+ At the original rename checkpoint there was no released package or installed
358
+ service to migrate: no compatibility aliases or automatic adoption of old state.
359
+ The later0.1.0/0.1.1 publications are recorded below. Foreign-resource protections remain strict.
360
+ The `companionHello` role, crypto salt/envelope schema, APNs categories and
361
+ app/Keychain identities are unchanged.
362
+
363
+ The source/documentation cutover and root-directory move are complete. Parent
364
+ verified the renamed source, real compiled command, isolated local state and
365
+ package contents; independent source review accepted the identity contract.
366
+ Historical local acceptance below used the former `moremote-companion` identity;
367
+ its execution transcript remains historically accurate.
368
+
369
+ The owner also approved proceeding toward cloud/Apple activation. Exact
370
+ resource, key, permission and billing-sensitive mutations still require
371
+ point-of-risk interactive confirmation. No production or device acceptance is
372
+ claimed by this approval; publication and everyday-host service installation
373
+ remain separate gates.
374
+
375
+ ## Managed updates and release — local acceptance complete
376
+
377
+ The owner authorized public scoped npm identity `@moxuli/moremote`, retained
378
+ private bootstrap/supervisor and cycle-safe automatic runtime activation.
379
+ Native service/state/executable identities remain unchanged.
380
+ See [decision](decisions/0001-managed-updates.md), [specification](specs/06-managed-updates.md),
381
+ [plan](plans/2026-11-10-managed-updates.md) and [publication prerequisites](releasing.md).
382
+
383
+ The parent exercised the real packaged upgrade9000.0.1→9000.0.2, retained
384
+ bootstrap/previous version, frontend through a parent symlink and clean owned
385
+ shutdown. No everyday service was installed. The first full126-case run had123
386
+ passes and three lifecycle-readiness failures; after correction, all21focused
387
+ control/initialization/frontend cases, types, build and packaged smoke passed.
388
+ Do not describe those separate runs as a newly green full suite.
389
+
390
+ Independent source review's four findings are closed: initialization cleanup,
391
+ termination/parent-death propagation, prerelease precedence and exact scoped
392
+ npm registry pinning. The final control-response/readiness delta also has no
393
+ actionable P1/P2 finding. Cross-provider review timed out without a report; the
394
+ completed independent-context review is not represented as cross-vendor approval.
395
+
396
+ Public GitHub repository `moxuli/moremote-cli` exists. The owner authorized the
397
+ first public0.1.0 release and reuse of an existing locally protected publishing
398
+ token; its npm identity is verified without disclosing the credential. No new
399
+ token or npm login is required. Existing organization secret `NPM_TOKEN` is
400
+ restricted to this selected CLI repository; the release publish step reuses it.
@@ -0,0 +1,115 @@
1
+ Workstation0.1.0 publication is independently visible through the anonymous npm
2
+ registry. Published tarball SHA256 is
3
+ `6bf3cab16245745f5f9d43026687cff880ca081f106f195d6abe40a169c5efd6`;
4
+ registry SHA1 matches and a fresh exact public install runs version/help/
5
+ configure/status with cloud off, no runtime/pairs and no installed service.
6
+ Initial asynchronous404 processing was observed; publication was not repeated.
7
+
8
+ Hosted CI42821005843 accepts Ubuntu24.04 and macOS15 check/build/package-upgrade;
9
+ Windows2025 reports8control-transport failures (112pass/10explicit POSIX skips).
10
+ The correction is patch0.1.1: generation-bound transport selection preserves the
11
+ published strict runtime shape; framed peers avoid Windows half-close, while
12
+ known legacy POSIX transport is selected before exactly one write, never replayed.
13
+ Historical0.1.0 Windows EOF control remains explicitly unavailable/unknown;
14
+ managed stop requires real supervisor/runtime retirement evidence.
15
+
16
+ Final types,35focused control/lifecycle/CLI consumers, build and actual published
17
+ 0.1.0 retained-bootstrap→0.1.1 archive upgrade pass. The latter verifies active/
18
+ previous selection, both transport generations, selected frontend and clean
19
+ shutdown without a service/cloud/official-data mutation. Independent review
20
+ closes the mixed-transport finding with no remaining actionable P1/P2 issue.
21
+ Hosted CI42826719991 passes all three jobs: Ubuntu24.04, macOS15 and
22
+ Windows2025, including each platform's check/build, release identity validation
23
+ and real packaged upgrade. Source is `dad3d964b9ab144b646316a543e5d36151f8c210`.
24
+ Tagv0.1.1 targets that exact source. Automatic Release42827612987 completed
25
+ successfully using the existing organization secret: check/build, packaged
26
+ upgrade, deterministic artifact, signed GitHub provenance, npm submission and
27
+ GitHub Release all passed. No new token, login or trusted-publisher setup.
28
+
29
+ Independent anonymous npm catalog read confirms latest0.1.1; a fresh installation
30
+ by exact public package name runs0.1.1. The downloaded GitHub asset matches its
31
+ SHA256SUMS and npm's SHA1/SHA512 integrity. GitHub asset SHA256:
32
+ `358574ca750d27c8a116743cd729d7ab830c41fc17045ddfa46ff808ff3bba3b`.
33
+ The actual release asset separately runs configure/status with cloud off and
34
+ no runtime/service. Both submissions initially reported asynchronous processing;
35
+ the same immutable version was never republished.
36
+
37
+ Release: https://github.com/moxuli/moremote-cli/releases/tag/v0.1.1
38
+ Environment `npm-release` has a `v*` tag-only deployment policy; no new secret
39
+ was created.
40
+
41
+ ## Locally accepted implementation
42
+
43
+ Real CLI configure/check/pair/run/status/service-install/unpair/cloud-disable/update/stop/uninstall; per-user ownership adapters; one-phone deadline-bounded proof activation; WebCrypto HKDF/AES-GCM; standalone02/03/04 contracts and independent envelope/bearer vectors; actual official SDK narrow observation/send/question/approval adapter; SQLite FULL-sync dispatch/control/occurrence/attention journal; bounded encrypted state. Independent-review corrections include endpoint-authenticated cancel/revoke, immutable acknowledgements, source/generation request bindings, exact question mapping, monotonic receipts, separate24h minimal audit retention and attention invalidation. No builds, tests, formatters, actual user services or real host session mutations have been run by this worker; dependency installation used --ignore-scripts.
44
+
45
+ The retention wording has independent static Stage A approval. Final operation and lifecycle re-reviews report no remaining findings in their scoped corrections. Executed acceptance is recorded below; it does not replace production or cross-platform service gates.
46
+
47
+ The final targeted lifecycle re-review also found no remaining findings among its original six defects and two staged-socket/XML ownership residuals. This covers the inspected source corrections and regression source, not broad security approval or executed platform/service acceptance.
48
+
49
+ ## Verification journal — 2026-11-10
50
+
51
+ Evidence below was reported by the integration owner; implementation workers did not run checks.
52
+
53
+ - Initial combined check attempt timed out after900seconds. Both SDK-wire modes had failed after approximately13seconds each; leaked fixture resources prevented clean process exit and assertion-stack reporting. Build was not reached.
54
+ - Corrected synthetic timeline ranges from start/end to the pinned protocol's startSeq/endSeq, validated complete synthetic responses with official schemas, and supplied the required subscriptionId in release responses. All behavioral assertions remain.
55
+ - Fixture teardown now owns every SDK, socket, server, journal and timer; it closes the wire before SDK disposal, bounds cleanup waits, propagates fixture errors and runs on failure/timeout. It does not wait indefinitely for a release RPC.
56
+ - Focused owner run: `node --import tsx --test tests/official-wire.test.ts` passed2/2 (legacy and owned subscriptions) in26.7seconds, with no hang.
57
+ - Remaining selection: typecheck passed; the runner reported66passing entries and one failure caused only by a strict stderr wording assertion encountering Node's legitimate SQLite experimental warning. The incidental exact-output assertion was removed, preserving exit-failure and no-private-child-output invariants; its focused regression then passed1/1. Warnings were not suppressed. The already-passed two wire consumers were excluded from that remaining selection; one empty wire-file runner entry is not an extra behavior test.
58
+ - Build then passed. Actual compiled bin help and version commands both succeeded; version is0.1.0. No single combined full-suite green run is claimed.
59
+ - Actual three-party journey passed: compiled CLI configured and authenticated read-only to an isolated official0.15.3 daemon; native production Kit/CryptoKit enrolled through actual Pages→Worker→SQLite and verified the exact daemon activation proof.
60
+ - Actual foreground runtime status was cloud-enabled with one active synthetic pair, no runtime error and no installed service. A native immutable command retry to a nonexistent synthetic target received an authenticated rejection, not execution; encrypted revoke obtained the companion's durable authenticated acknowledgement, followed by narrow post-revoke outcome audit.
61
+ - Public-source privacy check found no private owner/account/team/production identifiers. No official agent was created, no model invoked, no real session mutated, and no public release or cloud deployment occurred.
62
+ - Renamed-tree combined `npm run check` passed typecheck,100/100 behavioral tests
63
+ and build. Actual compiled help/version/configure/check/status all exited0 in
64
+ temporary `MOREMOTE_CLI_HOME`, cloud off and no runtime/service/official
65
+ connection. Package dry-run contains54files, the canonical bin and no obsolete
66
+ runtime identity in packaged bin/dist; no package was published.
67
+ - Cost corrections stop active-pair GET/acknowledged state/receipt amplification
68
+ and bound relay-retired recovery. HTTP quota/operator pauses preserve fixed
69
+ deadlines, original immutable bytes and independent origin cadence.
70
+ - Initial Retry-After selection failed11/24 before correction. Its focused29case
71
+ selection passed. A later independent P1 review exposed pause expiry inside a
72
+ slow official snapshot; the real-runtime regression failed with PUT preceding
73
+ the required GET controls. The cycle-fence correction then passed31/31 focused
74
+ cases plus typecheck/build. This delta is not a newly run combined full suite.
75
+ - Independent P1 re-review closed with no new blockers. Multi-origin/multiple-pair
76
+ actual runtime behavior remains unexercised beyond the scoped client/fixture
77
+ checks; source review is not cross-platform or production acceptance.
78
+
79
+
80
+ ## Reproduction commands
81
+
82
+ 1. npm ci --ignore-scripts
83
+ 2. npm run check
84
+ 3. node bin/moremote-cli.js --help
85
+ 4. node bin/moremote-cli.js --version
86
+ 5. With a synthetic temporary MOREMOTE_CLI_HOME, run check, configure, status. Do not install services in ordinary CI.
87
+ 6. Against an explicitly isolated official0.15.3 daemon: configure its exact target/home, check --connect, then run; inspect traffic for only narrow subscriptions/read RPCs and no heartbeat/read acknowledgement/push registration. Use synthetic conversations for explicit send and actual pending question/approval tests. Verify accepted admission separately from agent completion and simulate socket loss after dispatch without replay.
88
+ 7. Run the independent cloud’s local SQLite-backed Worker, configure explicit loopback development at both ends, pair a synthetic endpoint using the public contract, submit an encrypted command and validate its exact encrypted receipt. No repository runtime imports are needed.
89
+
90
+ ### Read-only isolated official smoke
91
+
92
+ Use an already-authorized isolated0.15.3 daemon, empty isolated user home and an unused selected port. Do not point this at everyday Paseo data. The companion commands are:
93
+
94
+ ```sh
95
+ HOME="$SANDBOX/user" PASEO_PASSWORD= node bin/moremote-cli.js configure --data-dir "$SANDBOX/cli" --paseo-home "$SANDBOX/daemon" --target "127.0.0.1:$PASEO_TEST_PORT"
96
+ HOME="$SANDBOX/user" PASEO_PASSWORD= node bin/moremote-cli.js check --connect --data-dir "$SANDBOX/cli"
97
+ ```
98
+
99
+ If no isolated daemon exists, an operator can explicitly authorize and run `paseo onboard --home "$SANDBOX/daemon" --listen "127.0.0.1:$PASEO_TEST_PORT" --no-relay --no-mcp --voice disable --json` with HOME set to "$SANDBOX/user"; afterward `paseo daemon stop --home "$SANDBOX/daemon"`. The owner exercised this isolated read-only setup for local acceptance. It neither created an agent nor called a provider/model. Reuse an already-authorized isolated daemon instead of starting a second one during verification.
100
+
101
+ The actual SDK synthetic-wire cases are `tests/official-wire.test.ts` (waits for the real10s liveness ping; asserts no presence/read/Expo; loses admission ack then reconnects without resend) and `tests/official-permission-wire.test.ts` (real structured question response/resolution, same-ID replacement rejection and lost resolution without resend). These are not mock adapter echoes and do not call a real model.
102
+
103
+ ### Upstream license evidence
104
+
105
+ Official tag v0.15.3 points to commit d91ae138cb931447635e94296023414a58bedcc5. Its root LICENSE expressly grants Apache-2.0 for non-third-party Paseo code and retains third-party terms; matching client/protocol package sources are version0.15.3. Full text and immutable primary URLs are in licenses/Paseo-0.15.3.txt and NOTICE. npm package license fields are absent and were not treated as evidence; no signed npm/source attestation is claimed.
106
+
107
+ ## External gates / substrate gaps
108
+
109
+ - Independent specification and quality/security reviews and frozen local check results belong to the integration owner.
110
+ - Hosted cross-platform CI, exactv0.1.1 tag, npm publication, signed provenance and GitHub assets are verified above. Environment deployment is `v*`-tag-only. No broader branch/tag Ruleset or trusted-publisher migration is claimed.
111
+ - The native macOS/Linux/Windows managers now have the scoped acceptance recorded above. Public-to-public next-version activation and corresponding published-version rollback still require their own release evidence; synthetic QA versions are not that proof.
112
+ - No everyday login service, real-work-session send/approval or paid-model task was exercised. The temporary macOS registration was removed; it is not daily-host deployment.
113
+ - One authorized synthetic sandbox alert was observed on a real iPad through the independent cloud/app path. This is not genuine permission/reply execution, production TestFlight delivery or terminated-app acceptance; emulation and artifact installation do not establish those gates.
114
+
115
+ Continue from this file and living specs, not private machine history. Record exercised evidence here before claiming a verified release.
@@ -0,0 +1,35 @@
1
+ # Custom API origin release — 2026-11-15
2
+
3
+ The owner requested the custom notification hostname while retaining Alibaba DNS
4
+ and conditional CLI publication. Missing-origin setup/discovery and expert
5
+ pairing now share that verified default; saved Pages/custom origins and exact
6
+ pending authority remain unchanged.
7
+
8
+ Reviewed sourcec38e2b07adc88e6fd5f4e18ef9c41fb87b51f9b9 was merged/pushed to
9
+ main. CI43611899292 passed complete checks and real packaged upgrades on
10
+ macOS15, Ubuntu24.04 and Windows2025 before tagv0.1.6. Release43612669196
11
+ repeated full checks, upgrade/rollback and deterministic packing, then used the
12
+ existing scoped repository secret to publish with provenance and create the
13
+ matching GitHub Release. No new credential, permission or service was created.
14
+
15
+ Anonymous registry read/download/install verifies0.1.6 and actual compiled new
16
+ defaults. npm integrity matches; GitHub archive and SHA256SUMS match the npm
17
+ archive exactly. Published SHA256: `cce7ddf6d1913ba27e8e07697cc73dbaa575d76b8be7f02fb62603654b29127b`.
18
+ Install used a disposable prefix and independent empty npm configuration, no
19
+ inherited publishing credentials and disabled install scripts. Only --version
20
+ was invoked; it reported0.1.6 without registering a real service.
21
+
22
+ The initial local236/238 result exposed real service queries outside temporary
23
+ HOME. A shared read-query fixture fixed isolation without weakening production
24
+ ownership/foreign-data refusal. A subsequent review found Windows preload paths
25
+ needed file URLs; focused5/5 and final actual three-platform CI pass. Acceptance
26
+ uses the weaker independent-context Codex fallback, not cross-vendor proof.
27
+
28
+ Local main packing initially reused prior ignored dist outputs. Rebuilding then
29
+ exposed two obsolete dist/activity outputs left by incremental tsc. Fresh public
30
+ CI packaging contains neither; every shared archived file byte matches local
31
+ source builds. Neither obsolete local archive was published. Original failed
32
+ preflight/packing observations remain retained rather than labeled successful.
33
+
34
+ No App release, everyday service update or physical push delivery is implied.
35
+ Complete prior state remains in [[2026-11-14-state-before-0.1.6-part-1]] and [[2026-11-14-state-before-0.1.6-part-2]].
@@ -0,0 +1,41 @@
1
+ # Informative encrypted notifications — local, unreleased
2
+
3
+ ## Root cause and correction
4
+
5
+ Released alerts contain generic provider copy; the app had no notification service
6
+ extension. Renaming that fallback cannot identify a private conversation without
7
+ endpoint display support. Attention now optionally carries separately encrypted
8
+ bounded session/computer/current-content presentation, with unchanged legacy
9
+ route plaintext, exact identity, independent nonce, expiry and durable retries.
10
+ Only current assistant prose or exact current questions/approvals/errors enter
11
+ presentation. Generated UI source, reasoning and tool output are excluded.
12
+
13
+ The official SDK may optionally read one30-entry canonical tail per completion,
14
+ with five-second timeout and two concurrent tails. Live and snapshot/reconnect
15
+ recovery use the same current-turn/terminal identity fence; recovery does not
16
+ block control/directory polling. Existing successful authenticated relay responses
17
+ passively advertise support; old relays receive legacy events without another
18
+ request. Once journaled, the original exact bytes remain immutable.
19
+
20
+ ## Evidence and review
21
+
22
+ The added presentation tests initially failed against the absent module. The real
23
+ SDK recovery-body regression then failed against the empty snapshot preview; its
24
+ final legacy/owned wire tests pass2/2, including independently decrypted durable
25
+ preview and unchanged legacy route. Full frozen `npm run check` passes types,
26
+ 243 tests with zero failures and compilation. The first full run had one timed
27
+ quota fixture failure under concurrent load; the exact isolated test passed, and
28
+ this fresh complete243-test run is the accepted final gate. No assertion or
29
+ production timeout was weakened.
30
+
31
+ Independent read-only review found the recovery omission and an app workspace
32
+ name precedence issue. Both are fixed and independently re-reviewed. Three
33
+ external-provider attempts produced no usable review (account hold, network reset,
34
+ timeout); the completed independent-context review is not a multi-vendor approval.
35
+
36
+ ## Boundary
37
+
38
+ Source remains on `fix/notification-content-1115`, unreleased after0.1.6. No
39
+ package/tag publication, real everyday service installation or real host/session
40
+ mutation occurred. Cloud/APNs transport and physical extension display are
41
+ separate acceptance gates; tests use synthetic wire/keys/temp journals only.