@moxuli/moremote 0.1.1 → 0.1.4

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 (45) hide show
  1. package/README.md +85 -7
  2. package/bin/moremote-cli.js +11 -4
  3. package/dist/activity.d.ts +79 -0
  4. package/dist/activity.js +193 -0
  5. package/dist/cli.js +36 -41
  6. package/dist/cloud-client.d.ts +13 -4
  7. package/dist/cloud-client.js +60 -15
  8. package/dist/config.d.ts +7 -0
  9. package/dist/config.js +23 -4
  10. package/dist/control.d.ts +1 -0
  11. package/dist/control.js +9 -0
  12. package/dist/crypto.d.ts +1 -1
  13. package/dist/crypto.js +2 -2
  14. package/dist/enrollment-files.d.ts +37 -0
  15. package/dist/enrollment-files.js +225 -0
  16. package/dist/enrollment-protocol.d.ts +50 -0
  17. package/dist/enrollment-protocol.js +44 -0
  18. package/dist/journal.js +2 -1
  19. package/dist/local-enrollment.d.ts +25 -0
  20. package/dist/local-enrollment.js +160 -0
  21. package/dist/official-client.d.ts +87 -6
  22. package/dist/official-client.js +135 -32
  23. package/dist/operations.d.ts +1 -0
  24. package/dist/operations.js +24 -4
  25. package/dist/projection.d.ts +7 -2
  26. package/dist/resources.d.ts +2 -1
  27. package/dist/resources.js +69 -32
  28. package/dist/runtime.d.ts +10 -1
  29. package/dist/runtime.js +111 -10
  30. package/dist/service.js +43 -8
  31. package/dist/setup-upgrade.d.ts +2 -0
  32. package/dist/setup-upgrade.js +65 -0
  33. package/dist/setup.d.ts +12 -0
  34. package/dist/setup.js +38 -0
  35. package/dist/supervisor.d.ts +1 -0
  36. package/dist/supervisor.js +44 -1
  37. package/docs/README.md +4 -3
  38. package/docs/STATE.md +327 -10
  39. package/docs/configuration.md +119 -5
  40. package/docs/plans/2026-11-11-native-service-acceptance.md +168 -0
  41. package/docs/specs/03-api-contract.md +122 -2
  42. package/docs/specs/04-control-and-receipt-lifecycle.md +12 -0
  43. package/docs/specs/05-endpoint-and-lifecycle.md +126 -2
  44. package/docs/specs/06-managed-updates.md +34 -1
  45. package/package.json +2 -2
