@moxuli/moremote 0.1.1 → 0.1.2
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.
- package/README.md +48 -1
- package/dist/activity.d.ts +77 -0
- package/dist/activity.js +193 -0
- package/dist/cli.js +3 -34
- package/dist/cloud-client.d.ts +12 -3
- package/dist/cloud-client.js +59 -14
- package/dist/control.d.ts +1 -0
- package/dist/control.js +9 -0
- package/dist/crypto.d.ts +1 -1
- package/dist/crypto.js +2 -2
- package/dist/journal.js +2 -1
- package/dist/official-client.d.ts +72 -5
- package/dist/official-client.js +69 -7
- package/dist/projection.d.ts +5 -2
- package/dist/resources.js +2 -1
- package/dist/runtime.js +40 -4
- package/dist/service.js +43 -8
- package/dist/supervisor.d.ts +1 -0
- package/dist/supervisor.js +44 -1
- package/docs/README.md +4 -3
- package/docs/STATE.md +174 -10
- package/docs/configuration.md +59 -5
- package/docs/plans/2026-11-11-native-service-acceptance.md +168 -0
- package/docs/specs/03-api-contract.md +122 -2
- package/docs/specs/06-managed-updates.md +9 -1
- package/package.json +1 -1
package/docs/STATE.md
CHANGED
|
@@ -1,8 +1,155 @@
|
|
|
1
|
-
# Current state — 2026-11-
|
|
1
|
+
# Current state — 2026-11-12
|
|
2
2
|
|
|
3
3
|
## Scope
|
|
4
4
|
|
|
5
|
-
Owner-approved notification/scoped
|
|
5
|
+
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.
|
|
6
|
+
|
|
7
|
+
## Native service acceptance — 2026-11-12
|
|
8
|
+
|
|
9
|
+
- Actual Ubuntu26.04/Node24.13.0/systemd259 user-service acceptance passes:
|
|
10
|
+
install/start, authenticated status, QA0.1.1 → synthetic9000.0.2 activation,
|
|
11
|
+
failed9000.0.3 startup rollback, normal stop/uninstall and independent absence
|
|
12
|
+
of the unit, definition and live runtime. No cloud or real official daemon I/O.
|
|
13
|
+
- Initial Windows QA exposed missing native-import BOM and current-reader BOM
|
|
14
|
+
handling. Fresh-context specification review then found that persisting a BOM
|
|
15
|
+
breaks unchanged public0.1.1 runtimes, despite the current/current QA success.
|
|
16
|
+
- The current installer keeps persistent ownership XML BOM-free. Only a private
|
|
17
|
+
transient import outside shared state has a BOM; it is removed before `/Run`
|
|
18
|
+
and on `/Create` failure. Retained0.1.1 consumers remain usable for bootstrap
|
|
19
|
+
and rollback without a storage migration.
|
|
20
|
+
- Both new consumer regressions first failed. All20focused lifecycle/resource
|
|
21
|
+
consumers, typecheck and build then pass. The frozen reader matches the
|
|
22
|
+
independently downloaded public0.1.1 module bytes.
|
|
23
|
+
- The new actual Windows Task Scheduler journey passes in183.86seconds:
|
|
24
|
+
unchanged registry0.1.1 bootstrap → current synthetic9000.0.2 → deliberately
|
|
25
|
+
failed9000.0.3 → recovered9000.0.2, then normal stop/uninstall. Task,
|
|
26
|
+
definition, control endpoint and live supervisor/runtime are independently absent.
|
|
27
|
+
- Fresh-context specification and quality re-review close the scoped blocker.
|
|
28
|
+
This is the explicitly weaker same-provider fallback, not cross-vendor approval.
|
|
29
|
+
Earlier168.23second QA acceptance and unavailable provider reviews remain
|
|
30
|
+
historical evidence in [[2026-11-11-native-service-acceptance]].
|
|
31
|
+
- The candidate is unpublished QA bytes, not a public-to-public release. No real
|
|
32
|
+
official host, paid provider, cloud operation or everyday login service is used.
|
|
33
|
+
- The shared production cloud remains persistently enabled under the owner's
|
|
34
|
+
later decision; these isolated native tests neither use nor disable it. Older
|
|
35
|
+
temporary-window shutdown receipts below are historical, not current policy.
|
|
36
|
+
|
|
37
|
+
## Local0.1.2 candidate preparation
|
|
38
|
+
|
|
39
|
+
- Package and lock root identities now select0.1.2; no dependency or compatibility
|
|
40
|
+
tuple changes. No tag, push, npm publication or GitHub Release has occurred.
|
|
41
|
+
- The combined check passes typecheck and180/181 tests. Its remaining legacy-wire
|
|
42
|
+
case incorrectly requires an extra read for an old event that may be coalesced.
|
|
43
|
+
The test now drains the actual wire and retains the phone-visible no-new-notice
|
|
44
|
+
and unchanged-ciphertext assertions without demanding that incidental RPC.
|
|
45
|
+
- Both actual SDK wire variants then pass2/2. Build, real packaged activation/
|
|
46
|
+
failed-start rollback/aliased frontend/clean stop, release identity validation
|
|
47
|
+
and deterministic0.1.2 packaging pass. These overlapping runs are not a new
|
|
48
|
+
single green full-suite result.
|
|
49
|
+
- Hosted cross-platform CI, exact immutable publication/receiver installation
|
|
50
|
+
and public-to-public activation remain release gates. Production device reply,
|
|
51
|
+
approval and remote activity/widget delivery still require their own evidence.
|
|
52
|
+
|
|
53
|
+
## Active work — unreleased activity/widget integration
|
|
54
|
+
|
|
55
|
+
- Published install identity is **`@moxuli/moremote`0.1.1**; command/runtime
|
|
56
|
+
remains `moremote-cli`, with existing per-platform service identities.
|
|
57
|
+
Local activity/widget changes are **not released**; local0.1.2 is a candidate.
|
|
58
|
+
- Implemented locally: authenticated encrypted per-task interests and activity
|
|
59
|
+
state, an owned optional2s host lane with250ms exact fallback reads, meaningful
|
|
60
|
+
keyed widget fingerprints on existing snapshot publication, and normal-only
|
|
61
|
+
quota pauses that preserve eligible terminal recovery. Commands/controls do
|
|
62
|
+
not await activity work; shutdown/drain joins it before SDK/journal close.
|
|
63
|
+
- Limits/expiry/error/dataflow truth lives in [[configuration]] and
|
|
64
|
+
[[specs/03-api-contract#Opt-in task activities and widget reloads]].
|
|
65
|
+
Interest expiry is at most8h (8 per pair); state at most600s, fresh acknowledged
|
|
66
|
+
renewal around8min. Unknown admissions retain exact bytes. Widget registration
|
|
67
|
+
expires24h with native renewal around12h. Missing tasks never imply finish.
|
|
68
|
+
- Integration-owner-reported evidence: CLI typecheck and57 tests across
|
|
69
|
+
`tests/activity.test.ts`, `tests/cloud-retry.test.ts` and
|
|
70
|
+
`tests/runtime-receipt.test.ts` passed. This is targeted local evidence, not
|
|
71
|
+
a newly green full suite, released artifact, or physical/device acceptance.
|
|
72
|
+
- Next gates: independent integration review and owner verification of the final
|
|
73
|
+
delta; authorized native Live Activity/widget rendering, stale/offline and
|
|
74
|
+
token replacement/expiry acceptance; separately authorized live cloud/APNs
|
|
75
|
+
delivery. APNs200 is provider admission, not delivery. Historical alert proof
|
|
76
|
+
below does not cover either new surface.
|
|
77
|
+
- A later owner-approved bounded physical acceptance observed all four attention
|
|
78
|
+
kinds through the actual official mock → companion → cloud → sandbox APNs path.
|
|
79
|
+
Duplicate completion and premature request-resolution bugs were exposed and
|
|
80
|
+
corrected locally; this is not real paid-model or production-service evidence.
|
|
81
|
+
- The request lifecycle and canonical terminal-identity corrections pass13focused
|
|
82
|
+
consumers plus typecheck. A later reverse-order wire regression first failed
|
|
83
|
+
both SDK variants, then both passed with typecheck after observation-order
|
|
84
|
+
fencing. Independent same-provider review reports no blocker; the preferred
|
|
85
|
+
cross-vendor provider was unavailable.
|
|
86
|
+
- Earlier bounded sandbox windows restored disabled service and production
|
|
87
|
+
provider secrets. The later November12 owner decision now keeps the existing
|
|
88
|
+
production service enabled; no temporary watchdog or sandbox swap is allowed.
|
|
89
|
+
Genuine device reply/approval receipts and remote ActivityKit/WidgetKit
|
|
90
|
+
acceptance remain open. No real-work session or new release is implied.
|
|
91
|
+
- Fresh local end-to-end action acceptance passes against the unchanged official
|
|
92
|
+
development mock, production runtime, real Pages/Worker/SQLite and a compiled
|
|
93
|
+
unchanged native Kit/CryptoKit slice. Exact send and bound plan denial each
|
|
94
|
+
execute once and produce authenticated accepted/resolved receipts; initial and
|
|
95
|
+
post-settlement identical retries cannot redispatch or change receipts. Both
|
|
96
|
+
SQLite journals retain exactly two settled operations. This is not physical
|
|
97
|
+
locked-notification UI or whole native-package acceptance. Earlier observer and
|
|
98
|
+
incidental-prose harness failures were corrected without product exceptions.
|
|
99
|
+
|
|
100
|
+
## Native macOS service continuation — partial acceptance
|
|
101
|
+
|
|
102
|
+
The current compiled source controller passed real launchd install/start/status/
|
|
103
|
+
stop/uninstall against the published0.1.1 managed runtime in an unused, isolated
|
|
104
|
+
per-user registration. A concurrent graceful-drain control-closure failure was
|
|
105
|
+
reproduced and corrected with an authoritative ownership-retirement barrier.
|
|
106
|
+
22 focused shutdown/frontend/control/CLI regressions, typecheck and build pass.
|
|
107
|
+
The final registration, plist and owned state were removed; cloud stayed disabled
|
|
108
|
+
and no official connection or real-work session was used.
|
|
109
|
+
|
|
110
|
+
See [native service evidence](plans/2026-11-11-native-service-acceptance.md).
|
|
111
|
+
Independent review closed a reproduced replacement-owner race with fresh post-probe
|
|
112
|
+
supervisor/runtime liveness checks. The November12 continuation below additionally
|
|
113
|
+
accepts native macOS upgrade/rollback with a real published bootstrap and synthetic
|
|
114
|
+
candidates. The November12 native Linux/Windows gates also pass as recorded above;
|
|
115
|
+
a next immutable public release and public-to-public delivery remain open.
|
|
116
|
+
Published0.1.1 does not contain the later source corrections.
|
|
117
|
+
|
|
118
|
+
## Packaged rollback continuation — 2026-11-12
|
|
119
|
+
|
|
120
|
+
The local macOS packaged smoke now exercises production `queueUpdate` and the
|
|
121
|
+
retained supervisor with three real npm-installed synthetic package versions:
|
|
122
|
+
9000.0.1→9000.0.2 succeeds; compatible9000.0.3 exits before runtime readiness,
|
|
123
|
+
and the supervisor returns to9000.0.2. Authenticated status confirms the recovered
|
|
124
|
+
version. Bootstrap/previous remain9000.0.1, failed9000.0.3 is recorded, and
|
|
125
|
+
pending/activating are absent. The retained aliased frontend and final clean
|
|
126
|
+
shutdown also pass. Only disposable failed-candidate package bytes are altered.
|
|
127
|
+
|
|
128
|
+
`npm run build` passes. The first expanded smoke stops during fixture setup
|
|
129
|
+
because its new import accidentally omitted `managedEntry`; no supervisor starts.
|
|
130
|
+
After restoring that import, the exact smoke passes in133.54seconds, including
|
|
131
|
+
owned-process/file cleanup. This is not a newly green full unit suite or new
|
|
132
|
+
hosted-platform result. That smoke installs no native login service and changes no
|
|
133
|
+
official daemon, cloud, real session or public package. The separate installed
|
|
134
|
+
macOS journey is recorded below; Linux/Windows observations remain open.
|
|
135
|
+
|
|
136
|
+
## Installed macOS upgrade continuation — 2026-11-12
|
|
137
|
+
|
|
138
|
+
An actual launchd test exposes raw-path ownership rejection after macOS resolves
|
|
139
|
+
`/tmp` to `/private/tmp`. Canonical parent aliases now require ordinary leaves,
|
|
140
|
+
equal device/inode and equal real paths; leaf symlinks and foreign files remain
|
|
141
|
+
rejected. All10service-lifecycle consumers, typecheck and build pass; independent
|
|
142
|
+
OpenCode review finds no blocker. Distinct hard links/bind mounts remain refused.
|
|
143
|
+
|
|
144
|
+
The real installed-service journey passes in181.29seconds: verified public0.1.1
|
|
145
|
+
bootstrap, current9000.0.2 synthetic activation, failed9000.0.3 startup, recovery
|
|
146
|
+
to9000.0.2, then normal stop/uninstall with registration/plist/owned successful-run
|
|
147
|
+
files removed. An earlier fixture missed the required client-ID prefix; that
|
|
148
|
+
`INVALID_CONFIG` startup failure is not a product defect. First-run cleanup safely
|
|
149
|
+
used its independently established canonical definition before the product fix.
|
|
150
|
+
No real official connection or cloud operation occurred. Details and remaining
|
|
151
|
+
public-release/platform limits: [native service evidence](plans/2026-11-11-native-service-acceptance.md).
|
|
152
|
+
|
|
6
153
|
|
|
7
154
|
## Approved identity cutover — locally verified
|
|
8
155
|
|
|
@@ -10,9 +157,10 @@ The owner approved the complete rename to **MoRemote CLI** on 2026-11-10:
|
|
|
10
157
|
repository/command `moremote-cli`, current public npm `@moxuli/moremote`, entry `bin/moremote-cli.js`,
|
|
11
158
|
`MOREMOTE_CLI_HOME`, state `MoRemoteCLI` on macOS/Windows and `moremote-cli`
|
|
12
159
|
on Linux, and services `com.moremote.cli` / `moremote-cli.service` / `MoRemoteCLI`.
|
|
13
|
-
Ownership/runtime/client/managed-package identities move together.
|
|
14
|
-
|
|
15
|
-
automatic adoption of old state.
|
|
160
|
+
Ownership/runtime/client/managed-package identities move together.
|
|
161
|
+
At the original rename checkpoint there was no released package or installed
|
|
162
|
+
service to migrate: no compatibility aliases or automatic adoption of old state.
|
|
163
|
+
The later0.1.0/0.1.1 publications are recorded below. Foreign-resource protections remain strict.
|
|
16
164
|
The `companionHello` role, crypto salt/envelope schema, APNs categories and
|
|
17
165
|
app/Keychain identities are unchanged.
|
|
18
166
|
|
|
@@ -74,7 +222,23 @@ Final types,35focused control/lifecycle/CLI consumers, build and actual publishe
|
|
|
74
222
|
previous selection, both transport generations, selected frontend and clean
|
|
75
223
|
shutdown without a service/cloud/official-data mutation. Independent review
|
|
76
224
|
closes the mixed-transport finding with no remaining actionable P1/P2 issue.
|
|
77
|
-
Hosted
|
|
225
|
+
Hosted CI42826719991 passes all three jobs: Ubuntu24.04, macOS15 and
|
|
226
|
+
Windows2025, including each platform's check/build, release identity validation
|
|
227
|
+
and real packaged upgrade. Source is `dad3d964b9ab144b646316a543e5d36151f8c210`.
|
|
228
|
+
Tagv0.1.1 targets that exact source. Automatic Release42827612987 completed
|
|
229
|
+
successfully using the existing organization secret: check/build, packaged
|
|
230
|
+
upgrade, deterministic artifact, signed GitHub provenance, npm submission and
|
|
231
|
+
GitHub Release all passed. No new token, login or trusted-publisher setup.
|
|
232
|
+
|
|
233
|
+
Independent anonymous npm catalog read confirms latest0.1.1; a fresh installation
|
|
234
|
+
by exact public package name runs0.1.1. The downloaded GitHub asset matches its
|
|
235
|
+
SHA256SUMS and npm's SHA1/SHA512 integrity. GitHub asset SHA256:
|
|
236
|
+
`358574ca750d27c8a116743cd729d7ab830c41fc17045ddfa46ff808ff3bba3b`.
|
|
237
|
+
The actual release asset separately runs configure/status with cloud off and
|
|
238
|
+
no runtime/service. Both submissions initially reported asynchronous processing;
|
|
239
|
+
the same immutable version was never republished.
|
|
240
|
+
|
|
241
|
+
Release: https://github.com/moxuli/moremote-cli/releases/tag/v0.1.1
|
|
78
242
|
Environment `npm-release` has a `v*` tag-only deployment policy; no new secret
|
|
79
243
|
was created.
|
|
80
244
|
|
|
@@ -147,9 +311,9 @@ Official tag v0.15.3 points to commit d91ae138cb931447635e94296023414a58bedcc5.
|
|
|
147
311
|
## External gates / substrate gaps
|
|
148
312
|
|
|
149
313
|
- Independent specification and quality/security reviews and frozen local check results belong to the integration owner.
|
|
150
|
-
-
|
|
151
|
-
-
|
|
152
|
-
- No everyday login service, real
|
|
153
|
-
-
|
|
314
|
+
- 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.
|
|
315
|
+
- 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.
|
|
316
|
+
- 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.
|
|
317
|
+
- 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
318
|
|
|
155
319
|
Continue from this file and living specs, not private machine history. Record exercised evidence here before claiming a verified release.
|
package/docs/configuration.md
CHANGED
|
@@ -15,11 +15,15 @@ HTTP response limit is5MiB, separately from the128KiB request limit; the relay c
|
|
|
15
15
|
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
16
|
|
|
17
17
|
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.
|
|
19
|
-
origins make no repeated3second HTTP attempts; unrelated origins keep
|
|
20
|
-
cadence.
|
|
21
|
-
|
|
22
|
-
|
|
18
|
+
it, cap the wait at24hours and retain a fixed deadline per API origin. By default,
|
|
19
|
+
paused origins make no repeated3second HTTP attempts; unrelated origins keep
|
|
20
|
+
their own cadence. Only429 `daily_work_limit` with `x-moremote-budget:normal`
|
|
21
|
+
and a future numeric `x-moremote-reset` consistent with Retry-After pauses normal
|
|
22
|
+
requests alone. Recovery routes still require server admission; hints grant no
|
|
23
|
+
authority. Missing/malformed hints, outages, disable and recovery exhaustion
|
|
24
|
+
retain origin-wide fences. Once observed, a pause fences its scope for the
|
|
25
|
+
remainder of the cycle even if slow SDK work outlasts the deadline. The next
|
|
26
|
+
cycle first reacquires controls before publication, receipt recovery or command acquisition.
|
|
23
27
|
Never reseal/renew an action or automatically repeat an uncertain mutation.
|
|
24
28
|
|
|
25
29
|
A successful upload acknowledges only those exact state/receipt bytes and
|
|
@@ -28,6 +32,56 @@ snapshots/receipt revisions are not retransmitted each poll. Relay disappearance
|
|
|
28
32
|
or retirement fences execution but is not authenticated endpoint revocation.
|
|
29
33
|
Retired recovery ends at original child audit deadlines without extending them.
|
|
30
34
|
|
|
35
|
+
## Optional activity and widget surfaces (unreleased)
|
|
36
|
+
|
|
37
|
+
Published `@moxuli/moremote` remains0.1.1; these are local source changes,
|
|
38
|
+
not a new release or a reason to alter service/runtime identities. There is no
|
|
39
|
+
new CLI enable flag or separate activity-device command. Existing cloud opt-in,
|
|
40
|
+
active pairing and a compatible phone/relay are prerequisites; official-only
|
|
41
|
+
use remains independent. No deployment or device acceptance is implied.
|
|
42
|
+
|
|
43
|
+
| Surface | Bound / behavior |
|
|
44
|
+
| --- | --- |
|
|
45
|
+
| Activity interests | Phone-selected, encrypted and pinned to pair/subscription/daemon/task; at most8 live interests per pair, original lifetime at most8h. |
|
|
46
|
+
| 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. |
|
|
47
|
+
| 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. |
|
|
48
|
+
| 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. |
|
|
49
|
+
| Widget registration | One current WidgetKit token per pair;24h expiry, native foreground renewal around12h with a fresh registration ID. Not the alert/activity token. |
|
|
50
|
+
| 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. |
|
|
51
|
+
|
|
52
|
+
The phone registers/deletes tokens and encrypted interests; the CLI never
|
|
53
|
+
registers an official daemon push token or downloads full chat/timeline for
|
|
54
|
+
these surfaces. The relay sees token/environment, IDs, opaque topic/fingerprint,
|
|
55
|
+
envelope times/sizes and ciphertext. Only paired endpoints decrypt task/title,
|
|
56
|
+
host/project and genuine usage values. Apple receives encrypted activity state
|
|
57
|
+
in `ContentState.payload`, or exactly `{aps:{"content-changed":true}}` for widgets.
|
|
58
|
+
Activity/widget pushes do not depend on alert admission or presence suppression.
|
|
59
|
+
|
|
60
|
+
Terminal recovery uses cached authenticated unexpired interests and fresh
|
|
61
|
+
snapshot facts before optional normal discovery; it needs no normal GET/state
|
|
62
|
+
upload. Only end/delete routes are recovery-eligible, not ordinary updates,
|
|
63
|
+
interest reads or registration. A404/409 publication rejection invalidates that
|
|
64
|
+
cached target; it does not authorize a replacement or a blind replay. Conflicting
|
|
65
|
+
same-registration bytes are409; replacement needs a fresh registration ID.
|
|
66
|
+
Relay retired-identity guards share a1000-entry cap and fail closed rather than
|
|
67
|
+
evicting live protection; guards last through original8h activity/24h widget
|
|
68
|
+
expiry. Delayed registration PUTs cannot roll back replacements; identity-exact
|
|
69
|
+
widget DELETEs and stale provider results cannot retire newer registrations.
|
|
70
|
+
Activity DELETE targets the subscription itself. Expiry never renews through
|
|
71
|
+
retry; stale/offline is not success.
|
|
72
|
+
|
|
73
|
+
The relay needs explicit `APNS_WIDGET_TOPIC` for the widget extension plus
|
|
74
|
+
`.push-type.widgets`; Live Activity topic is main `APNS_TOPIC` plus
|
|
75
|
+
`.push-type.liveactivity`. Environments must match configured APNs sending.
|
|
76
|
+
These are relay settings, not CLI configuration keys. Default-off, global
|
|
77
|
+
budgets, kill deadline and existing receipt priority remain unchanged.
|
|
78
|
+
Provider signing is inside the original10s attempt deadline; after signing,
|
|
79
|
+
the durable caller rechecks enabled state, active pair, exact current
|
|
80
|
+
registration/publication and expiry immediately before transport.
|
|
81
|
+
APNs200 is provider admission, never display/delivery proof. Physical Live
|
|
82
|
+
Activity, widget reload/freshness/offline behavior and live cloud/APNs acceptance
|
|
83
|
+
for this delta remain pending. Exact routes/crypto: [[specs/03-api-contract]].
|
|
84
|
+
|
|
31
85
|
## Service resources
|
|
32
86
|
|
|
33
87
|
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.
|
|
@@ -0,0 +1,168 @@
|
|
|
1
|
+
# Native service acceptance — 2026-11-11
|
|
2
|
+
|
|
3
|
+
## Status and boundary
|
|
4
|
+
|
|
5
|
+
The current compiled source controller has exercised real macOS launchd installation,
|
|
6
|
+
start, status, stop and uninstall against the published0.1.1 managed runtime.
|
|
7
|
+
This is not a new npm release, a published-version upgrade, or Linux/Windows native
|
|
8
|
+
service-manager acceptance. Existing released0.1.1 bytes remain unchanged.
|
|
9
|
+
|
|
10
|
+
The acceptance used an unused per-user service label, an isolated HOME and a short,
|
|
11
|
+
owned state directory. Cloud was disabled, pairings were empty and the official
|
|
12
|
+
endpoint was an unreachable loopback address. No official daemon, real-work session,
|
|
13
|
+
model, enrollment or APNs request was used. Installation was refused unless the
|
|
14
|
+
service label and real-home registration file were initially absent.
|
|
15
|
+
|
|
16
|
+
## Discovered shutdown race
|
|
17
|
+
|
|
18
|
+
The real service initially installed and started successfully. Stopping it could
|
|
19
|
+
fail with `CONTROL_CONNECTION_CLOSED`: native bootout had already begun graceful
|
|
20
|
+
supervisor/runtime shutdown while the CLI independently requested control shutdown.
|
|
21
|
+
The socket could close before its ownership records had finished retiring.
|
|
22
|
+
|
|
23
|
+
The correction preserves strict generic control transport errors. Only a managed
|
|
24
|
+
shutdown can cross this specific closure window; it must still wait for supervisor
|
|
25
|
+
retirement and confirm that no runtime remains. An empty response alone is never
|
|
26
|
+
success, malformed responses still fail, and an uncertain stop is not replayed
|
|
27
|
+
against a replacement generation. The workflow now lives with supervisor lifecycle
|
|
28
|
+
ownership instead of being duplicated in CLI command wiring.
|
|
29
|
+
|
|
30
|
+
Independent review exposed a second boundary: a final status probe can return null
|
|
31
|
+
for a departed generation while a replacement owner remains alive. Its regression
|
|
32
|
+
also failed before correction. Shutdown now revalidates the current supervisor and
|
|
33
|
+
runtime lock/PID synchronously after the awaited probe, including lock-only startup.
|
|
34
|
+
The replacement must remain intact and shutdown must fail rather than authorizing
|
|
35
|
+
uninstall. The independent follow-up found no remaining blocker in this scope.
|
|
36
|
+
These checks are snapshots; they cannot prevent an independent start afterward.
|
|
37
|
+
|
|
38
|
+
## Exercised proof
|
|
39
|
+
|
|
40
|
+
- The new owned-socket/supervisor-retirement regression failed before the behavior
|
|
41
|
+
correction. It checks that closure cannot complete shutdown before retirement.
|
|
42
|
+
- 22 focused behavioral checks passed across `managed-shutdown.test.ts`,
|
|
43
|
+
`frontend-lifecycle.test.ts`, `control-response.test.ts` and `cli.test.ts`.
|
|
44
|
+
- `npm run typecheck` and `npm run build` passed.
|
|
45
|
+
- The corrected compiled source controller installed the real launchd registration,
|
|
46
|
+
reached the published runtime's authenticated status endpoint, stopped it and
|
|
47
|
+
removed the registration, plist and isolated state. Final launchd lookup returned
|
|
48
|
+
the platform's explicit missing-service result; no test login service remained.
|
|
49
|
+
- Earlier fixture setup failures were not product acceptance: one used an invalid
|
|
50
|
+
synthetic client identity; another exceeded the Unix-domain socket path limit.
|
|
51
|
+
The final native run used valid configuration and a short isolated path.
|
|
52
|
+
|
|
53
|
+
## Remaining gates at the preceding checkpoint
|
|
54
|
+
|
|
55
|
+
1. A separately authorized, immutable next-version release including current source;
|
|
56
|
+
the published0.1.1 package must not be represented as containing this correction.
|
|
57
|
+
2. Real published-version activation/rollback through an installed native service.
|
|
58
|
+
3. Equivalent native service-manager acceptance on Linux and Windows.
|
|
59
|
+
|
|
60
|
+
Do not install a test registration over an everyday service. A fake HOME isolates
|
|
61
|
+
registration files, not launchd's per-user label namespace. When that label is in
|
|
62
|
+
use, use a separately owned OS environment rather than stopping another instance.
|
|
63
|
+
|
|
64
|
+
## Installed upgrade and rollback continuation — 2026-11-12
|
|
65
|
+
|
|
66
|
+
- A fresh anonymous npm download of immutable0.1.1 matches registry SHA512 and
|
|
67
|
+
published SHA256`358574ca750d27c8a116743cd729d7ab830c41fc17045ddfa46ff808ff3bba3b`.
|
|
68
|
+
The retained native service starts those actual published bootstrap bytes.
|
|
69
|
+
- The actual launchd namespace and real-home registration file are required to
|
|
70
|
+
be absent before installation. The service uses an owned temporary HOME/state,
|
|
71
|
+
no pairs, cloud disabled and an unreachable loopback official endpoint.
|
|
72
|
+
- Initial startup did not reach readiness because the fixture omitted the required
|
|
73
|
+
client-identity prefix. A private direct bootstrap diagnostic reports
|
|
74
|
+
`INVALID_CONFIG`; this is not a product startup defect.
|
|
75
|
+
- Failed-run cleanup exposed a real ownership defect: launchd canonicalizes
|
|
76
|
+
`/tmp` to `/private/tmp`, while the controller compared raw strings and rejected
|
|
77
|
+
its own registration. The exact first service was safely removed through the
|
|
78
|
+
normal controller using its independently established canonical definition.
|
|
79
|
+
- The product correction accepts a parent-path alias only when both leaves are
|
|
80
|
+
ordinary non-symlink files, device/inode match and real paths match. Exact
|
|
81
|
+
unchanged paths retain their fast path. Leaf symlinks, different files and
|
|
82
|
+
foreign registration/marker protections remain rejected. The same rule applies
|
|
83
|
+
to systemd's file path; Windows task matching is unchanged.
|
|
84
|
+
- All10focused service-lifecycle consumers, typecheck and build pass. Independent
|
|
85
|
+
OpenCode review reports no blocker. Distinct hard links/bind mounts remain a
|
|
86
|
+
conservative refusal; no general authority over user-writable services is added.
|
|
87
|
+
- The corrected real launchd run passes in181.29seconds: published0.1.1 bootstrap
|
|
88
|
+
→ current synthetic9000.0.2 candidate → failed compatible9000.0.3 startup →
|
|
89
|
+
recovered9000.0.2. Authenticated status and durable selection agree; bootstrap/
|
|
90
|
+
previous remain0.1.1. Normal stop/uninstall leaves no registration, plist or
|
|
91
|
+
owned successful-run files.
|
|
92
|
+
|
|
93
|
+
This accepts macOS native activation/rollback with real installed package bytes
|
|
94
|
+
and a deliberately failing unpublished fixture. It is not a new immutable public
|
|
95
|
+
release, public-to-public next-version delivery, Linux/Windows native acceptance,
|
|
96
|
+
cloud activation or any real-work-session operation.
|
|
97
|
+
|
|
98
|
+
## Linux user-service and Windows encoding continuation — 2026-11-12
|
|
99
|
+
|
|
100
|
+
Actual Linux acceptance uses the existing Ubuntu26.04 user manager, systemd259
|
|
101
|
+
and pinned Node24.13.0. The real unit reaches active/running/enabled and the
|
|
102
|
+
authenticated control reports the installed version. QA0.1.1 activates synthetic
|
|
103
|
+
9000.0.2, then rejects compatible9000.0.3 before readiness and recovers9000.0.2
|
|
104
|
+
with unchanged bootstrap/previous0.1.1. Normal stop/uninstall leaves
|
|
105
|
+
LoadState=not-found, an empty FragmentPath, absent definition/control and no live
|
|
106
|
+
supervisor/runtime. This is actual user-systemd, not every Linux distribution.
|
|
107
|
+
|
|
108
|
+
The preceding Windows QA implementation identified missing BOM in a UTF-16LE
|
|
109
|
+
task import file. Native COM syntax-only validation of a decoded string did not
|
|
110
|
+
test the file bytes consumed by schtasks. That QA writer emitted FF FE; its
|
|
111
|
+
current reader was corrected to consume one leading U+FEFF while retaining
|
|
112
|
+
ownership/XML checks. This was current/current QA evidence, not retained-version
|
|
113
|
+
compatibility; the later correction below supersedes the persistent-BOM design.
|
|
114
|
+
|
|
115
|
+
That18consumer run covered writer/current-reader consumption, legacy unmarked
|
|
116
|
+
UTF-16 ownership inspection, repeated-BOM, wrong-encoding and foreign-marker
|
|
117
|
+
rejection. Typecheck and build also passed.
|
|
118
|
+
|
|
119
|
+
The final unwrapped native Windows Task Scheduler run passes in168.23seconds.
|
|
120
|
+
It installs/starts QA0.1.1, authenticates status, activates synthetic9000.0.2,
|
|
121
|
+
rejects9000.0.3 before readiness and recovers9000.0.2, then normally stops and
|
|
122
|
+
uninstalls. Independent task/definition/control checks are absent and no live
|
|
123
|
+
supervisor/runtime remains. The exercised QA archive SHA256 is
|
|
124
|
+
`8b5c55ac04edfaf5c93eb7b1708ad07be9eec5b0d288b04ec0b5dbbd81b4df82`.
|
|
125
|
+
|
|
126
|
+
No console-token impersonation, account/policy change, real daemon/cloud
|
|
127
|
+
operation or public release is used. A private fixture's elevated-owner ACL
|
|
128
|
+
mismatch was recorded separately rather than misrepresented as a product login
|
|
129
|
+
requirement. Failed and diagnostic task registrations were normally removed.
|
|
130
|
+
An independent provider review could not run because its read tools were
|
|
131
|
+
refused; no review approval is claimed.
|
|
132
|
+
|
|
133
|
+
|
|
134
|
+
## Retained public reader correction — 2026-11-12
|
|
135
|
+
|
|
136
|
+
Fresh-context specification review found that unchanged public0.1.1 starts its
|
|
137
|
+
resource reader before runtime readiness and cannot consume persistent BOM-prefixed
|
|
138
|
+
ownership XML. A matching compatibility tuple and synthetic current/current
|
|
139
|
+
native pass did not establish retained-reader compatibility.
|
|
140
|
+
|
|
141
|
+
Persistent `moremote-cli-task.xml` is now BOM-free UTF-16LE. Native `/Create`
|
|
142
|
+
receives a separate BOM-prefixed XML file in an owned private temporary directory
|
|
143
|
+
outside shared state. `finally` removes that copy before `/Run`; registration or
|
|
144
|
+
cleanup failure cannot start the runtime. No schema bump or migration is needed.
|
|
145
|
+
|
|
146
|
+
Two new deterministic regressions first fail, then the20focused lifecycle/resource
|
|
147
|
+
consumers, typecheck and build pass. The frozen public reader is unmodified,
|
|
148
|
+
SHA256`1ee80f6bdab819e15da817038cecf46133b07d1a157663893a64112a2fdca13b`;
|
|
149
|
+
an independent anonymous npm download confirms those module bytes. Fresh-context
|
|
150
|
+
Stage A and Stage B re-review close the blocker, explicitly using the weaker
|
|
151
|
+
same-provider fallback after the unavailable cross-provider attempt.
|
|
152
|
+
|
|
153
|
+
The actual Windows journey starts unchanged npm0.1.1 bootstrap bytes, activates
|
|
154
|
+
the current synthetic9000.0.2, fails9000.0.3 before readiness, recovers9000.0.2
|
|
155
|
+
and normally stops/uninstalls. The native interval is183.86seconds; the enclosing
|
|
156
|
+
fleet job takes202.70seconds. Independent final observations show no task,
|
|
157
|
+
definition, control endpoint or live supervisor/runtime; successful-run runtime
|
|
158
|
+
files are removed. The intentionally unused loopback official target yields
|
|
159
|
+
degraded connection status while authenticated runtime/version checks succeed.
|
|
160
|
+
|
|
161
|
+
Public0.1.1 archive SHA256 is
|
|
162
|
+
`358574ca750d27c8a116743cd729d7ab830c41fc17045ddfa46ff808ff3bba3b`;
|
|
163
|
+
unpublished exercised candidate SHA256 is
|
|
164
|
+
`6dca555348e87dd395aa0564d97aa1499581fbeadc98b78dbb1c9c3c179ff861`.
|
|
165
|
+
No real daemon/cloud/model operation, account/security-policy change, npm
|
|
166
|
+
publication or everyday installed service occurs. Synthetic candidates are
|
|
167
|
+
still not a new immutable public release or public-to-public delivery.
|
|
168
|
+
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# 03 — Relay HTTP API, version 1
|
|
2
2
|
|
|
3
|
-
**Status:**
|
|
3
|
+
**Status:** living relay-v1 contract. Activity/widget additions below describe unreleased local integration, not published CLI0.1.1 or native/live-cloud acceptance.
|
|
4
4
|
|
|
5
5
|
## Common rules
|
|
6
6
|
|
|
@@ -103,7 +103,9 @@ without contacting cloud.
|
|
|
103
103
|
|
|
104
104
|
### PUT /pairs/{pairId}/state; GET /pairs/{pairId}/state
|
|
105
105
|
|
|
106
|
-
Host writes, phone reads.
|
|
106
|
+
Host writes, phone reads. PUT accepts strict `{envelope}` or additive
|
|
107
|
+
`{envelope,widgetFingerprint}`; GET returns the envelope only, as specified below.
|
|
108
|
+
Envelope channel is `state`.
|
|
107
109
|
Only the latest nonexpired snapshot keeps ciphertext, monotonic by issuedAt then
|
|
108
110
|
immutable ID. Each state ID/digest remains a conflict guard through its own
|
|
109
111
|
original envelope expiry, including after supersession; no additional24hour
|
|
@@ -395,3 +397,121 @@ may contain both original128KiB-bounded payload and a separate8KiB receipt; a
|
|
|
395
397
|
host pairing response may contain two bounded proofs. A128KiB response reader
|
|
396
398
|
would permanently reject valid work and is nonconforming. This larger response
|
|
397
399
|
budget never raises the128KiB request or64KiB decrypted command-content limits.
|
|
400
|
+
|
|
401
|
+
## Opt-in task activities and widget reloads
|
|
402
|
+
|
|
403
|
+
These additive routes do not change command, receipt, alert, pairing, service,
|
|
404
|
+
or managed-update identities. Cloud remains disabled by default. Every route
|
|
405
|
+
uses the existing pair bearer; subscription IDs and registration IDs are
|
|
406
|
+
lowercase canonical UUIDs. No pair-level activity-device registration exists.
|
|
407
|
+
|
|
408
|
+
| Route (under `/v1/pairs/{pairId}`) | Role | Exact JSON body | Admission |
|
|
409
|
+
| --- | --- | --- | --- |
|
|
410
|
+
| `PUT /activities/{subscriptionId}` | phone | `{registrationId,token,environment,topic,interest}` | normal |
|
|
411
|
+
| `DELETE /activities/{subscriptionId}` | phone | none | recovery |
|
|
412
|
+
| `GET /activities` | host | none | normal |
|
|
413
|
+
| `PUT /activities/{subscriptionId}/state` | host | `{registrationId,topic,event:"update",envelope}` | normal |
|
|
414
|
+
| `PUT /activities/{subscriptionId}/end` | host | `{registrationId,topic,event:"end",envelope}` | recovery |
|
|
415
|
+
| `PUT /widget-device` | phone | `{registrationId,token,environment}` | normal |
|
|
416
|
+
| `DELETE /widget-device/{registrationId}` | phone | none | recovery |
|
|
417
|
+
|
|
418
|
+
Tokens are even-length hex,1–256 bytes, normalized lowercase. Environment is
|
|
419
|
+
`sandbox|production`; provider configuration must match. The activity `topic`
|
|
420
|
+
is the existing pair-key HMAC `presenceTopic(rootKey,pairId,agentId)` (32 bytes,
|
|
421
|
+
base64url), not an APNs topic or plaintext agent identity. At most8 live
|
|
422
|
+
subscriptions are admitted per pair. GET returns
|
|
423
|
+
`{ok:true,subscriptions:[{id,registrationId,topic,interest,expiresAt}]}`.
|
|
424
|
+
PUT registration returns the same single row as `{ok:true,subscription:...}`.
|
|
425
|
+
Registration replacement uses a fresh registrationId; different bytes under
|
|
426
|
+
the same registrationId conflict. Native renewal must preserve the ActivityKit
|
|
427
|
+
activity's original8-hour ceiling. DELETE removes queued state immediately.
|
|
428
|
+
Retired subscription/registration IDs share a bounded1000-entry token-free guard
|
|
429
|
+
pool with widget registrations. Delayed registration PUTs cannot resurrect or
|
|
430
|
+
roll back retired identities. Widget DELETE is registration-exact; activity DELETE targets the subscription.
|
|
431
|
+
Activity guards retain the original8h ceiling and widget guards the original24h
|
|
432
|
+
expiry, without retry extension. Unknown DELETEs also reserve bounded guards;
|
|
433
|
+
capacity exhaustion fails closed, never evicts live protection.
|
|
434
|
+
|
|
435
|
+
The encrypted `interest` uses additive channel `activityInterest`, envelope.id
|
|
436
|
+
equal to subscriptionId, lifetime at most8h. Exact plaintext:
|
|
437
|
+
`{version:1,subscriptionId,daemonServerId,agentId}`. The companion authenticates
|
|
438
|
+
the envelope, pinned daemon, exact subscription and derived topic before any
|
|
439
|
+
read-only task lookup. This plaintext cannot authorize commands. No timeline
|
|
440
|
+
or chat download is required. Existing snapshot cadence (at least30s) admits
|
|
441
|
+
one bounded interest pass, at most8 exact fallback reads outside the recent list.
|
|
442
|
+
The owned optional lane has a2s deadline,250ms SDK reads and request cancellation.
|
|
443
|
+
Commands/control never await it; drain aborts/joins before SDK/journal close. Missing tasks never imply finish.
|
|
444
|
+
|
|
445
|
+
Activity state uses additive channel `activityState`, fresh envelope UUID and
|
|
446
|
+
at most600s lifetime, capped by subscription expiry. Exact plaintext:
|
|
447
|
+
`{version:1,subscriptionId,daemonServerId,agentId,title,hostName,phase,startedAt,measuredAt,expiresAt,requiresAttention,isTerminal}`.
|
|
448
|
+
Title/hostName are limited to160/80 characters. Phase is
|
|
449
|
+
`running|waiting|finished|error|idle`; permission attention maps to waiting;
|
|
450
|
+
official closed/error or current terminal attention maps to end. A running
|
|
451
|
+
turn supersedes an old terminal attention flag. startedAt is nullable, from
|
|
452
|
+
official activeTurn.startedAt or lastUserMessageAt, never a measurement
|
|
453
|
+
substitute. measuredAt/expiresAt exactly match envelope headers in milliseconds.
|
|
454
|
+
Existing encrypted snapshots also include optional lastUserMessageAt,
|
|
455
|
+
activeTurnStartedAt and bounded cwd per task. Encrypted usage adds genuine
|
|
456
|
+
provider displayName and window/balance label (at most128 characters each),
|
|
457
|
+
preserving absent values as unavailable. No full chats, invented labels or
|
|
458
|
+
synthetic percentages are added.
|
|
459
|
+
|
|
460
|
+
HKDF salt, AES-GCM nonce/tag framing, metadata AAD and existing channels remain
|
|
461
|
+
byte-compatible. Only the new channel name changes HKDF info. Activity state
|
|
462
|
+
serialized envelope is at most3000 UTF-8 bytes. Native ContentState has default
|
|
463
|
+
Codable field `payload`, a canonical JSON string of that envelope (key order
|
|
464
|
+
version,pairId,id,channel,issuedAt,expiresAt,nonce,ciphertext).
|
|
465
|
+
Updates derive directly from real semantic task transitions, independently of
|
|
466
|
+
alert admission/presence suppression. Unchanged measurements normally do not push.
|
|
467
|
+
Acknowledged nonterminal state renews from fresh samples every8minutes (120s before600s expiry).
|
|
468
|
+
Unknown admissions retain identical ciphertext until expiry; semantic changes can supersede progress. Disconnected state expires.
|
|
469
|
+
|
|
470
|
+
Live authenticated interests are cached against the current pair key/daemon. Terminal work precedes optional normal discovery, once per fresh
|
|
471
|
+
snapshot, without GET/state admission; authenticated404/409 invalidates its cache.
|
|
472
|
+
Only exact429 `daily_work_limit`, `x-moremote-budget:normal` and consistent future
|
|
473
|
+
`x-moremote-reset`/Retry-After pauses normal work alone. Missing/malformed hints,
|
|
474
|
+
outages, disable or recovery exhaustion preserve origin-wide pause/cycle fences.
|
|
475
|
+
Recovery still requires server admission; hints never grant operation authority.
|
|
476
|
+
|
|
477
|
+
APNs uses `apns-push-type:liveactivity`, configured main topic plus
|
|
478
|
+
`.push-type.liveactivity`, priority5 update/10 end, collapse-id subscriptionId,
|
|
479
|
+
apns-id envelope.id, expiration floor(expiresAt/1000). Body is
|
|
480
|
+
`{aps:{timestamp,event,"content-state":{payload},"stale-date"}}`; all APNs dates
|
|
481
|
+
are epoch seconds. End additionally sets dismissal-date. There is no apns-event
|
|
482
|
+
header. A512-byte static-attributes reserve and the complete4096-byte provider
|
|
483
|
+
payload limit both apply. End and invalid-token retirement compare the exact
|
|
484
|
+
current registration identity; stale provider failures never remove replacement
|
|
485
|
+
tokens. Provider admission is not proof of rendering.
|
|
486
|
+
|
|
487
|
+
Existing `PUT /state` accepts strict legacy `{envelope}` or additive
|
|
488
|
+
`{envelope,widgetFingerprint}`. GET state remains unchanged. The new fingerprint
|
|
489
|
+
is a pair-keyed HMAC using the presence domain over JSON
|
|
490
|
+
`["widgetSnapshot",meaningfulProjection]`. Projection includes bounded sorted
|
|
491
|
+
task identity/title/status/attention/latest turn/project plus usage values;
|
|
492
|
+
measurement and usage fetchedAt clocks are excluded. Only a changed opaque
|
|
493
|
+
fingerprint for the current widget registration queues a coalesced push.
|
|
494
|
+
Legacy envelope-only publications do not cause widget pushes.
|
|
495
|
+
|
|
496
|
+
Widget registration expires after24h and requires foreground/token renewal
|
|
497
|
+
(native renewal around12h uses a fresh registration ID).
|
|
498
|
+
Native uses the WidgetKit token, not an alert or activity token. Explicit
|
|
499
|
+
`APNS_WIDGET_TOPIC` is the widget extension bundle ID plus `.push-type.widgets`;
|
|
500
|
+
it is never derived from the main app topic. APNs uses push-type widgets,
|
|
501
|
+
priority5 and `{aps:{"content-changed":true}}`, no private identifiers.
|
|
502
|
+
WidgetKit automatically reloads timelines opportunistically on receipt;
|
|
503
|
+
WidgetPushHandler observes token/configuration updates. Timeline providers use
|
|
504
|
+
the existing sealed snapshot and its expiry; reload is not realtime delivery.
|
|
505
|
+
See Apple's [WidgetKit push documentation](https://developer.apple.com/documentation/widgetkit/updating-widgets-with-widgetkit-push-notifications).
|
|
506
|
+
|
|
507
|
+
Activity/widget work shares bounded provider attempts and background batches
|
|
508
|
+
with alerts; no recursive requests, unbounded retries, recovery-budget borrowing
|
|
509
|
+
for progress or changes to endpoint retirement/receipt/updater lifecycle.
|
|
510
|
+
|
|
511
|
+
Every APNs sender requires a synchronous `BeforeSend = () => boolean` fence
|
|
512
|
+
after asynchronous JWT signing and immediately before transport. The durable
|
|
513
|
+
caller rechecks service enabled, active pair, exact current registration and
|
|
514
|
+
publication, and expiry. Signing shares the original10s attempt deadline;
|
|
515
|
+
late signing cannot start transport. Global budgets and kill deadline are unchanged.
|
|
516
|
+
Physical Live Activity/widget behavior and live APNs/cloud delivery for this
|
|
517
|
+
delta remain pending; provider200 never establishes device delivery.
|
|
@@ -42,9 +42,17 @@ After old exit, candidate readiness requires journal creation and acquired runti
|
|
|
42
42
|
|
|
43
43
|
Opt-out during drain allows the old cycle to settle, then resumes old active without starting candidate. Opt-out during candidate startup drains it before resuming old active. Explicit stop signals only the owned service/runtime, writes a separate supervisor stop request, and waits for supervisor exit before managed deletion. Stop does not cause an internal respawn. A hung in-flight operation cannot be safely force-killed by an update: activation waits, status retains activating, and explicit operator stop remains separate. A staged package alone is never reported as active.
|
|
44
44
|
|
|
45
|
+
On Windows, the persistent ownership XML remains BOM-free UTF-16LE so unchanged
|
|
46
|
+
retained0.1.1 readers can validate shared state during startup and rollback.
|
|
47
|
+
Task Scheduler's file import instead receives an owned private transient copy
|
|
48
|
+
with the required UTF-16LE BOM, outside shared state. Remove that copy on every
|
|
49
|
+
normal success/failure path and before `/Run`; failed cleanup must not start the
|
|
50
|
+
runtime. Native registration acceptance must include unchanged public bootstrap
|
|
51
|
+
bytes, not only current code relabeled as an older QA version.
|
|
52
|
+
|
|
45
53
|
## Evidence entrypoints
|
|
46
54
|
|
|
47
|
-
`npm run check` exercises ordinary regression tests and compiles; `npm run smoke:upgrade` then packs
|
|
55
|
+
`npm run check` exercises ordinary regression tests and compiles; `npm run smoke:upgrade` then packs three synthetic versions of the actual compiled package and installs them through real npm into isolated private prefixes. It starts the production retained service entry without registering an OS service, confirms9000.0.1→9000.0.2, exercises the retained frontend through a path alias, then queues compatible9000.0.3 whose disposable runtime exits before readiness. The supervisor must return to9000.0.2, retain bootstrap/previous, record the failed candidate and clear pending/activating before a clean stop. Only the disposable failed package bytes change. It contacts npm plus an intentionally unavailable localhost endpoint, never everyday official data or cloud. This is explicit acceptance, not an install hook. CI includes this smoke on macOS/Linux/Windows; observed results belong in STATE, not this specification.
|
|
48
56
|
|
|
49
57
|
The packaged smoke explicitly invokes the old frontend through a parent-directory symlink/junction and requires one selected-version response. Every network/subprocess/control/wait stage has a bounded deadline and a named checkpoint. Teardown retains handles to its own spawned processes, signals only their dedicated POSIX process groups or Windows PID subtrees, and awaits exit. Failure keeps the temporary root plus the last stage/selection; it never deletes an unexplained failed fixture or signals a PID discovered from an arbitrary state record.
|
|
50
58
|
|