@moxuli/moremote 0.1.6 → 0.1.8
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 +34 -14
- package/dist/activity-capabilities.d.ts +21 -0
- package/dist/activity-capabilities.js +107 -0
- package/dist/cloud-client.d.ts +10 -1
- package/dist/cloud-client.js +43 -3
- package/dist/enrollment-files.d.ts +1 -0
- package/dist/enrollment-files.js +7 -0
- package/dist/event-publication.d.ts +6 -0
- package/dist/event-publication.js +48 -0
- package/dist/journal.d.ts +3 -0
- package/dist/journal.js +7 -1
- package/dist/limits.d.ts +1 -0
- package/dist/limits.js +1 -1
- package/dist/live-activity-titles.d.ts +20 -0
- package/dist/live-activity-titles.js +34 -0
- package/dist/live-activity.d.ts +64 -0
- package/dist/live-activity.js +143 -0
- package/dist/live-directory.d.ts +19 -0
- package/dist/live-directory.js +87 -0
- package/dist/live-workspaces.d.ts +26 -0
- package/dist/live-workspaces.js +217 -0
- package/dist/notification-preview.d.ts +29 -0
- package/dist/notification-preview.js +75 -0
- package/dist/official-client.d.ts +74 -1
- package/dist/official-client.js +63 -12
- package/dist/resources.js +20 -2
- package/dist/runtime.d.ts +2 -1
- package/dist/runtime.js +14 -13
- package/docs/STATE.md +110 -515
- package/docs/configuration.md +33 -0
- package/docs/journal/2026-11-14-state-before-0.1.6-part-1.md +400 -0
- package/docs/journal/2026-11-14-state-before-0.1.6-part-2.md +115 -0
- package/docs/journal/2026-11-15-custom-origin-release.md +35 -0
- package/docs/journal/2026-11-15-informative-notifications-activity-release.md +31 -0
- package/docs/journal/2026-11-15-informative-notifications-and-settings.md +41 -0
- package/docs/journal/2026-11-15-live-activity-title-provenance.md +88 -0
- package/docs/journal/2026-11-15-remote-activity-local-acceptance.md +85 -0
- package/docs/journal/2026-11-15-title-provenance-release.md +86 -0
- package/docs/plans/2026-11-10-notification-delivery.md +8 -0
- package/docs/plans/2026-11-15-remote-activity-and-shared-events.md +99 -0
- package/docs/specs/01-architecture.md +15 -2
- package/docs/specs/02-encrypted-delivery.md +44 -0
- package/docs/specs/03-api-contract.md +54 -6
- package/docs/specs/04-control-and-receipt-lifecycle.md +5 -0
- package/docs/specs/05-endpoint-and-lifecycle.md +19 -0
- package/package.json +2 -2
- package/vectors/remote-activity-v2.json +30 -0
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
# Informative encrypted notifications — local, unreleased
|
|
2
|
+
|
|
3
|
+
## Root cause and correction
|
|
4
|
+
|
|
5
|
+
Released alerts contain generic provider copy; the app had no notification service
|
|
6
|
+
extension. Renaming that fallback cannot identify a private conversation without
|
|
7
|
+
endpoint display support. Attention now optionally carries separately encrypted
|
|
8
|
+
bounded session/computer/current-content presentation, with unchanged legacy
|
|
9
|
+
route plaintext, exact identity, independent nonce, expiry and durable retries.
|
|
10
|
+
Only current assistant prose or exact current questions/approvals/errors enter
|
|
11
|
+
presentation. Generated UI source, reasoning and tool output are excluded.
|
|
12
|
+
|
|
13
|
+
The official SDK may optionally read one30-entry canonical tail per completion,
|
|
14
|
+
with five-second timeout and two concurrent tails. Live and snapshot/reconnect
|
|
15
|
+
recovery use the same current-turn/terminal identity fence; recovery does not
|
|
16
|
+
block control/directory polling. Existing successful authenticated relay responses
|
|
17
|
+
passively advertise support; old relays receive legacy events without another
|
|
18
|
+
request. Once journaled, the original exact bytes remain immutable.
|
|
19
|
+
|
|
20
|
+
## Evidence and review
|
|
21
|
+
|
|
22
|
+
The added presentation tests initially failed against the absent module. The real
|
|
23
|
+
SDK recovery-body regression then failed against the empty snapshot preview; its
|
|
24
|
+
final legacy/owned wire tests pass2/2, including independently decrypted durable
|
|
25
|
+
preview and unchanged legacy route. Full frozen `npm run check` passes types,
|
|
26
|
+
243 tests with zero failures and compilation. The first full run had one timed
|
|
27
|
+
quota fixture failure under concurrent load; the exact isolated test passed, and
|
|
28
|
+
this fresh complete243-test run is the accepted final gate. No assertion or
|
|
29
|
+
production timeout was weakened.
|
|
30
|
+
|
|
31
|
+
Independent read-only review found the recovery omission and an app workspace
|
|
32
|
+
name precedence issue. Both are fixed and independently re-reviewed. Three
|
|
33
|
+
external-provider attempts produced no usable review (account hold, network reset,
|
|
34
|
+
timeout); the completed independent-context review is not a multi-vendor approval.
|
|
35
|
+
|
|
36
|
+
## Boundary
|
|
37
|
+
|
|
38
|
+
Source remains on `fix/notification-content-1115`, unreleased after0.1.6. No
|
|
39
|
+
package/tag publication, real everyday service installation or real host/session
|
|
40
|
+
mutation occurred. Cloud/APNs transport and physical extension display are
|
|
41
|
+
separate acceptance gates; tests use synthetic wire/keys/temp journals only.
|
|
@@ -0,0 +1,88 @@
|
|
|
1
|
+
# Live Activity title provenance — local, unreleased
|
|
2
|
+
|
|
3
|
+
## Root cause and correction
|
|
4
|
+
|
|
5
|
+
The notification path already resolves App-authorized workspace names, while the
|
|
6
|
+
companion activity path projected the raw provider agent title. Blindly replacing
|
|
7
|
+
that encrypted title with App catalog text would let stale cached names replace
|
|
8
|
+
fresh remote renames. Inferring workspace authority from a partial recent agent
|
|
9
|
+
page would also regress imported or shared-root conversations.
|
|
10
|
+
|
|
11
|
+
Encrypted activity interests may now carry at most32 exact source hints whose
|
|
12
|
+
complete UTF-8 JSON array is at most4000bytes. They contain only agent/workspace
|
|
13
|
+
IDs and conversation/workspace provenance. Matching workspace hints authorize
|
|
14
|
+
fresh official workspace metadata; conversation/mismatched/missing hints retain
|
|
15
|
+
fresh agent text. Visible independent roots can disprove workspace authority,
|
|
16
|
+
never manufacture it. Managed children do not become roots.
|
|
17
|
+
|
|
18
|
+
An active activity owns a bounded100-workspace read subscription. Missing targets
|
|
19
|
+
acquire at most32 exact reads with exact-ID response checks and a132-row shared
|
|
20
|
+
cache. Owned-subscription hosts use separate target owners. Legacy hosts use
|
|
21
|
+
non-subscribing seeds, preserving their connection-wide broad subscription slot.
|
|
22
|
+
Stop releases owners and fences late read results. No Worker poll is added.
|
|
23
|
+
|
|
24
|
+
Unknown metadata delays activity publication independently of attention delivery.
|
|
25
|
+
Read errors and page omissions retain confirmed names; a full official entry
|
|
26
|
+
without a title normalizes to null, while a removed record stays unknown. Shared
|
|
27
|
+
rows compare generation/sequence across observers; retired generations and
|
|
28
|
+
released ownership cannot restore older names. Unversioned owned exact reads
|
|
29
|
+
conservatively outrank broad reads, and legacy seeds cannot overwrite newer
|
|
30
|
+
stream observations. Page membership skips a targeted read only while known
|
|
31
|
+
metadata remains cached. Original unacknowledged publications retain exact bytes.
|
|
32
|
+
|
|
33
|
+
## Rolling compatibility
|
|
34
|
+
|
|
35
|
+
The legacy enrollment descriptor is exact-field validated by older App versions;
|
|
36
|
+
the legacy discovery directory also rejects unknown resources. Neither changes.
|
|
37
|
+
Capability support is published separately at
|
|
38
|
+
`<home>/.moremote-cli-activity/<sha256(UTF8 daemonServerId)>/capabilities.json`.
|
|
39
|
+
The exact version1 document contains daemon/instance identity, descriptor lease
|
|
40
|
+
clocks and `titleHints:1`, with no title text or keys. Its independent marked
|
|
41
|
+
private tree follows existing enrollment lock ownership and matching-instance
|
|
42
|
+
cleanup. Old-runtime rollback ignores that directory; old capability files fail
|
|
43
|
+
fresh descriptor instance/expiry checks. Config and cloud HTTP shapes are unchanged.
|
|
44
|
+
|
|
45
|
+
## Verification and review
|
|
46
|
+
|
|
47
|
+
New capability/strict-interest tests first failed with missing files/rejected
|
|
48
|
+
hints. The initial owner test then failed without workspace observation. Later
|
|
49
|
+
regressions reproduced raw-title publication before metadata readiness, loss of
|
|
50
|
+
confirmed names during recovery, legacy seed races, cross-owner sequence rollback,
|
|
51
|
+
unversioned observer precedence, missing-title confusion and cache-eviction stalls.
|
|
52
|
+
Each behavioral correction was preceded by its failing regression.
|
|
53
|
+
|
|
54
|
+
The initial complete default-concurrency run reported258tests,256passes and2
|
|
55
|
+
runtime-deadline failures (`REPAIRED_RUNTIME_COULD_NOT_ACQUIRE` and
|
|
56
|
+
`RECEIPT_OR_STATE_BLOCKED_COMMANDS`). Deadlines and production timeouts were not
|
|
57
|
+
weakened. Intermediate complete concurrency4 runs passed265/265and267/267.
|
|
58
|
+
After the final cache-membership fix, the frozen complete check passes types,
|
|
59
|
+
267tests with zero failures/skips, and compilation. Final focused regressions
|
|
60
|
+
pass24/24. The accepted command is the complete check sequence with explicit
|
|
61
|
+
test concurrency4:
|
|
62
|
+
|
|
63
|
+
```sh
|
|
64
|
+
npm run typecheck
|
|
65
|
+
node --import tsx --test --test-concurrency=4 tests/*.test.ts
|
|
66
|
+
npm run build
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
Both legacy and owned real-SDK wire fixtures cover workspace bootstrap arriving
|
|
70
|
+
after agents, current rename, exact target metadata, non-subscribing legacy wire
|
|
71
|
+
behavior and late response after release. The independent notification consumer
|
|
72
|
+
proves unknown title metadata does not block its attention outbox. Existing
|
|
73
|
+
immutable activity retry and real runtime acquisition/receipt tests remain green.
|
|
74
|
+
|
|
75
|
+
Independent-context review found the cross-subscription ordering blocker, which
|
|
76
|
+
now has an explicit RED/GREEN regression. Parent review additionally identified
|
|
77
|
+
unknown metadata, full-entry title semantics and cache membership edges; those
|
|
78
|
+
are covered. External-provider attempts yielded no usable review because of
|
|
79
|
+
account/transport availability; no cross-vendor approval is claimed. Actual final
|
|
80
|
+
logs and clearly labeled early output excerpts are in this run's local CLI
|
|
81
|
+
acceptance bundle. Source remained uncommitted at handoff.
|
|
82
|
+
|
|
83
|
+
## Boundary
|
|
84
|
+
|
|
85
|
+
Only CLI code/tests/contracts changed. There was no package/tag publication,
|
|
86
|
+
deployment, service installation, dependency upgrade or real provider-session
|
|
87
|
+
mutation. Native/Cloud changes and physical APNs display remain independently
|
|
88
|
+
owned acceptance scopes.
|
|
@@ -0,0 +1,85 @@
|
|
|
1
|
+
# Remote Live Activity delivery — local acceptance
|
|
2
|
+
|
|
3
|
+
Status: local implementation, unreleased. Existing deployed versions are unchanged.
|
|
4
|
+
The owner explicitly authorized sharing Cloudflare notifications with Live Activity
|
|
5
|
+
updates; widgets and ordinary app/extension reads remain direct Paseo clients.
|
|
6
|
+
|
|
7
|
+
## Implemented behavior
|
|
8
|
+
|
|
9
|
+
Native rendering cannot network. The phone starts its normal aggregate activity,
|
|
10
|
+
observes ActivityKit token rotations, and registers that one activity across active
|
|
11
|
+
paired computers. Each source receives only a dedicated display key, encrypted
|
|
12
|
+
under its own pairing root. The local attribute seed never enters the service.
|
|
13
|
+
The CLI acquires a separate owned official read interest only when needed. It
|
|
14
|
+
publishes semantic candidates and notification attention in one bounded event
|
|
15
|
+
POST, retaining independent durable acknowledgements and immutable unknown retries.
|
|
16
|
+
Unchanged state creates no extra Worker request; display freshness renews at most
|
|
17
|
+
once per eight minutes. A definitively closed generation stops CLI retries.
|
|
18
|
+
|
|
19
|
+
An existing PAIRS namespace object arbitrates the phone-wide fair queue and last
|
|
20
|
+
opened fallback. A source-specific final sender fences APNs against current pair,
|
|
21
|
+
member, token and deadline authority. An unknown end cannot resume updates. Remote
|
|
22
|
+
APNs can update/end the existing activity while the app is suspended; a renderer
|
|
23
|
+
verifies ciphertext, subscription/generation, host/daemon/lifetime and route even
|
|
24
|
+
without a cached conversation. Foreground content has a bounded local lease.
|
|
25
|
+
Registration success alone never grants remote background writer ownership.
|
|
26
|
+
|
|
27
|
+
Token rotation reuses immutable interest. Cleanup compares registration AND client
|
|
28
|
+
revision, including compensating cleanup after a late PUT. A cold token wait is
|
|
29
|
+
not a disable; replacement snapshots are unknown, not empty/finished. Local
|
|
30
|
+
revocation writes throw before pairing-vault changes can commit. Explicit disable
|
|
31
|
+
also ends a restored native handle before its first directory publication.
|
|
32
|
+
A build with no signed push environment retains its original local activity type.
|
|
33
|
+
|
|
34
|
+
Only events and their private publish hop accept512KiB; other requests remain
|
|
35
|
+
128KiB. Sources are bounded to100candidates,16members/512aggregate candidates,
|
|
36
|
+
8KiB interests,2700byte individual ciphertexts and1,900,000byte aggregate storage. Native
|
|
37
|
+
APNs output is checked after final serialization against4KiB. A full100-target
|
|
38
|
+
long-Unicode fixture verifies the batch and does not widen command limits.
|
|
39
|
+
|
|
40
|
+
## Verification
|
|
41
|
+
|
|
42
|
+
- CLI complete types/tests/build:249passed, zero failures before the final clock
|
|
43
|
+
tolerance correction; final affected7tests, fresh types/build also pass. An
|
|
44
|
+
actual RED/GREEN case aligns phone-created time with the envelope120second
|
|
45
|
+
tolerance, including future-clock refusal. Real pinned official
|
|
46
|
+
SDK legacy and owned wire flows both pass, without notification-interest widening.
|
|
47
|
+
- Cloud complete types/tests/Worker+Pages dry-run:202passed, zero failures. Actual
|
|
48
|
+
SQLite objects cover restart, two sources, shared acknowledgements, source revoke,
|
|
49
|
+
late registration, clock skew, token rotation, bounded body parsing, uncertain
|
|
50
|
+
APNs timestamps and irreversible end. Provider transport is synthetic, not Apple.
|
|
51
|
+
- Kit complete:554tests,5explicit environment skips, zero failures.
|
|
52
|
+
- Final hosted native regression:83passed, zero failures.
|
|
53
|
+
- Actual SpringBoard native journeys:2passed, zero failures; pending question
|
|
54
|
+
outranks its running turn, and isolated compact glyph pixels keep moving after
|
|
55
|
+
Home. Source-only DEBUG fixture reconnect ownership and Sendable capture were
|
|
56
|
+
corrected without changing product admission checks.
|
|
57
|
+
- Final unsigned Release build succeeds. The main app and all3extensions are
|
|
58
|
+
present; ActivityKit support and13loading fonts/30,040bytes independently verify.
|
|
59
|
+
- The real Node publisher's encrypted vector is decrypted by the bundled native
|
|
60
|
+
renderer with an empty conversation catalog; changed lifetime, topic tampering,
|
|
61
|
+
revoked grant and expiry fail closed.
|
|
62
|
+
- Read-only important-code review found and closed lifecycle/race/capacity defects;
|
|
63
|
+
its final source review reports no remaining definite P1/P2. No external review
|
|
64
|
+
service, real provider notification, device or Apple account was used.
|
|
65
|
+
|
|
66
|
+
Initial native UI attempts are retained: a push-unconfigured simulator exposed the
|
|
67
|
+
need to keep local creation; a real visible compact glyph exposed a test-only
|
|
68
|
+
minimum-width assumption (146.7pt versus177.3pt). The crop now follows actual native
|
|
69
|
+
container geometry and still requires isolated moving glyph pixels. Initial
|
|
70
|
+
unknown numeric system errors and directory-start timeouts are not erased. The
|
|
71
|
+
DEBUG reconnect factory now owns fresh streams for each foreground attempt.
|
|
72
|
+
|
|
73
|
+
Evidence is outside the repository at
|
|
74
|
+
`/Users/yangxiaoming/Documents/MoRemoteAcceptance/notification-content-20261115-eoaqf6yx`:
|
|
75
|
+
`remote-activity-cli-accepted-check.log`, `remote-clock-green.log`, `remote-activity-cloud-check.log`,
|
|
76
|
+
`remote-activity-kit-check.log`, native xcresults and the source manifest.
|
|
77
|
+
|
|
78
|
+
## Explicit remaining release boundary
|
|
79
|
+
|
|
80
|
+
No push-to-start is implemented: a new activity after termination/expiry still
|
|
81
|
+
needs the foreground app. Actual device APNs delivery and OS throttling behavior
|
|
82
|
+
have not been accepted. Complete rollout requires the corresponding App, CLI and
|
|
83
|
+
Worker versions; no new deployment, package publication or TestFlight delivery
|
|
84
|
+
was performed. Native APNs has separate alert/activity tokens/topics, so a shared
|
|
85
|
+
public event POST does not mean one Apple request or a claimed billing percentage.
|
|
@@ -0,0 +1,86 @@
|
|
|
1
|
+
# Title provenance release0.1.8
|
|
2
|
+
|
|
3
|
+
## Authorized scope and preflight
|
|
4
|
+
|
|
5
|
+
The owner explicitly authorized0.1.8publication alongside the related App update.
|
|
6
|
+
The reviewed title-provenance implementation is unchanged from the accepted
|
|
7
|
+
source snapshot. Initial preparation changes package/lock root versions, README
|
|
8
|
+
and release records; dependencies and compatibility tuple remain pinned.
|
|
9
|
+
The original seven-field enrollment descriptor and rollback discovery layout
|
|
10
|
+
remain unchanged. Source behavior and historical failed-check evidence are in
|
|
11
|
+
[[2026-11-15-live-activity-title-provenance]].
|
|
12
|
+
|
|
13
|
+
Fresh Node24.13.0 `npm ci --ignore-scripts` installs the pinned lock and audits
|
|
14
|
+
zero vulnerabilities. Default `npm run check` passes267tests with zero failures
|
|
15
|
+
or skips, plus typecheck/build. Actual `npm run smoke:upgrade` accepts compatible
|
|
16
|
+
activation, failed-candidate rollback, retained bootstrap/previous, aliased
|
|
17
|
+
frontend selection and clean stop. It uses disposable private prefixes and owned
|
|
18
|
+
test processes; no native login service or real provider session is touched.
|
|
19
|
+
`node scripts/release.mjs validate v0.1.8` passes. Deterministic pack and hosted
|
|
20
|
+
publication/receiver results are recorded separately after their actual completion.
|
|
21
|
+
|
|
22
|
+
Independent same-provider follow-up `run-20261115121907-cdb3164c` closes all4
|
|
23
|
+
initial blockers and independently passes11CLI tests. The earlier external
|
|
24
|
+
provider account hold yielded no review; this is an independent-context fallback,
|
|
25
|
+
not a cross-vendor approval. The previously accepted complete267/267and focused
|
|
26
|
+
24/24results remain preserved alongside this fresh release gate.
|
|
27
|
+
|
|
28
|
+
## Hosted pathname-read race found before tagging
|
|
29
|
+
|
|
30
|
+
Candidate541715e's first hosted CI exposed `FOREIGN_RESOURCE_LINKS` in the real
|
|
31
|
+
local-enrollment consumer's config read on Ubuntu. The tag was withheld. Initial
|
|
32
|
+
and final pathname lookup can observe a valid owned inode whose link count has
|
|
33
|
+
already become0during atomic rename, before the stat result reaches the caller.
|
|
34
|
+
The previous reader handled that retirement only after opening a file descriptor.
|
|
35
|
+
|
|
36
|
+
Two deterministic regressions hold the real old inode, rename its replacement,
|
|
37
|
+
and return that inode's actual retired fstat as the pathname lookup result; both
|
|
38
|
+
failed with the hosted stack's error before the fix. The minimal private-reader
|
|
39
|
+
helper recognizes only retired0, strictly validates a different ordinary owned
|
|
40
|
+
replacement and reopens within the original3attempts. General inspect/write/delete
|
|
41
|
+
paths remain strict. Eight additional retirement-to-foreign replacement cases
|
|
42
|
+
retain symlink/hardlink/mode/limit rejection. Original observed-mutation and
|
|
43
|
+
continuous-replacement tests remain intact. The resource suites pass34/34locally;
|
|
44
|
+
the10POSIX retirement-specific cases are explicitly unsupported on Windows.
|
|
45
|
+
Original candidate bytes/checksum, hosted failure and actual RED/GREEN logs are
|
|
46
|
+
retained separately rather than overwritten or described as a successful release.
|
|
47
|
+
|
|
48
|
+
Independent Codex review then found an integrity gap: final pathname lookup could
|
|
49
|
+
observe size/mtime changes made after the final handle fstat, yet the retired0
|
|
50
|
+
branch discarded that observation. Two actual-fd truncate/equal-size regressions
|
|
51
|
+
first failed. The final helper receives the opened snapshot and rejects observed
|
|
52
|
+
same-inode size/mtime differences before any retirement retry; retirement's own
|
|
53
|
+
ctime change is not treated as a content write. Resource suites now pass36/36.
|
|
54
|
+
The first independent reviewer re-ran36/36and closed its P2 in follow-up
|
|
55
|
+
`run-20261115131303-ff270ab1`; a second independent static security context matched
|
|
56
|
+
the frozen source/test hashes and confirmed the corrected final-read fence.
|
|
57
|
+
Both are same-provider fallbacks, not cross-provider approvals. Wrong-uid, fd-close
|
|
58
|
+
counts and no-read-on-retired-handle are verified by control flow rather than
|
|
59
|
+
new direct counters in these regressions.
|
|
60
|
+
|
|
61
|
+
The obsolete initial CI retained its Ubuntu failure and macOS success. Windows
|
|
62
|
+
was canceled after its real enrollment consumer missed the original15s admission
|
|
63
|
+
deadline; its stalled teardown made the job linger. That failure is not described
|
|
64
|
+
as a proven consequence of the POSIX lookup race. The fixture now reports only
|
|
65
|
+
allowlisted stage/error codes and synthetic request counts, and stops its own
|
|
66
|
+
child before server teardown on failures/abort. Original15s/20sassertions remain
|
|
67
|
+
unchanged. A new complete source/test check and all3hosted platforms are required
|
|
68
|
+
for the final candidate; the initial CI is not accepted as the release gate.
|
|
69
|
+
|
|
70
|
+
The final frozen production guard and diagnostic fixture pass a fresh default
|
|
71
|
+
complete279/279check with types/build and the actual packaged upgrade/rollback
|
|
72
|
+
smoke. The focused real enrollment consumer passes1/1. A separate temporary
|
|
73
|
+
failure probe disables its synthetic claim and deliberately uses a1500msprobe
|
|
74
|
+
admission deadline; it retains the failure and exits with owned-child/server
|
|
75
|
+
teardown in2.685s. That probe does not alter the repository's15s/20sassertions.
|
|
76
|
+
Final hosted platform checks/publication/receiver acceptance remain pending.
|
|
77
|
+
|
|
78
|
+
## Publication boundary
|
|
79
|
+
|
|
80
|
+
The existing GitHub `Release` workflow and its scoped repository/environment
|
|
81
|
+
publishing authority perform npm publication and create the GitHub Release only
|
|
82
|
+
after npm accepts the exact tested tarball. A pushed tag or successful identity
|
|
83
|
+
check alone does not establish public availability. Independent anonymous registry
|
|
84
|
+
download, exact-version isolated installation and tarball/checksum equality are
|
|
85
|
+
required before recording publication as accepted. No real everyday service is
|
|
86
|
+
restarted or upgraded by this release procedure.
|
|
@@ -116,3 +116,11 @@ resource/key/permission/billing mutations requiring point-of-risk interactive
|
|
|
116
116
|
confirmation. No deployment, Apple activation, physical delivery, public
|
|
117
117
|
publication or everyday-host service installation is claimed by this update.
|
|
118
118
|
|
|
119
|
+
|
|
120
|
+
## November15 informative-alert iteration
|
|
121
|
+
|
|
122
|
+
The owner approved useful session/content notifications. The optional encrypted
|
|
123
|
+
preview, native offline display and passive compatibility contract extend only
|
|
124
|
+
ordinary notifications, preserving original commands, expiry and authority. Local
|
|
125
|
+
implementation and acceptance: [[2026-11-15-informative-notifications-and-settings]]. No new
|
|
126
|
+
publishing/deployment/Apple or real notification operation is included.
|
|
@@ -0,0 +1,99 @@
|
|
|
1
|
+
# Remote Live Activities through shared notification delivery
|
|
2
|
+
|
|
3
|
+
Status: owner-requested implementation, unreleased. This supersedes only the
|
|
4
|
+
previous prohibition on ActivityKit APNs; widgets stay independent of cloud.
|
|
5
|
+
|
|
6
|
+
## User contract
|
|
7
|
+
|
|
8
|
+
Preserve one aggregate island per phone across paired computers. Pending new
|
|
9
|
+
questions/approvals and real completion/error occurrences receive fair sequential
|
|
10
|
+
presentation (eight seconds with ongoing work, fifteen seconds for final notices).
|
|
11
|
+
Without new notices choose the most recently opened ongoing conversation. No
|
|
12
|
+
confirmed ongoing work and no pending announcement means no activity; an unknown
|
|
13
|
+
source is never treated as proof of completion. No manual tracking, second
|
|
14
|
+
enablement, continued app execution requirement or extra sound is introduced. Existing
|
|
15
|
+
local-only behavior remains available without the optional computer CLI.
|
|
16
|
+
|
|
17
|
+
## Confirmed platform facts
|
|
18
|
+
|
|
19
|
+
Apple does not allow a Live Activity renderer to access the network. Native
|
|
20
|
+
ActivityKit APNs can start/update/end it without a continually running app.
|
|
21
|
+
Use token-based unicast, not public broadcast channels. Observe token rotations,
|
|
22
|
+
use the separate liveactivity APNs topic/type, and send only bounded content-state.
|
|
23
|
+
This implementation remotely updates/ends an activity that the foreground app
|
|
24
|
+
has already started. Push-to-start is not implemented or claimed. A new activity
|
|
25
|
+
after expiry/termination still requires opening the app; raw stateKey is never
|
|
26
|
+
uploaded in push-to-start attributes.
|
|
27
|
+
OS delivery budgets, disconnected phones, disabled activities and force-quit
|
|
28
|
+
behavior are system constraints, not an always-delivered guarantee.
|
|
29
|
+
|
|
30
|
+
References:
|
|
31
|
+
- https://developer.apple.com/documentation/activitykit/displaying-live-data-with-live-activities
|
|
32
|
+
- https://developer.apple.com/documentation/activitykit/starting-and-updating-live-activities-with-activitykit-push-notifications
|
|
33
|
+
|
|
34
|
+
## Shared transport and ownership
|
|
35
|
+
|
|
36
|
+
Use the existing paired CLI observer, HTTPS ingress, PAIRS namespace, APNs signer
|
|
37
|
+
and retry machinery. A phone-installation aggregate coordinator serializes all
|
|
38
|
+
paired host contributions; independent hosts must never race the same token.
|
|
39
|
+
Reuse a paired event-batch request for notification attention and ActivityKit
|
|
40
|
+
changes. Control polling passively returns activity subscription metadata; no
|
|
41
|
+
new capability polling, widget feed or phone status polling is introduced.
|
|
42
|
+
Only semantic state changes publish; token registration/rotation and bounded
|
|
43
|
+
freshness renewal are separate infrequent operations. Spinning/prose streaming
|
|
44
|
+
never produce Worker requests. Ordinary notifications and silent activity pushes
|
|
45
|
+
may require distinct APNs requests; they cannot share an Apple token/type.
|
|
46
|
+
|
|
47
|
+
## Confidentiality and authority
|
|
48
|
+
|
|
49
|
+
No endpoint root, command/control key, provider credential, host password or
|
|
50
|
+
plaintext title/question/response enters the cloud. Each host contribution is
|
|
51
|
+
sealed with its pair's dedicated activity-state key. The renderer uses protected
|
|
52
|
+
local display-only keys, exact host/daemon/pair lifetimes and authenticated route
|
|
53
|
+
identities; a new background conversation need not already be in the local catalog.
|
|
54
|
+
Public minimal phase/occurrence routing metadata is documented separately from
|
|
55
|
+
encrypted labels and navigation. No display record can execute an operation.
|
|
56
|
+
|
|
57
|
+
Phone-scoped configuration binds the installation, coordinator capability,
|
|
58
|
+
ActivityKit type/environment/token generation and enabled host membership. Host
|
|
59
|
+
credentials only submit their own contribution; they cannot register another
|
|
60
|
+
phone or choose arbitrary provider topics. Local disable/delete/re-pair fences
|
|
61
|
+
rendering synchronously; durable cloud retirement and exact registration compare
|
|
62
|
+
prevent old retries from moving to a replacement token or reviving a stopped run.
|
|
63
|
+
|
|
64
|
+
## Lifecycle and ordering
|
|
65
|
+
|
|
66
|
+
Persist occurrence/fair queue and outbound attempt identity before provider I/O.
|
|
67
|
+
Exact retries retain bytes and APNs identity. Coalesce routine state while keeping
|
|
68
|
+
new questions/approvals/completions distinct. Late state generations cannot
|
|
69
|
+
regress a newer observation. APNs timestamps are monotonically ordered per
|
|
70
|
+
aggregate; return to foreground reconciles authoritative Paseo state and existing
|
|
71
|
+
system activities without duplicating them. Eight-hour activity expiry and
|
|
72
|
+
start/update token rotation must be explicit, including failed or delayed starts.
|
|
73
|
+
|
|
74
|
+
## Implemented bounds and ordering
|
|
75
|
+
|
|
76
|
+
The shared events ingress and private publish hop alone accept512KiB; ordinary
|
|
77
|
+
requests remain128KiB, each interest8KiB and each encrypted candidate2700bytes.
|
|
78
|
+
There are at most100candidates per source,512per aggregate,16paired sources,
|
|
79
|
+
and1,900,000bytes per aggregate storage row. CLI pending-publication storage is bounded to
|
|
80
|
+
1MiB. Real100-target long-label regressions cover the full budget end to end.
|
|
81
|
+
Token-only registration reuses immutable interest; replacement contributions are
|
|
82
|
+
unknown until observed. Cleanup binds member registrationId AND client revision.
|
|
83
|
+
A server wall clock never replaces the client's registration version. App local
|
|
84
|
+
background writes yield only after the native activity contains a valid v2
|
|
85
|
+
payload, not after HTTP registration. Foreground local rendering has a45second
|
|
86
|
+
lease refreshed by existing publication, with no network timer.
|
|
87
|
+
|
|
88
|
+
## Acceptance
|
|
89
|
+
|
|
90
|
+
Test real bundled decoder/routes, not a catalog-only replay. Cover two computers
|
|
91
|
+
and multiple conversations, pending question during running, sequential final
|
|
92
|
+
notices, last-opened fallback, app absent, cold new conversation, out-of-order
|
|
93
|
+
state, expiry, restart, token rotation, dismissal/disable/revocation races, full
|
|
94
|
+
four-kilobyte payload limits, immutable uncertain retries and zero polling for
|
|
95
|
+
unchanged state. Native simulated delivery is separate from real device APNs
|
|
96
|
+
acceptance. Publish actual request-count evidence for shared event ingress.
|
|
97
|
+
|
|
98
|
+
No new cloud deployment, public CLI package, Apple capability/key, persistent
|
|
99
|
+
service or TestFlight delivery is included in local implementation acceptance.
|
|
@@ -104,8 +104,9 @@ publication remains separately authorized.
|
|
|
104
104
|
## Notification-only cloud boundary — November 14
|
|
105
105
|
|
|
106
106
|
The optional companion publishes only current question/approval forms and their
|
|
107
|
-
exact occurrence bindings. It does not request provider usage or upload
|
|
108
|
-
|
|
107
|
+
exact occurrence bindings. It does not request provider usage or upload a conversation directory. A current
|
|
108
|
+
alert may carry its bounded title, host label and excerpt only inside the optional
|
|
109
|
+
endpoint-encrypted preview described in02. Accepted source reads
|
|
109
110
|
retain pending requests outside the bounded recent discovery page; stale reads
|
|
110
111
|
and resolved/replaced occurrences cannot restore them. Publication changes are
|
|
111
112
|
deduplicated; only pending hydration renews near expiry, and one empty publication
|
|
@@ -113,3 +114,15 @@ clears the last resolved request. Unknown acknowledgements retain immutable byte
|
|
|
113
114
|
No activity interests, WidgetKit registrations or dedicated surface APNs calls
|
|
114
115
|
remain. Notification control, explicit reply/approval execution, immutable action
|
|
115
116
|
journals and outcome reconciliation retain their original safeguards.
|
|
117
|
+
|
|
118
|
+
## Optional activity title provenance — unreleased November 15
|
|
119
|
+
|
|
120
|
+
An active phone activity separately owns bounded official agent and workspace
|
|
121
|
+
read subscriptions. The phone may authorize an exact agent/workspace title source;
|
|
122
|
+
the companion resolves current official text, never a cached phone title. Missing
|
|
123
|
+
provenance cannot be inferred from a partial recent directory. Visible shared roots
|
|
124
|
+
deny workspace projection; managed children do not count as independent roots.
|
|
125
|
+
Workspace updates enter the existing semantic event fingerprint, not another
|
|
126
|
+
Worker poll. Unknown workspace metadata delays only activity publication; explicit
|
|
127
|
+
empty official titles fall back to agent text. Same-daemon read recovery retains
|
|
128
|
+
confirmed names until new authority arrives. Disabling releases every read interest.
|
|
@@ -184,8 +184,52 @@ it does not execute or renew an expired command, question or approval. The norma
|
|
|
184
184
|
command decoder and recipient pre-dispatch expiry checks remain strict.
|
|
185
185
|
|
|
186
186
|
|
|
187
|
+
|
|
188
|
+
### Encrypted notification presentation — unreleased November 15
|
|
189
|
+
|
|
190
|
+
An attention POST may additionally carry `preview`, a separately sealed attention
|
|
191
|
+
channel envelope with the exact same pair, ID, issuedAt and expiresAt as `envelope`.
|
|
192
|
+
Its plaintext is exactly `{type:"notificationPreview",version:1,agentId,kind,
|
|
193
|
+
timestamp,title,hostName,body}`. Identity/kind/time must match the authenticated
|
|
194
|
+
route. It uses a fresh random nonce under the existing independently derived
|
|
195
|
+
attention key; legacy route plaintext and action authority are unchanged.
|
|
196
|
+
Title/host/excerpt limits are256/128/960 UTF-8 bytes. Only current-turn assistant
|
|
197
|
+
prose or the exact current question/approval/error is included, never reasoning,
|
|
198
|
+
tool output or a full transcript. A finished event may read one canonical30-entry
|
|
199
|
+
tail with a five-second timeout; recovery uses at most two concurrent tails,
|
|
200
|
+
checks the same terminal identity and does not block control/directory polling.
|
|
201
|
+
|
|
202
|
+
Cloud never decrypts previews. The complete APNs JSON in either locale must fit
|
|
203
|
+
4,096 bytes; endpoints reduce or omit only the optional preview before immutable
|
|
204
|
+
publication. Retry never changes already journaled bytes. Expiry/revoke removes
|
|
205
|
+
both ciphertexts at the original route deadline; audit digests do not renew them.
|
|
206
|
+
A native notification service extension authenticates/decrypts locally, with only
|
|
207
|
+
the derived attention display key in protected shared Keychain storage. It retains
|
|
208
|
+
the original category/actions/userInfo. No network lookup or extra cloud request
|
|
209
|
+
is required. Missing keys, unavailable extension or invalid preview retain a safe
|
|
210
|
+
localized fallback; an authenticated legacy route may use cached local labels.
|
|
211
|
+
|
|
187
212
|
## Required evidence
|
|
188
213
|
|
|
214
|
+
An optional v2 `activityInterest` plaintext may contain `titleHints`, at most32
|
|
215
|
+
exact `{agentId,workspaceId,source:"conversation"|"workspace"}` objects whose full
|
|
216
|
+
UTF-8 JSON array is at most4000bytes. IDs are nonempty, at most512 UTF-8 bytes,
|
|
217
|
+
and exclude whitespace, slashes, backslashes and control characters. Duplicate
|
|
218
|
+
agent IDs, unknown fields, cached title text and other source values reject.
|
|
219
|
+
Existing host/daemon/lifetime and encrypted interest expiry bind every hint.
|
|
220
|
+
Only a matching workspace hint permits current official workspace text; conversation,
|
|
221
|
+
missing/mismatched hints or visible multiple roots retain current agent text.
|
|
222
|
+
The relay sees only the existing opaque envelope. Unknown publications keep
|
|
223
|
+
their exact original ciphertext, even if names or hints change before acknowledgement.
|
|
224
|
+
Missing workspace metadata is unknown, not an empty title: optional activity
|
|
225
|
+
publication waits without delaying notifications. A full official workspace entry
|
|
226
|
+
with a missing/null/blank title permits agent fallback; a removal is unknown.
|
|
227
|
+
Read failures and bounded-page omissions retain
|
|
228
|
+
confirmed metadata. One workspace shares generation/sequence ordering across
|
|
229
|
+
subscriptions; older same-generation snapshots cannot replace newer updates.
|
|
230
|
+
Without sequence evidence, an active exact owned read outranks a broad read;
|
|
231
|
+
legacy exact seeds cannot overwrite stream changes observed during their request.
|
|
232
|
+
|
|
189
233
|
Cross-runtime vectors cover exact encryption/decryption and authenticated metadata;
|
|
190
234
|
wrong keys, modified routing, expired envelopes and unsupported versions fail.
|
|
191
235
|
State-machine tests cover conflicting reuse, restart at each execution boundary,
|
|
@@ -4,7 +4,7 @@
|
|
|
4
4
|
|
|
5
5
|
## Common rules
|
|
6
6
|
|
|
7
|
-
Base path is `/v1`. JSON is UTF-8 with bounded body parsing (128 KiB). Responses
|
|
7
|
+
Base path is `/v1`. JSON is UTF-8 with bounded body parsing (128 KiB; shared v2 events512KiB). Responses
|
|
8
8
|
use `{ok:true,...}` or `{ok:false,error:{code,message}}`; errors contain concise
|
|
9
9
|
codes, never raw private payloads. TLS is required except explicit loopback dev.
|
|
10
10
|
UUID identifiers are lowercase canonical strings. Timestamps are integer epoch
|
|
@@ -145,14 +145,14 @@ No official heartbeat/read acknowledgement is sent by the companion.
|
|
|
145
145
|
|
|
146
146
|
### POST /pairs/{pairId}/attention; GET /pairs/{pairId}/attention/{eventId}
|
|
147
147
|
|
|
148
|
-
Host writes, phone reads exact event. Body `{id,kind,topic,envelope}`; kind is
|
|
148
|
+
Host writes, phone reads exact event. Body `{id,kind,topic,envelope,preview?}`; kind is
|
|
149
149
|
`finished|question|permission|error`, envelope channel `attention` and ID `id`.
|
|
150
150
|
Encrypted content contains `{agentId,requestId?,requestBinding?,kind,timestamp}`;
|
|
151
151
|
question/permission attention includes the exact companion-issued requestBinding.
|
|
152
152
|
Event identity is stable across reconnect/retry. Exact retry does not send another
|
|
153
153
|
push; conflicting bytes are rejected. Only currently valid events get attempts.
|
|
154
154
|
Suppress this app's push if a genuine unexpired matching presence lease exists.
|
|
155
|
-
No inference from the official shouldNotify flag. APNs copy is generic/localized.
|
|
155
|
+
No inference from the official shouldNotify flag. APNs fallback copy is generic/localized.
|
|
156
156
|
|
|
157
157
|
Persist notification attempt state before I/O. A lost APNs response is uncertain,
|
|
158
158
|
not proof of failure; retries reuse the same apns-id/collapse identity with bounded
|
|
@@ -304,8 +304,8 @@ Delivery states are `queued|inflight|retry|uncertain|accepted|rejected|unavailab
|
|
|
304
304
|
suppressed|expired|revoked|resolved`; they never assert display or acknowledgement.
|
|
305
305
|
Missing configuration is `unavailable`, not provider acceptance.
|
|
306
306
|
|
|
307
|
-
APNs custom data is
|
|
308
|
-
`aps`. `route` is the original attention envelope, never a plaintext conversation
|
|
307
|
+
APNs custom data is `pairId,eventId,kind,route` plus optional encrypted `preview`,
|
|
308
|
+
beside localized fallback `aps` with `mutable-content:1`. `route` is the original attention envelope, never a plaintext conversation
|
|
309
309
|
identifier. Attention ingestion rejects any event whose complete alert payload
|
|
310
310
|
would exceed4,096 UTF-8 bytes in either supported locale (`413`,
|
|
311
311
|
`apns_payload_too_large`), even before a device registers. No route is silently
|
|
@@ -399,7 +399,7 @@ most32 entries;32 near-maximum envelopes can approach4MiB. Exact command reads
|
|
|
399
399
|
may contain both original128KiB-bounded payload and a separate8KiB receipt; a
|
|
400
400
|
host pairing response may contain two bounded proofs. A128KiB response reader
|
|
401
401
|
would permanently reject valid work and is nonconforming. This larger response
|
|
402
|
-
budget never raises the128KiB request or64KiB decrypted command-content limits.
|
|
402
|
+
budget never raises the128KiB ordinary-request or64KiB decrypted command-content limits.
|
|
403
403
|
|
|
404
404
|
### Retired system-surface routes
|
|
405
405
|
|
|
@@ -410,3 +410,51 @@ these features remain. Durable Object initialization purges legacy surface rows;
|
|
|
410
410
|
notification device, attention, operation and control records remain intact.
|
|
411
411
|
Widgets and local ActivityKit read/update through the official Paseo path and
|
|
412
412
|
shared device state, independently of this notification service.
|
|
413
|
+
|
|
414
|
+
|
|
415
|
+
## Optional preview interoperability — unreleased November 15
|
|
416
|
+
|
|
417
|
+
Successful authenticated pair responses advertise
|
|
418
|
+
`x-moremote-notification-preview:1`; existing successful response bodies remain
|
|
419
|
+
unchanged. A new companion observes this passively on existing control reads
|
|
420
|
+
before adding `preview` to a newly journaled attention event. An older relay gets
|
|
421
|
+
the immutable legacy shape, without an extra capability request. Existing
|
|
422
|
+
journaled events are never resealed or stripped after attempted publication.
|
|
423
|
+
A new relay accepts both exact legacy and exact optional-preview shapes. Preview
|
|
424
|
+
metadata must match the route interval, pairing, attention channel and event ID;
|
|
425
|
+
unknown fields remain invalid. The same event's digest covers both ciphertexts.
|
|
426
|
+
Both are actively erased on original expiry/revoke. Existing attention GET
|
|
427
|
+
response names, attempt/registration fences, uncertain outcomes, categories and
|
|
428
|
+
reply/current-request validation are unchanged. New apps can label legacy alerts
|
|
429
|
+
from authenticated local cache; old apps retain the safe localized alert fallback.
|
|
430
|
+
|
|
431
|
+
## Remote activity v2 (unreleased)
|
|
432
|
+
|
|
433
|
+
Only the authenticated phone may PUT `/pairs/:id/live-activity` with
|
|
434
|
+
subscriptionId, generation, monotonic client revision, activity token/environment,
|
|
435
|
+
startedAt, deadline, encrypted interest and a32byte aggregate membership capability.
|
|
436
|
+
DELETE takes `{revision}` and cannot retire a newer registration. Interest is
|
|
437
|
+
bounded to8KiB and8hours; the separate local rendering seed never enters cloud.
|
|
438
|
+
The existing host controls response passively includes registrationId/interest
|
|
439
|
+
and `x-moremote-live-activity:2`; no capability probe is added.
|
|
440
|
+
|
|
441
|
+
Host POST `/pairs/:id/events` takes `{attention:[...],activity?:contribution}`.
|
|
442
|
+
This route and its private publish hop alone allow512KiB; other requests remain
|
|
443
|
+
128KiB. Attention has at most8 original immutable events, independent per-ID ACKs;
|
|
444
|
+
activity has a separate accepted result, registrationId and increasing sequence.
|
|
445
|
+
Each source may publish100 candidates (aggregate512 across16pairs), with encrypted
|
|
446
|
+
payloads at most2700bytes each. Opaque topic/cycle/event identities plus minimal
|
|
447
|
+
phase/ordering metadata support fair arbitration; titles/routes remain encrypted.
|
|
448
|
+
Provider content-state is `{payload:string}` containing the bounded v2 wrapper.
|
|
449
|
+
APNs uses liveactivity type, `<bundle>.push-type.liveactivity` topic, priority5
|
|
450
|
+
for routine updates/10for attention or end, ordered epoch-second timestamps,
|
|
451
|
+
stale-date and immediate end dismissal. Apple4KiB limits are checked after final
|
|
452
|
+
serialization. Registration, exact retries, revocation and end never authorize
|
|
453
|
+
commands. Legacy activity/widget routes remain410. No push-to-start is implemented.
|
|
454
|
+
|
|
455
|
+
Optional title provenance changes only encrypted endpoint plaintext, not any
|
|
456
|
+
HTTP request/response shape or routing authority. Capable companions accept
|
|
457
|
+
the bounded `titleHints` extension specified in02; phones send it only after
|
|
458
|
+
matching a fresh official-file capability to the current enrollment descriptor.
|
|
459
|
+
Older companions receive the unchanged interest shape. No cloud capability
|
|
460
|
+
probe, title plaintext, additional event route or Worker poll is introduced.
|
|
@@ -173,6 +173,11 @@ claim a local resolve API erases a notification already displayed by iOS.
|
|
|
173
173
|
|
|
174
174
|
## Required regression cases
|
|
175
175
|
|
|
176
|
+
Activity title-source hints are presentation-only: they cannot select a command
|
|
177
|
+
target, approve a request, clear attention or change any operation/receipt identity.
|
|
178
|
+
Resolving a rename preserves all exact unknown-publication bytes and existing
|
|
179
|
+
dispatch, revocation and expiry checks.
|
|
180
|
+
|
|
176
181
|
- Lost/withheld revoke reaches cloud but not companion: no endpoint-confirmed UI.
|
|
177
182
|
- Revoke/cancel persisted locally survives restart and blocks later dispatch;
|
|
178
183
|
already-dispatched cancellation is tooLate, not falsely cancelled.
|
|
@@ -50,6 +50,20 @@ over the already authenticated official file channel. Descriptor lifetime is90s,
|
|
|
50
50
|
renewed no faster than30s; disablement can remove resources or publish disabled
|
|
51
51
|
without granting a new enabled lease. This is not a cloud heartbeat.
|
|
52
52
|
|
|
53
|
+
Optional activity title support is published outside that legacy tree at
|
|
54
|
+
`<home>/.moremote-cli-activity/<sha256(UTF8 daemonServerId)>/capabilities.json`.
|
|
55
|
+
Its exact bounded object is `{version:1,daemonServerId,instanceId,measuredAt,
|
|
56
|
+
expiresAt,titleHints:1}`. It contains no title text or keys. The independent
|
|
57
|
+
marked0700 directories bind to the same state directory; the0600 document uses
|
|
58
|
+
the descriptor's exact instance/clock/90s expiry and30s renewal, while the existing
|
|
59
|
+
enrollment runtime holds its exclusive lock. Matching-instance stop removes it;
|
|
60
|
+
foreign files/markers/symlinks are never overwritten or deleted. Phones require
|
|
61
|
+
a fresh matching enabled descriptor and capability before sending title hints.
|
|
62
|
+
The old descriptor fields/tree stay unchanged, so an older runtime rollback
|
|
63
|
+
ignores the separate tree; a retained file loses authority on instance mismatch
|
|
64
|
+
or expiry. A later capable runtime can replace a valid old-instance document
|
|
65
|
+
only after acquiring the normal enrollment runtime lock.
|
|
66
|
+
|
|
53
67
|
After validating the original authenticated host/session/generation and fresh
|
|
54
68
|
descriptor, the app durably retains one exact immutable UTF-8 request before
|
|
55
69
|
official create/read-revision/write. Empty files are unfinished creates, not
|
|
@@ -114,6 +128,11 @@ Config/resource readers and atomic writers use the same524288-byte serialized
|
|
|
114
128
|
bound, preserving full original request bytes. Oversize writes reject before
|
|
115
129
|
replacement. Only acquired runtime ownership initializes fresh config; duplicate
|
|
116
130
|
`run` never writes an old loaded config over live enrollment.
|
|
131
|
+
Private reads retain their3-attempt bound when a POSIX pathname lookup itself
|
|
132
|
+
returns an inode retired by rename. Reopening requires a different strictly
|
|
133
|
+
owned regular replacement; no retired bytes may be returned. Hardlinks, symlinks,
|
|
134
|
+
foreign owners/modes and observed in-place mutation still reject, and mutation
|
|
135
|
+
operations do not gain this read-only retry permission.
|
|
117
136
|
|
|
118
137
|
## Expert-only manual enrollment offer v1
|
|
119
138
|
|