@@ -8,6 +8,7 @@ export interface ManagedRuntime {
8
8
  export declare function launchRuntime(entry: string, dir: string, onReady?: () => void): ManagedRuntime;
9
9
  export declare function drainRuntime(runtime: ManagedRuntime): Promise<number>;
10
10
  export declare function startupHealthy(runtime: ManagedRuntime, signal?: AbortSignal, grace?: number, deadline?: number, cancel?: () => boolean): Promise<boolean>;
11
+ export declare function stopManagedRuntime(dir: string): Promise<void>;
11
12
  export declare function runSupervisor(dir: string, timing?: {
12
13
  pollMs?: number;
13
14
  startupGraceMs?: number;
@@ -2,7 +2,8 @@ import { spawn } from 'node:child_process';
2
2
  import { setTimeout as sleep } from 'node:timers/promises';
3
3
  import { managedEntry } from './service.js';
4
4
  import { checkForUpdate, compatibleEntry } from './updater.js';
5
- import { readUpdateState, writeUpdateState, updateLock, supervisorStopRequested } from './update-state.js';
5
+ import { readUpdateState, writeUpdateState, updateLock, supervisorStopRequested, requestSupervisorStop, supervisorRunning } from './update-state.js';
6
+ import { requestControl, runtimeHasLiveOwner } from './control.js';
6
7
  export function launchRuntime(entry, dir, onReady = () => { }) {
7
8
  const child = spawn(process.execPath, [entry, 'run', '--data-dir', dir], { stdio: ['ignore', 'inherit', 'inherit', 'ipc'], windowsHide: true, env: { ...process.env, MOREMOTE_MANAGED_CHILD: '1' } });
8
9
  let ready = false, closed = false;
@@ -32,6 +33,48 @@ export async function startupHealthy(runtime, signal, grace = 10000, deadline =
32
33
  }
33
34
  return false;
34
35
  }
36
+ async function stopRuntime(dir) {
37
+ if (!await requestControl(dir, 'stop'))
38
+ return;
39
+ for (let i = 0; i < 300; i++) {
40
+ await sleep(200);
41
+ if (!await requestControl(dir, 'status'))
42
+ return;
43
+ }
44
+ throw Error('STOP_TIMEOUT');
45
+ }
46
+ export async function stopManagedRuntime(dir) {
47
+ requestSupervisorStop(dir);
48
+ let controlUnavailable = false;
49
+ // Native service shutdown may close IPC before its owned records are retired.
50
+ // A transport's absent generation is not proof that no replacement is alive.
51
+ try {
52
+ await stopRuntime(dir);
53
+ }
54
+ catch (error) {
55
+ if (error instanceof Error && (error.message === 'LEGACY_WINDOWS_CONTROL_UNAVAILABLE' || error.message === 'CONTROL_CONNECTION_CLOSED') && readUpdateState(dir))
56
+ controlUnavailable = true;
57
+ else
58
+ throw error;
59
+ }
60
+ if (!readUpdateState(dir)) {
61
+ if (runtimeHasLiveOwner(dir))
62
+ throw Error('STOP_TIMEOUT');
63
+ return;
64
+ }
65
+ for (let i = 0; i < 900; i++) {
66
+ if (!supervisorRunning(dir)) {
67
+ if (controlUnavailable && await requestControl(dir, 'status'))
68
+ throw Error('STOP_TIMEOUT');
69
+ // Revalidate synchronously after the awaited probe, including lock-only startup.
70
+ if (supervisorRunning(dir) || runtimeHasLiveOwner(dir))
71
+ throw Error('STOP_TIMEOUT');
72
+ return;
73
+ }
74
+ await sleep(200);
75
+ }
76
+ throw Error('SUPERVISOR_STOP_TIMEOUT');
77
+ }
35
78
  export async function runSupervisor(dir, timing = {}) {
36
79
  return updateLock(dir, async () => {
37
80
  let state = readUpdateState(dir);
package/docs/README.md CHANGED
@@ -1,9 +1,10 @@
1
1
  # Documentation index
2
2
 
3
3
  **MoRemote CLI**: independent optional `moremote-cli` repository/command,
4
- public npm `@moxuli/moremote`, over unmodified Paseo.
5
- STATE distinguishes historical pre-rename acceptance, renamed-tree checks and
6
- separately gated cloud/Apple activation.
4
+ public npm `@moxuli/moremote`0.1.1, over unmodified Paseo.
5
+ Activity/widget support is local unreleased source, not part of that published
6
+ package. [[STATE]] separates targeted local evidence from native/device/live
7
+ cloud acceptance, which remains pending for these new surfaces; cloud is disabled.
7
8
 
8
9
  - [Current state and external gates](STATE.md)
9
10
  - [Architecture](specs/01-architecture.md)
package/docs/STATE.md CHANGED
@@ -1,8 +1,308 @@
1
- # Current state — 2026-11-10
1
+ # Current state — 2026-11-13
2
+
3
+ ## 0.1.4 release candidate — owner-authorized, not yet published
4
+
5
+ - Pending questions/approvals now use a stable current-occurrence clock, not an
6
+ older task-completion clock. Actual SDK delayed-current/snapshot regressions
7
+ first reproduce resolution/replacement resurrection, then the observation fence
8
+ prevents journal, binding and notification renewal. Actual same-batch SDK reply
9
+ consumers also reproduce caller-continuation resurrection before repair: adapter
10
+ journal ownership removes duplicate synchronization, source fingerprints prevent
11
+ old request text acquiring a replacement binding, and crypto rechecks currentness.
12
+ Cached question/approval consumers fail before exact occurrence capture/drain
13
+ binding, then notifications10/10 pass without old clocks consuming new IDs.
14
+ Final unchanged-input full check passes251/251,typecheck and build. Independent
15
+ Stage A closes both lifecycle blockers; final quality re-review and hosted
16
+ three-platform verification remain pending before immutable publication.
17
+ - Quality review catches observed in-place mutation followed by valid rename;
18
+ both real regressions fail before the pre-retry guard, then resource24/24 pass.
19
+ Hosted40e1b73 passes Linux/macOS but Windows rejects test-injected replacement
20
+ with a live handle. Tests now verify real refusal, complete original contents
21
+ and identity, then actual post-close replacement and strict unsafe-file refusal;
22
+ no production error guard or platform coverage is removed. Narrow review passes.
23
+
24
+ - Ordinary config rename is now distinguished from an unsafe resource: at most
25
+ three reopen attempts, independent descriptor/path validation, retired handles
26
+ discarded, strict no-follow/user/private-mode/link/byte/encoding checks retained.
27
+ Same-inode content changes remain rejected. Real rename regressions reproduce
28
+ the failure before repair, then22resource consumers and the original2runtime
29
+ cases pass. Final unchanged-input full check passes235/235,typecheck and build.
30
+ Stage A narrow review passes; independent quality/security review and fresh
31
+ hosted three-platform verification remain in progress before publication.
32
+
33
+ - Hosted1df64e0 exercises all new behaviors successfully on Windows, but its
34
+ new cache fixture removes the directory before closing SQLite. Combine cleanup
35
+ into one ordered close-then-remove hook; preserve all behavior assertions and
36
+ rerun the full matrix on the corrected test source. Production bytes are unchanged.
37
+
38
+ - Corrected8e4e065 Windows cleanup passes; macOS then rejects signaling an
39
+ already stopped wrapper's old process group. Preserve independent lock/control/
40
+ supervisor/exit assertions and skip redundant group signaling only after those
41
+ shutdown proofs. All4actual local lifecycle consumers pass; narrow review agrees.
42
+
43
+ - Exact tagv0.1.3 and its successful three-platform CI43380589650 are retained.
44
+ Release43381419784 fails its full check before packaging/publication: concurrent
45
+ normal runtime config replacement triggers FOREIGN_RESOURCE_LIMIT in a read.
46
+ Publish and GitHub Release steps are skipped; no0.1.3 package is submitted.
47
+ Preserve that immutable failed tag and prepare0.1.4 after a deterministic repair.
48
+
49
+ - First hosted run43378427840 correctly rejects three cross-environment fixture
50
+ defects: inherited config/service paths, unsupported Windows POSIX-mode equality,
51
+ and an unbound synthetic Paseo home whose local mismatch check had accidentally
52
+ contacted the ordinary daemon read-only. Bind the exact fixture home and require
53
+ its real handshake, no cloud calls, unchanged config and private-output absence.
54
+ - Stricter pending-endpoint controls return409 before activation. Runtime now
55
+ activates only after official identity and original expiry/revocation checks;
56
+ no command/state lane exists in that cycle, and the next cycle validates controls.
57
+ Shared origin quota fences and fixed activation proof remain intact. Independent
58
+ narrow review finds no blocker. Final unchanged-input full check passes221/221
59
+ and build; hosted portability/packaged smoke are being rerun on this exact delta.
60
+
61
+ - Integrated51942a0 and reviewed the final enrollment/setup and packaging delta.
62
+ Exact public0.1.2 archive bytes now live in the test fixtures with verified npm
63
+ SHA1/SHA512 and matching recorded GitHub SHA256, independent of workstation caches.
64
+ - Final full check passes typecheck,221/221 tests and build. Three actual retained
65
+ public0.1.2 migration consumers pass. Real packaged activation/failed-start
66
+ rollback/retained frontend and clean shutdown pass; no everyday service is installed.
67
+ - Release validation accepts additive capability metadata while retaining the
68
+ strict1/1/1 protocol tuple and exact source/package capability equality.
69
+ Constructor-scoped fixture isolation removes inherited operator credentials;
70
+ the smoke retries only read-only unproven-stage probes under its live owned supervisor.
71
+ - Independent Stage A and Stage B reviews find no remaining scoped blocker.
72
+ Main integration, hosted checks, immutable npm/GitHub publication and independent
73
+ registry receipt remain pending. The production cloud remains unchanged.
2
74
 
3
75
  ## Scope
4
76
 
5
- Owner-approved notification/scoped-delivery first iteration; Apache-2.0. Standalone Node24 companion targeting inspected official SDK/protocol 0.15.3. Existing iOS protocol-vector floor is independent and unchanged. OpenUI, system extensions and broader native surfaces belong to later app iterations.
77
+ Owner-approved notification/scoped delivery and local activity/widget integration; 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.
78
+
79
+ ## Unreleased single-pairing enrollment — source0.1.3, locally accepted
80
+
81
+ - Official Paseo pairing is the only normal user pairing. Explicit
82
+ `setup --yes` prepares the optional owned CLI service; a connected native
83
+ client exchanges the existing per-phone offer through official authenticated
84
+ file APIs. No second QR, pasted invitation, terminal command or new relay
85
+ configuration is required in the app.
86
+ - Discovery is private and bounded; original request identity/expiry, canonical
87
+ offer and cloud-create bytes are durable before network I/O. Activation and
88
+ expiry remove the private handoff. Revocation, retained active phones, custom
89
+ origin, daemon pinning and managed-update opt-out remain authoritative.
90
+ - Confirmed review findings are fixed: duplicate runtime startup never rewrites
91
+ configuration; setup prepares packages before acquiring shared runtime
92
+ ownership, then holds it across load/authenticate/save. A concurrent runtime
93
+ either wins before config loading or is refused. Config readers/writers share
94
+ the524288-byte encoded bound; old managed0.1.2 setup selects a verified
95
+ enrollment-capable current package instead of silently enabling old code.
96
+ - Optional admission performs at most one cloud-create attempt per cycle with
97
+ its own3-second deadline. Unknown results retain exact retry bytes. No cloud
98
+ endpoint, recursive dispatch, polling budget or production deployment changes.
99
+ - Node24.13.0 typecheck passes. The final six-file selection passes37/38;
100
+ its remaining source-setup assertion incorrectly demanded absence of an
101
+ internal managed directory. That implementation-detail assertion is removed,
102
+ while actual package-manager refusal and service-entry checks remain. The
103
+ corrected consumer passes independently and the compiled build passes.
104
+ Both new setup/runtime interleavings failed before the ownership correction.
105
+ - Actual unmodified official Paseo0.15.4 and the native transport exchange the
106
+ canonical offer, verify the real native claim and unchanged activation proof,
107
+ and remove exact private request/response files. One cloud-create body and
108
+ zero official agents are observed. The cloud is a local in-process test
109
+ double; this is not production, physical-device or APNs acceptance.
110
+ - Independent-context source re-review closes the scoped native/CLI findings.
111
+ The weaker same-provider route is explicit; unavailable external native
112
+ reviews are not approvals. Temporary probe code/state are removed, with
113
+ redacted receipts retained outside the repository.
114
+ - Source0.1.3 remains unpublished. Public0.1.2, shared production and existing
115
+ official data are unchanged. No npm tag, TestFlight upload or phone install
116
+ is implied.
117
+
118
+ ## Unreleased Share-first onboarding delta — locally verified
119
+
120
+ - Approved cross-repository plan: MoRemote
121
+ `docs/plans/2026-11-13-share-first-onboarding.md`; CLI ownership is source,
122
+ focused consumers and public docs only. No publication or deployment.
123
+ - Explicit `pair` opts in to cloud, uses the production endpoint only when no
124
+ origin exists, and reuses existing official listen/credential discovery.
125
+ Origin validation, daemon pinning, custom targets/origins and retained
126
+ pair authority remain intact. Plain load/check/status remain passive.
127
+ - Task snapshots carry genuine provider and ISO-8601 creation time alongside
128
+ last-user time, through existing bounded projection and authenticated state.
129
+ Widget equality includes the new meaningful metadata. No assistant-update
130
+ substitution for user recency.
131
+ - Added actual CLI enrollment consumers with a synthetic official WebSocket
132
+ and isolated relay, passive diagnostics/custom authority/invalid-origin and
133
+ daemon-pin cases; added real-SDK encrypted task metadata consumers.
134
+ - Node24.13.0 typecheck, 22 focused pair-onboarding/task-projection/activity/CLI
135
+ consumers, and compiled build pass. The actual SDK/HTTP boundary exercises
136
+ passive diagnostics, authenticated enrollment, custom authority and encrypted
137
+ metadata without production enrollment or official-file changes.
138
+ - Independent read-only review `run-20261113030053-9f69faa3` approves the scoped
139
+ implementation. The same-provider fallback is explicit; this is not physical
140
+ acceptance or a new package release. Public0.1.2 and its cached receiver remain
141
+ unchanged.
142
+
143
+ ## Native service acceptance — 2026-11-12
144
+
145
+ - Actual Ubuntu26.04/Node24.13.0/systemd259 user-service acceptance passes:
146
+ install/start, authenticated status, QA0.1.1 → synthetic9000.0.2 activation,
147
+ failed9000.0.3 startup rollback, normal stop/uninstall and independent absence
148
+ of the unit, definition and live runtime. No cloud or real official daemon I/O.
149
+ - Initial Windows QA exposed missing native-import BOM and current-reader BOM
150
+ handling. Fresh-context specification review then found that persisting a BOM
151
+ breaks unchanged public0.1.1 runtimes, despite the current/current QA success.
152
+ - The current installer keeps persistent ownership XML BOM-free. Only a private
153
+ transient import outside shared state has a BOM; it is removed before `/Run`
154
+ and on `/Create` failure. Retained0.1.1 consumers remain usable for bootstrap
155
+ and rollback without a storage migration.
156
+ - Both new consumer regressions first failed. All20focused lifecycle/resource
157
+ consumers, typecheck and build then pass. The frozen reader matches the
158
+ independently downloaded public0.1.1 module bytes.
159
+ - The new actual Windows Task Scheduler journey passes in183.86seconds:
160
+ unchanged registry0.1.1 bootstrap → current synthetic9000.0.2 → deliberately
161
+ failed9000.0.3 → recovered9000.0.2, then normal stop/uninstall. Task,
162
+ definition, control endpoint and live supervisor/runtime are independently absent.
163
+ - Fresh-context specification and quality re-review close the scoped blocker.
164
+ This is the explicitly weaker same-provider fallback, not cross-vendor approval.
165
+ Earlier168.23second QA acceptance and unavailable provider reviews remain
166
+ historical evidence in [[2026-11-11-native-service-acceptance]].
167
+ - The candidate is unpublished QA bytes, not a public-to-public release. No real
168
+ official host, paid provider, cloud operation or everyday login service is used.
169
+ - The shared production cloud remains persistently enabled under the owner's
170
+ later decision; these isolated native tests neither use nor disable it. Older
171
+ temporary-window shutdown receipts below are historical, not current policy.
172
+
173
+ ## Released0.1.2 — 2026-11-12
174
+
175
+ - Package and lock root identities select0.1.2; no dependency or compatibility
176
+ tuple changes. Owner-approved tagv0.1.2 targets739c76008ea583fa86bfb023dafaa17a3ea9adf4.
177
+ - The combined check passes typecheck and180/181 tests. Its remaining legacy-wire
178
+ case incorrectly requires an extra read for an old event that may be coalesced.
179
+ The test now drains the actual wire and retains the phone-visible no-new-notice
180
+ and unchanged-ciphertext assertions without demanding that incidental RPC.
181
+ - Both actual SDK wire variants then pass2/2. Build, real packaged activation/
182
+ failed-start rollback/aliased frontend/clean stop, release identity validation
183
+ and deterministic0.1.2 packaging pass. These overlapping runs are not a new
184
+ single green full-suite result.
185
+ - Hosted CI43227228037 passes full check/build, release validation and real
186
+ packaged upgrade on Ubuntu24.04, macOS15 and Windows2025.
187
+ Automatic Release43232455123 passes check/build, upgrade smoke, deterministic
188
+ packaging, existing-secret npm publication/provenance and GitHub Release.
189
+ - Anonymous registry reads independently confirm version/latest0.1.2 after
190
+ asynchronous processing; publication is never repeated. Downloaded GitHub
191
+ bytes match SHA256SUMS and npm SHA1/SHA512 integrity. Archive SHA256:
192
+ `845fd98470964303a6a86dc696e64c47ac1e7b1ce90b59cd730cdec56d64f9bb`.
193
+ - Actual public0.1.1 installation/retained supervisor discovers and downloads
194
+ public0.1.2 through its unchanged normal background scheduler, not a custom
195
+ fetcher, direct queue, altered package or fake clock. Exact authenticated
196
+ status becomes0.1.2; bootstrap/previous remain0.1.1; retained frontend returns
197
+ 0.1.2; normal stop exits0 and all owned processes/files are removed, in80.12s.
198
+ No login service, real official connection or cloud operation occurs.
199
+ An initial fixture prepopulates an unowned state directory and is correctly
200
+ rejected before any process starts; initialization is corrected outside the
201
+ managed state, preserving strict ownership. Its exact failed fixture is removed.
202
+ - Production device reply/approval and remote activity/widget delivery still
203
+ require their separate acceptance; the release does not claim those gates.
204
+ - Release: https://github.com/moxuli/moremote-cli/releases/tag/v0.1.2
205
+
206
+ ## Released activity/widget integration — production acceptance open
207
+
208
+ - Published install identity is **`@moxuli/moremote`0.1.2**; command/runtime
209
+ remains `moremote-cli`, with existing per-platform service identities.
210
+ Activity/widget changes are included; physical production acceptance remains open.
211
+ - Implemented locally: authenticated encrypted per-task interests and activity
212
+ state, an owned optional2s host lane with250ms exact fallback reads, meaningful
213
+ keyed widget fingerprints on existing snapshot publication, and normal-only
214
+ quota pauses that preserve eligible terminal recovery. Commands/controls do
215
+ not await activity work; shutdown/drain joins it before SDK/journal close.
216
+ - Limits/expiry/error/dataflow truth lives in [[configuration]] and
217
+ [[specs/03-api-contract#Opt-in task activities and widget reloads]].
218
+ Interest expiry is at most8h (8 per pair); state at most600s, fresh acknowledged
219
+ renewal around8min. Unknown admissions retain exact bytes. Widget registration
220
+ expires24h with native renewal around12h. Missing tasks never imply finish.
221
+ - Integration-owner-reported evidence: CLI typecheck and57 tests across
222
+ `tests/activity.test.ts`, `tests/cloud-retry.test.ts` and
223
+ `tests/runtime-receipt.test.ts` passed. This is targeted local evidence, not
224
+ a newly green full suite, released artifact, or physical/device acceptance.
225
+ - Next gates: independent integration review and owner verification of the final
226
+ delta; authorized native Live Activity/widget rendering, stale/offline and
227
+ token replacement/expiry acceptance; separately authorized live cloud/APNs
228
+ delivery. APNs200 is provider admission, not delivery. Historical alert proof
229
+ below does not cover either new surface.
230
+ - A later owner-approved bounded physical acceptance observed all four attention
231
+ kinds through the actual official mock → companion → cloud → sandbox APNs path.
232
+ Duplicate completion and premature request-resolution bugs were exposed and
233
+ corrected locally; this is not real paid-model or production-service evidence.
234
+ - The request lifecycle and canonical terminal-identity corrections pass13focused
235
+ consumers plus typecheck. A later reverse-order wire regression first failed
236
+ both SDK variants, then both passed with typecheck after observation-order
237
+ fencing. Independent same-provider review reports no blocker; the preferred
238
+ cross-vendor provider was unavailable.
239
+ - Earlier bounded sandbox windows restored disabled service and production
240
+ provider secrets. The later November12 owner decision now keeps the existing
241
+ production service enabled; no temporary watchdog or sandbox swap is allowed.
242
+ Genuine device reply/approval receipts and remote ActivityKit/WidgetKit
243
+ acceptance remain open. No real-work session or new release is implied.
244
+ - Fresh local end-to-end action acceptance passes against the unchanged official
245
+ development mock, production runtime, real Pages/Worker/SQLite and a compiled
246
+ unchanged native Kit/CryptoKit slice. Exact send and bound plan denial each
247
+ execute once and produce authenticated accepted/resolved receipts; initial and
248
+ post-settlement identical retries cannot redispatch or change receipts. Both
249
+ SQLite journals retain exactly two settled operations. This is not physical
250
+ locked-notification UI or whole native-package acceptance. Earlier observer and
251
+ incidental-prose harness failures were corrected without product exceptions.
252
+
253
+ ## Native macOS service continuation — partial acceptance
254
+
255
+ The current compiled source controller passed real launchd install/start/status/
256
+ stop/uninstall against the published0.1.1 managed runtime in an unused, isolated
257
+ per-user registration. A concurrent graceful-drain control-closure failure was
258
+ reproduced and corrected with an authoritative ownership-retirement barrier.
259
+ 22 focused shutdown/frontend/control/CLI regressions, typecheck and build pass.
260
+ The final registration, plist and owned state were removed; cloud stayed disabled
261
+ and no official connection or real-work session was used.
262
+
263
+ See [native service evidence](plans/2026-11-11-native-service-acceptance.md).
264
+ Independent review closed a reproduced replacement-owner race with fresh post-probe
265
+ supervisor/runtime liveness checks. The November12 continuation below additionally
266
+ accepts native macOS upgrade/rollback with a real published bootstrap and synthetic
267
+ candidates. The November12 native Linux/Windows gates also pass as recorded above;
268
+ a next immutable public release and public-to-public delivery remain open.
269
+ Published0.1.1 does not contain the later source corrections.
270
+
271
+ ## Packaged rollback continuation — 2026-11-12
272
+
273
+ The local macOS packaged smoke now exercises production `queueUpdate` and the
274
+ retained supervisor with three real npm-installed synthetic package versions:
275
+ 9000.0.1→9000.0.2 succeeds; compatible9000.0.3 exits before runtime readiness,
276
+ and the supervisor returns to9000.0.2. Authenticated status confirms the recovered
277
+ version. Bootstrap/previous remain9000.0.1, failed9000.0.3 is recorded, and
278
+ pending/activating are absent. The retained aliased frontend and final clean
279
+ shutdown also pass. Only disposable failed-candidate package bytes are altered.
280
+
281
+ `npm run build` passes. The first expanded smoke stops during fixture setup
282
+ because its new import accidentally omitted `managedEntry`; no supervisor starts.
283
+ After restoring that import, the exact smoke passes in133.54seconds, including
284
+ owned-process/file cleanup. This is not a newly green full unit suite or new
285
+ hosted-platform result. That smoke installs no native login service and changes no
286
+ official daemon, cloud, real session or public package. The separate installed
287
+ macOS journey is recorded below; Linux/Windows observations remain open.
288
+
289
+ ## Installed macOS upgrade continuation — 2026-11-12
290
+
291
+ An actual launchd test exposes raw-path ownership rejection after macOS resolves
292
+ `/tmp` to `/private/tmp`. Canonical parent aliases now require ordinary leaves,
293
+ equal device/inode and equal real paths; leaf symlinks and foreign files remain
294
+ rejected. All10service-lifecycle consumers, typecheck and build pass; independent
295
+ OpenCode review finds no blocker. Distinct hard links/bind mounts remain refused.
296
+
297
+ The real installed-service journey passes in181.29seconds: verified public0.1.1
298
+ bootstrap, current9000.0.2 synthetic activation, failed9000.0.3 startup, recovery
299
+ to9000.0.2, then normal stop/uninstall with registration/plist/owned successful-run
300
+ files removed. An earlier fixture missed the required client-ID prefix; that
301
+ `INVALID_CONFIG` startup failure is not a product defect. First-run cleanup safely
302
+ used its independently established canonical definition before the product fix.
303
+ No real official connection or cloud operation occurred. Details and remaining
304
+ public-release/platform limits: [native service evidence](plans/2026-11-11-native-service-acceptance.md).
305
+
6
306
 
7
307
  ## Approved identity cutover — locally verified
8
308
 
@@ -10,9 +310,10 @@ The owner approved the complete rename to **MoRemote CLI** on 2026-11-10:
10
310
  repository/command `moremote-cli`, current public npm `@moxuli/moremote`, entry `bin/moremote-cli.js`,
11
311
  `MOREMOTE_CLI_HOME`, state `MoRemoteCLI` on macOS/Windows and `moremote-cli`
12
312
  on Linux, and services `com.moremote.cli` / `moremote-cli.service` / `MoRemoteCLI`.
13
- Ownership/runtime/client/managed-package identities move together. There is no
14
- released package or installed service to migrate: no compatibility aliases or
15
- automatic adoption of old state. Foreign-resource protections remain strict.
313
+ Ownership/runtime/client/managed-package identities move together.
314
+ At the original rename checkpoint there was no released package or installed
315
+ service to migrate: no compatibility aliases or automatic adoption of old state.
316
+ The later0.1.0/0.1.1 publications are recorded below. Foreign-resource protections remain strict.
16
317
  The `companionHello` role, crypto salt/envelope schema, APNs categories and
17
318
  app/Keychain identities are unchanged.
18
319
 
@@ -74,7 +375,23 @@ Final types,35focused control/lifecycle/CLI consumers, build and actual publishe
74
375
  previous selection, both transport generations, selected frontend and clean
75
376
  shutdown without a service/cloud/official-data mutation. Independent review
76
377
  closes the mixed-transport finding with no remaining actionable P1/P2 issue.
77
- Hosted final Windows acceptance and tag publishing still need receiver results.
378
+ Hosted CI42826719991 passes all three jobs: Ubuntu24.04, macOS15 and
379
+ Windows2025, including each platform's check/build, release identity validation
380
+ and real packaged upgrade. Source is `dad3d964b9ab144b646316a543e5d36151f8c210`.
381
+ Tagv0.1.1 targets that exact source. Automatic Release42827612987 completed
382
+ successfully using the existing organization secret: check/build, packaged
383
+ upgrade, deterministic artifact, signed GitHub provenance, npm submission and
384
+ GitHub Release all passed. No new token, login or trusted-publisher setup.
385
+
386
+ Independent anonymous npm catalog read confirms latest0.1.1; a fresh installation
387
+ by exact public package name runs0.1.1. The downloaded GitHub asset matches its
388
+ SHA256SUMS and npm's SHA1/SHA512 integrity. GitHub asset SHA256:
389
+ `358574ca750d27c8a116743cd729d7ab830c41fc17045ddfa46ff808ff3bba3b`.
390
+ The actual release asset separately runs configure/status with cloud off and
391
+ no runtime/service. Both submissions initially reported asynchronous processing;
392
+ the same immutable version was never republished.
393
+
394
+ Release: https://github.com/moxuli/moremote-cli/releases/tag/v0.1.1
78
395
  Environment `npm-release` has a `v*` tag-only deployment policy; no new secret
79
396
  was created.
80
397
 
@@ -147,9 +464,9 @@ Official tag v0.15.3 points to commit d91ae138cb931447635e94296023414a58bedcc5.
147
464
  ## External gates / substrate gaps
148
465
 
149
466
  - Independent specification and quality/security reviews and frozen local check results belong to the integration owner.
150
- - Public GitHub repository exists; CI/release workflow source is prepared but no hosted run, tag/release, npm publication, trusted publisher, scheduler or branch/tag protection is claimed. Unpublished npm404 is a real update failure, persisted with bounded discovery rather than a retry storm or fake success.
151
- - Real per-user launchd/systemd/Windows logon-task installation requires point-of-use operator authorization and testing on each OS; adapters are source, not evidence of another OS’s acceptance.
152
- - No everyday login service, real work-session action, DNS/cloud deployment, paid model call, Apple key/capability change or public publication has been performed.
153
- - Production Cloudflare storage/network reachability, Apple provider signing and app topic/environment, actual iOS app enrollment and physical APNs delivery are real external setup/acceptance requirements. Emulation is not proof of delivery.
467
+ - 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.
468
+ - 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.
469
+ - 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.
470
+ - 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.
154
471
 
155
472
  Continue from this file and living specs, not private machine history. Record exercised evidence here before claiming a verified release.
@@ -8,6 +8,66 @@ Each pairing retains its explicit API origin through retirement. Local revokedAt
8
8
 
9
9
  MOREMOTE_CLI_HOME or --data-dir overrides platform state defaults: ~/Library/Application Support/MoRemoteCLI on macOS, LOCALAPPDATA/MoRemoteCLI on Windows, XDG_STATE_HOME/moremote-cli (fallback ~/.local/state/moremote-cli) on Linux. PASEO_HOME selects the official read-only home, PASEO_PASSWORD matches official CLI password precedence. Only paseo.pid and local-credential are read under the official home, only at an explicit connection. No credential discovery scans or official writes. The unpublished former moremote-companion identity has no command/env aliases or automatic state adoption.
10
10
 
11
+ Unreleased single-pairing onboarding uses explicit `setup --yes`: stop only the
12
+ owned CLI runtime/service, reload its latest configuration, authenticate the
13
+ existing official daemon and preserve its exact identity, then enable cloud and
14
+ local enrollment before installing/starting the existing owned service.
15
+ Configured custom HTTPS origin/target, existing active/revoked phones and update
16
+ policy are preserved. An absent origin selects
17
+ `https://moremote-cloud-ingress.pages.dev`. Source checkout without managed state
18
+ binds its own current frontend and stays manual-update. Installed packages and
19
+ retained managed state use capability-aware setup: if selected code predates
20
+ enrollment, explicit setup installs/verifies the exact current version before
21
+ enabling the feature, then moves active/bootstrap while retaining previous
22
+ packages, pairs/custom origin and the independent auto-update opt-out.
23
+ `SETUP_CURRENT_PACKAGE_UNAVAILABLE`/`SETUP_CAPABILITY_REQUIRED` are failures,
24
+ never enabled success or an older-package fallback. Nothing patches/upgrades
25
+ official Paseo or global tools. This capability requires CLI0.1.4 or later.
26
+
27
+ Optional schema-1 fields are `localEnrollment:{home:<absolute user home>}` and
28
+ at most16 `enrollmentRequests`. Only explicit setup supplies that home; ordinary
29
+ `run`/tests with legacy configuration never create discovery in the real HOME.
30
+ Each durable record stores the exact request bytes, SHA256 fingerprint, parsed
31
+ request, original pair/offer, exact cloud-create JSON bytes and confirmed-create
32
+ flag. Per-pair `automaticClientId` and `automaticRequestId` retain app/request
33
+ identity without replacing an old pair. Runtime-cycle ownership serializes all enrollment/config changes;
34
+ there is no second config writer or background watcher.
35
+
36
+ Config reads, owned-resource validation and atomic writes share a524288-byte
37
+ bound, including the serialized trailing newline. This accommodates16 maximum
38
+ 4096-byte requests even when literal tab/newline bytes expand during JSON
39
+ serialization. Oversize writes fail before replacing any config. Fresh `run`
40
+ initializes config only after acquiring runtime ownership; duplicate `run`
41
+ refuses without rewriting a live enrollment snapshot.
42
+
43
+ The private tree is `<home>/.moremote-cli-connect/<sha256(UTF8 daemonServerId)>/`;
44
+ its parent/host/request/response directories have owned markers and POSIX0700.
45
+ Descriptor and secret responses are0600; official-created requests may be0644
46
+ inside the private request directory. Reject links, foreign markers/owners,
47
+ collisions and competing runtime locks before cloud creation. Windows relies on
48
+ the user-profile ACL. Only this owned local tree is written, not official files.
49
+ The app gets the real home via official directory suggestions, never a guessed
50
+ path. Descriptor includes the configured/default validated HTTPS `apiOrigin`,
51
+ which pins the original canonical offer's origin.
52
+
53
+ Unchanged request bytes resume the same endpoint and idempotent create bytes
54
+ through lost acknowledgements/restarts; changed bytes/client/daemon/expiry fail
55
+ closed. No more than16 request files are consumed per cycle and no more than16
56
+ pairs exist. At most one optional cloud-create attempt runs per cycle with its
57
+ own3s abort deadline; existing phones retain ordinary controls/command handling.
58
+ Descriptor lifetime90s/renewal30s; request/offer lifetime at most600s.
59
+ Activation/expiry removes private responses, expiry removes durable request
60
+ records. An old exact request remains disabled after revocation; only the app's
61
+ explicit fresh Enable request may create a new endpoint after prior retirement.
62
+ Full schemas and ownership behavior:
63
+ [single-pairing contract](specs/05-endpoint-and-lifecycle.md#single-pairing-local-enrollment-v1-unreleased).
64
+
65
+ Loading config, `check` and `status` do not create discovery, enable cloud,
66
+ select an origin, enroll or install a service; `check --connect` is read-only.
67
+ Manual `pair` remains expert-only and installs no service. Published0.1.2 lacks
68
+ `setup` and still requires explicit origin/cloud configuration before manual
69
+ pairing; this source delta is not published.
70
+
11
71
  ## Central limits (src/limits.ts)
12
72
 
13
73
  Envelope request128KiB; decrypted content64KiB; send text60000 UTF-8 bytes; command/control TTL300s; enrollment/state/attention maximum600s; receipt/controlReceipt maximum8KiB serialized envelope with600s attestation interval; future clock tolerance120s (never expiry grace). User payloads expire at original TTL, minimal encrypted receipts/evidence remain24h after original operation/control expiry. Receipt revision is persisted before I/O; control ack revision1 is immutable. At most1000 operations,1000 controls and1000 attention records per pairing,100 tasks/snapshot,10 pending requests/task,16 providers,8 windows/balances/provider. Raw enhanced request limit8KiB; whole state limit60000bytes. State refresh30s, polling3s backing off to30s, HTTP timeout20s, official connection/read15s, SDK mutation timeout per pinned upstream. Capacity errors never silently evict live authority.
@@ -15,11 +75,15 @@ HTTP response limit is5MiB, separately from the128KiB request limit; the relay c
15
75
  Local pair revocation tombstones are capped at4096, never evicting live protection. Exhaustion is an explicit failure. Running cleanup removes a tombstone only after its pairing credentials have been durably removed and all immutable child audit deadlines have passed. Offline configuration-only reads cannot prune revoked keys without their journal.
16
76
 
17
77
  HTTP429/503 may carry Retry-After as seconds or a canonical HTTP-date. Validate
18
- it, cap the wait at24hours and retain a fixed deadline per API origin. Paused
19
- origins make no repeated3second HTTP attempts; unrelated origins keep their own
20
- cadence. Once observed, a pause fences that origin for the remainder of the
21
- runtime cycle even if slow SDK work outlasts the deadline. The next cycle first
22
- reacquires controls before publication, receipt recovery or command acquisition.
78
+ it, cap the wait at24hours and retain a fixed deadline per API origin. By default,
79
+ paused origins make no repeated3second HTTP attempts; unrelated origins keep
80
+ their own cadence. Only429 `daily_work_limit` with `x-moremote-budget:normal`
81
+ and a future numeric `x-moremote-reset` consistent with Retry-After pauses normal
82
+ requests alone. Recovery routes still require server admission; hints grant no
83
+ authority. Missing/malformed hints, outages, disable and recovery exhaustion
84
+ retain origin-wide fences. Once observed, a pause fences its scope for the
85
+ remainder of the cycle even if slow SDK work outlasts the deadline. The next
86
+ cycle first reacquires controls before publication, receipt recovery or command acquisition.
23
87
  Never reseal/renew an action or automatically repeat an uncertain mutation.
24
88
 
25
89
  A successful upload acknowledges only those exact state/receipt bytes and
@@ -28,6 +92,56 @@ snapshots/receipt revisions are not retransmitted each poll. Relay disappearance
28
92
  or retirement fences execution but is not authenticated endpoint revocation.
29
93
  Retired recovery ends at original child audit deadlines without extending them.
30
94
 
95
+ ## Optional activity and widget surfaces (unreleased)
96
+
97
+ Published `@moxuli/moremote` remains0.1.1; these are local source changes,
98
+ not a new release or a reason to alter service/runtime identities. There is no
99
+ new CLI enable flag or separate activity-device command. Existing cloud opt-in,
100
+ active pairing and a compatible phone/relay are prerequisites; official-only
101
+ use remains independent. No deployment or device acceptance is implied.
102
+
103
+ | Surface | Bound / behavior |
104
+ | --- | --- |
105
+ | Activity interests | Phone-selected, encrypted and pinned to pair/subscription/daemon/task; at most8 live interests per pair, original lifetime at most8h. |
106
+ | Optional host work | Interest discovery no faster than30s; one owned2s cancellation-bounded lane, at most8 exact SDK fallback reads, each bounded250ms. Commands/controls do not await it; drain/stop cancels and joins before closing SDK/journal. |
107
+ | Activity state | At most600s, capped by interest expiry; serialized encrypted envelope at most3000bytes, title160/hostName80 characters. APNs body at most4096bytes with512bytes reserved for static attributes. |
108
+ | Activity renewal | Only acknowledged nonterminal state renews from a fresh official measurement with120s remaining (about8min). Unknown admissions retry identical bytes until expiry; semantic transitions can supersede progress. Missing tasks do not imply completion. |
109
+ | Widget registration | One current WidgetKit token per pair;24h expiry, native foreground renewal around12h with a fresh registration ID. Not the alert/activity token. |
110
+ | Widget reload | Pair-keyed meaningful-change fingerprint on existing state PUT; clocks alone do not trigger reloads. One coalesced signal per changed fingerprint/current registration; legacy envelope-only uploads do not queue pushes. |
111
+
112
+ The phone registers/deletes tokens and encrypted interests; the CLI never
113
+ registers an official daemon push token or downloads full chat/timeline for
114
+ these surfaces. The relay sees token/environment, IDs, opaque topic/fingerprint,
115
+ envelope times/sizes and ciphertext. Only paired endpoints decrypt task/title,
116
+ host/project and genuine usage values. Apple receives encrypted activity state
117
+ in `ContentState.payload`, or exactly `{aps:{"content-changed":true}}` for widgets.
118
+ Activity/widget pushes do not depend on alert admission or presence suppression.
119
+
120
+ Terminal recovery uses cached authenticated unexpired interests and fresh
121
+ snapshot facts before optional normal discovery; it needs no normal GET/state
122
+ upload. Only end/delete routes are recovery-eligible, not ordinary updates,
123
+ interest reads or registration. A404/409 publication rejection invalidates that
124
+ cached target; it does not authorize a replacement or a blind replay. Conflicting
125
+ same-registration bytes are409; replacement needs a fresh registration ID.
126
+ Relay retired-identity guards share a1000-entry cap and fail closed rather than
127
+ evicting live protection; guards last through original8h activity/24h widget
128
+ expiry. Delayed registration PUTs cannot roll back replacements; identity-exact
129
+ widget DELETEs and stale provider results cannot retire newer registrations.
130
+ Activity DELETE targets the subscription itself. Expiry never renews through
131
+ retry; stale/offline is not success.
132
+
133
+ The relay needs explicit `APNS_WIDGET_TOPIC` for the widget extension plus
134
+ `.push-type.widgets`; Live Activity topic is main `APNS_TOPIC` plus
135
+ `.push-type.liveactivity`. Environments must match configured APNs sending.
136
+ These are relay settings, not CLI configuration keys. Default-off, global
137
+ budgets, kill deadline and existing receipt priority remain unchanged.
138
+ Provider signing is inside the original10s attempt deadline; after signing,
139
+ the durable caller rechecks enabled state, active pair, exact current
140
+ registration/publication and expiry immediately before transport.
141
+ APNs200 is provider admission, never display/delivery proof. Physical Live
142
+ Activity, widget reload/freshness/offline behavior and live cloud/APNs acceptance
143
+ for this delta remain pending. Exact routes/crypto: [[specs/03-api-contract]].
144
+
31
145
  ## Service resources
32
146
 
33
147
  macOS: user Library/LaunchAgents/com.moremote.cli.plist. Linux: XDG_CONFIG_HOME/systemd/user/moremote-cli.service (fallback user .config). Windows: current-user task MoRemoteCLI and UTF-16 XML in CLI state, InteractiveToken/LeastPrivilege; built-in PowerShell checks exact existing task ownership before schtasks mutation. Marker binds the data-directory hash; manager registration/file ownership mismatch fails closed. A private CLI root marker refuses nonempty foreign directories and gates purge. No official Paseo service/resource is altered. Missing managers fail honestly.