@moxuli/moremote 0.0.0-stage → 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (67) hide show
  1. package/LICENSE +202 -0
  2. package/NOTICE +31 -0
  3. package/README.md +73 -2
  4. package/bin/moremote-cli.js +34 -0
  5. package/bin/moremote-service.js +7 -0
  6. package/dist/bindings.d.ts +6 -0
  7. package/dist/bindings.js +4 -0
  8. package/dist/cli.d.ts +1 -0
  9. package/dist/cli.js +325 -0
  10. package/dist/cloud-client.d.ts +43 -0
  11. package/dist/cloud-client.js +128 -0
  12. package/dist/config.d.ts +36 -0
  13. package/dist/config.js +68 -0
  14. package/dist/control-transport.d.ts +4 -0
  15. package/dist/control-transport.js +68 -0
  16. package/dist/control.d.ts +3 -0
  17. package/dist/control.js +297 -0
  18. package/dist/controls.d.ts +15 -0
  19. package/dist/controls.js +36 -0
  20. package/dist/crypto.d.ts +23 -0
  21. package/dist/crypto.js +68 -0
  22. package/dist/evidence.d.ts +19 -0
  23. package/dist/evidence.js +4 -0
  24. package/dist/journal.d.ts +104 -0
  25. package/dist/journal.js +132 -0
  26. package/dist/limits.d.ts +21 -0
  27. package/dist/limits.js +8 -0
  28. package/dist/official-client.d.ts +120 -0
  29. package/dist/official-client.js +162 -0
  30. package/dist/operations.d.ts +71 -0
  31. package/dist/operations.js +210 -0
  32. package/dist/pairing.d.ts +19 -0
  33. package/dist/pairing.js +68 -0
  34. package/dist/permission.d.ts +9 -0
  35. package/dist/permission.js +66 -0
  36. package/dist/projection.d.ts +24 -0
  37. package/dist/projection.js +35 -0
  38. package/dist/resources.d.ts +76 -0
  39. package/dist/resources.js +299 -0
  40. package/dist/runtime.d.ts +8 -0
  41. package/dist/runtime.js +375 -0
  42. package/dist/service.d.ts +21 -0
  43. package/dist/service.js +310 -0
  44. package/dist/supervisor.d.ts +15 -0
  45. package/dist/supervisor.js +175 -0
  46. package/dist/update-state.d.ts +30 -0
  47. package/dist/update-state.js +158 -0
  48. package/dist/updater.d.ts +9 -0
  49. package/dist/updater.js +152 -0
  50. package/docs/README.md +23 -0
  51. package/docs/STATE.md +155 -0
  52. package/docs/configuration.md +37 -0
  53. package/docs/conventions.md +9 -0
  54. package/docs/decisions/0001-managed-updates.md +19 -0
  55. package/docs/plans/2026-11-10-managed-updates.md +26 -0
  56. package/docs/plans/2026-11-10-notification-delivery.md +118 -0
  57. package/docs/releasing.md +34 -0
  58. package/docs/specs/01-architecture.md +102 -0
  59. package/docs/specs/02-encrypted-delivery.md +194 -0
  60. package/docs/specs/03-api-contract.md +397 -0
  61. package/docs/specs/04-control-and-receipt-lifecycle.md +175 -0
  62. package/docs/specs/05-endpoint-and-lifecycle.md +57 -0
  63. package/docs/specs/06-managed-updates.md +55 -0
  64. package/licenses/Paseo-0.15.3.txt +211 -0
  65. package/package.json +37 -4
  66. package/vectors/bearer-v1.json +6 -0
  67. package/vectors/envelope-v1.json +24 -0
@@ -0,0 +1,55 @@
1
+ # 06 — Managed updates and release identity
2
+
3
+ ## Scope and ownership
4
+
5
+ Public npm identity is exactly `@moxuli/moremote`; executable/repository/service/data names remain `moremote-cli`. Only this package is requested from `https://registry.npmjs.org`. Node24.13.0 is the pinned build/release runtime; supported runtime is Node24.13+ within Node24. Never upgrade Node, npm globally, official Paseo, its daemon registration or official data.
6
+
7
+ An actual scoped npm installation is identified by its resolved module location (`node_modules/@moxuli/moremote`), exact manifest identity and current-user resource ownership, not cwd or a matching directory substring. A source checkout stays foreground/manual until explicit `update` or `service-install --yes`. A root/foreign-owned scoped installation is rejected rather than implicitly adopted; install the public package in a user-owned npm prefix. Read-only global package bytes are never modified: the updater uses only the separately owned private state directory. Unwritable or foreign private state is an error, not success.
8
+
9
+ The retained/global frontend dispatches raw arguments to the verified selected CLI before option parsing, so newer flags and `--version` execute the selected package without replacing package-manager files. Compare canonical real paths, not raw entry strings: Node ESM canonicalizes its import URL, and a parent-directory alias must not cause recursive delegation to the same executable. A supervisor child bypasses this frontend redirection while an uncommitted candidate is being assessed.
10
+
11
+ Delegating frontends forward termination and wait for the selected process. Their OS child IPC channel also proves parent lifetime: parent disconnect/death shuts down the selected supervisor, which drains its runtime and waits for ownership release. Check already-disconnected startup as well as future disconnect events. Initialization cleanup starts immediately after acquiring runtime control ownership; a SQLite constructor/schema failure closes any opened database and releases the server/lock before reporting startup failure, allowing rollback to proceed.
12
+
13
+ Managed npm arguments pin **both** the default registry and `@moxuli:registry` to npmjs; an inherited scoped registry cannot redirect selected public-package installation.
14
+
15
+ Readiness observers use the runtime's positive parent IPC acknowledgement after journal initialization, relayed through the supervisor/frontend. They do not inspect staged socket ownership before publication or treat a partial filesystem snapshot as readiness. Terminal child exit rejects readiness immediately; bounded test/command cancellation remains in force. Read-only control discovery retains its strict foreign/unproven-stage protections.
16
+
17
+ An empty control EOF or reset is `CONTROL_CONNECTION_CLOSED` while the previously validated owner still exists, not a raw JSON parser exception or a successful stop. A malformed/nonobject reply is `CONTROL_INVALID_RESPONSE`. Only observed retirement/replacement of that exact validated record can classify an empty disconnect as not-running. No control or official mutation is retried because of a lost reply.
18
+
19
+ Ephemeral control transport compatibility: `managed/runtime-transport.json` is a marked version1, private/no-follow descriptor binding `json-lines-v1` to instanceId, pid, startedAt and SHA256(token). It is durably published before the runtime record. The original strict runtime.lock/runtime.json shapes remain unchanged, so retained0.1.0 readers and crash recovery can still read them; the existing marked managed directory contains the additional descriptor. Cleanup removes only the matching descriptor inode/generation.
20
+
21
+ The controller chooses one transport from that fact before sending: a matching descriptor means bounded4KiB newline frames and a duplex connection; no descriptor or a valid descriptor from another generation means the known0.1.0 EOF/unframed transport on POSIX. Invalid/linked/foreign descriptors are terminal, not an excuse to guess or probe. Ownership and selected framing are revalidated immediately before the single write. There is no timeout-based fallback, second connection or action replay.
22
+
23
+ Historical Windows boundary: unchanged published0.1.0 EOF-only control cannot provide a reliable duplex named-pipe reply. A live such generation reports `LEGACY_WINDOWS_CONTROL_UNAVAILABLE`, never fake status/stopped. It remains an explicit selectable candidate. The retained supervisor's separate child IPC can still drain, roll back or stop it. A managed stop waits for supervisor retirement and positive runtime retirement evidence before reporting success; an unsupervised live historical runtime remains unavailable/unknown. New framed runtimes retain full Windows support. An absent PID or retired record is evidence, not permission to signal an arbitrary PID.
24
+
25
+ The first installed-package `run` or explicit service installation obtains its exact current version into `managed/versions/<version>/node_modules/@moxuli/moremote`. Lifecycle scripts are disabled. npm network retries are disabled, fetches have a60second limit and installation has a120second process limit. Package name/version, ordinary nonsymlinked build/entry files and directory ownership are verified before an atomic staging rename. Existing version directories are immutable and reverified. Failed installations never change selection. There is no global npm self-overwrite or sudo.
26
+
27
+ ## Durable selection and bounded discovery
28
+
29
+ `managed/update.json` has owner `MoRemote CLI updater v1`, enabled, active, bootstrap, optional previous/pending/pendingManual/activating/failed/manualRequired, lastCheck/nextCheck and a sanitized error code. Private atomic writes flush file and POSIX parent directory. A no-follow exclusive writer lock serializes installation and selection. A separate supervisor lock prevents two launchers. A stale marked lock is recoverable only after its PID is definitely absent; PID reuse conservatively reports busy, never authorizes signalling.
30
+
31
+ Automatic discovery requests bounded latest metadata once per six hours, persists the next deadline **before** network I/O, allows no redirects, has a20second request deadline and256KiB body cap.429/503 Retry-After can delay the original next check up to24hours; it never creates a renewed sliding deadline.404/unpublished, malformed identity and network failure preserve active selection and record a sanitized error until a later bounded attempt. Supervisor restart retains deadlines and failed-version suppression. Automatic selection accepts only strictly newer stable X.Y.Z versions; explicit update accepts exact semver including prereleases. No ranges, tags, URLs or alternate npm identities are accepted.
32
+
33
+ `auto-update --disable` writes a separate durable marked private opt-out even while another writer is staging/draining. Readers immediately report disabled. No queued candidate activates while disabled, including an explicit manual candidate; `auto-update --enable` resumes eligible queued work. An automatic pending candidate is cancelled when the writer is available; a concurrent installation may finish staging but cannot activate. Enabling never resets discovery deadlines or failed-version suppression. `status` distinguishes package bootstrap required, source-checkout manual mode, and the managed active/pending/previous/error/check facts.
34
+
35
+ ## Compatibility and activation
36
+
37
+ Every publish declares `moremote: {updateProtocol:1,journalSchema:1,wireProtocol:1}`. Both staging selection and the retained supervisor independently check this exact compatibility tuple. Missing/different compatibility remains pending with manualRequired and `UPDATE_MANUAL_COMPATIBILITY_REQUIRED`; it never drains or executes. Automatic-release validation also rejects another tuple. A compatible release MUST preserve all older retained versions' ability to read/write the same config/journal, mutation tombstones and wire lifecycle. A mere startup survival window cannot prove this property. Breaking storage/wire changes require a separately designed, owner-approved migration/release process; do not relabel an incompatible schema as1 or promise arbitrary downgrade safety. The existing FULL-sync journal, occurrence, revoke and no-replay contracts are unchanged.
38
+
39
+ A service points at `bin/moremote-service.js` inside the retained immutable bootstrap package. That bootstrap and its dependencies are never removed automatically. The supervisor starts active's runtime as a child with an OS parent-child IPC channel. It requests `moremote-drain`, never a PID kill. Runtime finishes its **whole existing cycle**, including in-flight journalled writes and receipts, then closes the SDK/journal and authenticated runtime ownership. A paused sleep wakes for drain and cannot start another cycle. Losing the parent IPC channel also drains. Only after exit can another runtime start.
40
+
41
+ After old exit, candidate readiness requires journal creation and acquired runtime ownership; ten seconds of process survival commits active/previous. A failure or30second missing-ready deadline first drains the candidate and then starts the last-known-good active version. The failed candidate is persisted and not retried automatically; explicit `update --version ... --yes` authorizes another attempt. An interrupted activating marker on supervisor restart selects old active and suppresses the uncertain candidate. No rollback replays an official operation. All version directories are retained; there is no automatic garbage collection.
42
+
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
+
45
+ ## Evidence entrypoints
46
+
47
+ `npm run check` exercises ordinary regression tests and compiles; `npm run smoke:upgrade` then packs two synthetic versions of the actual compiled package, installs both through real npm into isolated private prefixes, starts the production retained service entry (without registering any OS service), confirms runtime.version advances from9000.0.1 to9000.0.2, retains the old/bootstrap executable and performs a clean stop. It contacts only npm plus an intentionally unavailable localhost official endpoint, never everyday official data or cloud. It is explicit acceptance, not an install hook. CI includes the same smoke on macOS/Linux/Windows. Neither this specification nor test source claims those checks have been exercised.
48
+
49
+ 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
+
51
+ ## Official design references
52
+
53
+ - [Claude Code update behavior and package-manager boundaries](https://code.claude.com/docs/en/setup#update-claude-code): background checks, next-start activation, diagnostic visibility, opt-out; native versus Homebrew/WinGet/OS-package manager boundaries. This project borrows the owned-version/launcher boundary, not Claude's installer or global package-manager upgrade behavior. Our continuously running consumer needs an explicit cycle-safe handoff rather than a silent session restart.
54
+ - [npm trusted publishers](https://docs.npmjs.com/trusted-publishers/): an optional future authentication migration, not a prerequisite for the owner's existing organization publishing secret.
55
+ - [GitHub Node package publication](https://docs.github.com/en/actions/tutorials/publish-packages/publish-nodejs-packages): exact identity, scoped public access and build-before-publish/provenance. Existing `NPM_TOKEN` is available only to this selected public repository and exposed as `NODE_AUTH_TOKEN` only during its release publish step.
@@ -0,0 +1,211 @@
1
+ Copyright (c) 2025-present Mohamed Boudra
2
+
3
+ Portions of this software are licensed as follows:
4
+
5
+ * Third-party components incorporated into Paseo remain licensed under
6
+ the licenses provided by their respective copyright holders.
7
+ * Except for those third-party components, Paseo is licensed under the
8
+ Apache License, Version 2.0, reproduced below.
9
+
10
+
11
+ Apache License
12
+ Version 2.0, January 2004
13
+ http://www.apache.org/licenses/
14
+
15
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
16
+
17
+ 1. Definitions.
18
+
19
+ "License" shall mean the terms and conditions for use, reproduction,
20
+ and distribution as defined by Sections 1 through 9 of this document.
21
+
22
+ "Licensor" shall mean the copyright owner or entity authorized by
23
+ the copyright owner that is granting the License.
24
+
25
+ "Legal Entity" shall mean the union of the acting entity and all
26
+ other entities that control, are controlled by, or are under common
27
+ control with that entity. For the purposes of this definition,
28
+ "control" means (i) the power, direct or indirect, to cause the
29
+ direction or management of such entity, whether by contract or
30
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
31
+ outstanding shares, or (iii) beneficial ownership of such entity.
32
+
33
+ "You" (or "Your") shall mean an individual or Legal Entity
34
+ exercising permissions granted by this License.
35
+
36
+ "Source" form shall mean the preferred form for making modifications,
37
+ including but not limited to software source code, documentation
38
+ source, and configuration files.
39
+
40
+ "Object" form shall mean any form resulting from mechanical
41
+ transformation or translation of a Source form, including but
42
+ not limited to compiled object code, generated documentation,
43
+ and conversions to other media types.
44
+
45
+ "Work" shall mean the work of authorship, whether in Source or
46
+ Object form, made available under the License, as indicated by a
47
+ copyright notice that is included in or attached to the work
48
+ (an example is provided in the Appendix below).
49
+
50
+ "Derivative Works" shall mean any work, whether in Source or Object
51
+ form, that is based on (or derived from) the Work and for which the
52
+ editorial revisions, annotations, elaborations, or other modifications
53
+ represent, as a whole, an original work of authorship. For the purposes
54
+ of this License, Derivative Works shall not include works that remain
55
+ separable from, or merely link (or bind by name) to the interfaces of,
56
+ the Work and Derivative Works thereof.
57
+
58
+ "Contribution" shall mean any work of authorship, including
59
+ the original version of the Work and any modifications or additions
60
+ to that Work or Derivative Works thereof, that is intentionally
61
+ submitted to Licensor for inclusion in the Work by the copyright owner
62
+ or by an individual or Legal Entity authorized to submit on behalf of
63
+ the copyright owner. For the purposes of this definition, "submitted"
64
+ means any form of electronic, verbal, or written communication sent
65
+ to the Licensor or its representatives, including but not limited to
66
+ communication on electronic mailing lists, source code control systems,
67
+ and issue tracking systems that are managed by, or on behalf of, the
68
+ Licensor for the purpose of discussing and improving the Work, but
69
+ excluding communication that is conspicuously marked or otherwise
70
+ designated in writing by the copyright owner as "Not a Contribution."
71
+
72
+ "Contributor" shall mean Licensor and any individual or Legal Entity
73
+ on behalf of whom a Contribution has been received by Licensor and
74
+ subsequently incorporated within the Work.
75
+
76
+ 2. Grant of Copyright License. Subject to the terms and conditions of
77
+ this License, each Contributor hereby grants to You a perpetual,
78
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
79
+ copyright license to reproduce, prepare Derivative Works of,
80
+ publicly display, publicly perform, sublicense, and distribute the
81
+ Work and such Derivative Works in Source or Object form.
82
+
83
+ 3. Grant of Patent License. Subject to the terms and conditions of
84
+ this License, each Contributor hereby grants to You a perpetual,
85
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
86
+ (except as stated in this section) patent license to make, have made,
87
+ use, offer to sell, sell, import, and otherwise transfer the Work,
88
+ where such license applies only to those patent claims licensable
89
+ by such Contributor that are necessarily infringed by their
90
+ Contribution(s) alone or by combination of their Contribution(s)
91
+ with the Work to which such Contribution(s) was submitted. If You
92
+ institute patent litigation against any entity (including a
93
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
94
+ or a Contribution incorporated within the Work constitutes direct
95
+ or contributory patent infringement, then any patent licenses
96
+ granted to You under this License for that Work shall terminate
97
+ as of the date such litigation is filed.
98
+
99
+ 4. Redistribution. You may reproduce and distribute copies of the
100
+ Work or Derivative Works thereof in any medium, with or without
101
+ modifications, and in Source or Object form, provided that You
102
+ meet the following conditions:
103
+
104
+ (a) You must give any other recipients of the Work or
105
+ Derivative Works a copy of this License; and
106
+
107
+ (b) You must cause any modified files to carry prominent notices
108
+ stating that You changed the files; and
109
+
110
+ (c) You must retain, in the Source form of any Derivative Works
111
+ that You distribute, all copyright, patent, trademark, and
112
+ attribution notices from the Source form of the Work,
113
+ excluding those notices that do not pertain to any part of
114
+ the Derivative Works; and
115
+
116
+ (d) If the Work includes a "NOTICE" text file as part of its
117
+ distribution, then any Derivative Works that You distribute must
118
+ include a readable copy of the attribution notices contained
119
+ within such NOTICE file, excluding those notices that do not
120
+ pertain to any part of the Derivative Works, in at least one
121
+ of the following places: within a NOTICE text file distributed
122
+ as part of the Derivative Works; within the Source form or
123
+ documentation, if provided along with the Derivative Works; or,
124
+ within a display generated by the Derivative Works, if and
125
+ wherever such third-party notices normally appear. The contents
126
+ of the NOTICE file are for informational purposes only and
127
+ do not modify the License. You may add Your own attribution
128
+ notices within Derivative Works that You distribute, alongside
129
+ or as an addendum to the NOTICE text from the Work, provided
130
+ that such additional attribution notices cannot be construed
131
+ as modifying the License.
132
+
133
+ You may add Your own copyright statement to Your modifications and
134
+ may provide additional or different license terms and conditions
135
+ for use, reproduction, or distribution of Your modifications, or
136
+ for any such Derivative Works as a whole, provided Your use,
137
+ reproduction, and distribution of the Work otherwise complies with
138
+ the conditions stated in this License.
139
+
140
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
141
+ any Contribution intentionally submitted for inclusion in the Work
142
+ by You to the Licensor shall be under the terms and conditions of
143
+ this License, without any additional terms or conditions.
144
+ Notwithstanding the above, nothing herein shall supersede or modify
145
+ the terms of any separate license agreement you may have executed
146
+ with Licensor regarding such Contributions.
147
+
148
+ 6. Trademarks. This License does not grant permission to use the trade
149
+ names, trademarks, service marks, or product names of the Licensor,
150
+ except as required for reasonable and customary use in describing the
151
+ origin of the Work and reproducing the content of the NOTICE file.
152
+
153
+ 7. Disclaimer of Warranty. Unless required by applicable law or
154
+ agreed to in writing, Licensor provides the Work (and each
155
+ Contributor provides its Contributions) on an "AS IS" BASIS,
156
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
157
+ implied, including, without limitation, any warranties or conditions
158
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
159
+ PARTICULAR PURPOSE. You are solely responsible for determining the
160
+ appropriateness of using or redistributing the Work and assume any
161
+ risks associated with Your exercise of permissions under this License.
162
+
163
+ 8. Limitation of Liability. In no event and under no legal theory,
164
+ whether in tort (including negligence), contract, or otherwise,
165
+ unless required by applicable law (such as deliberate and grossly
166
+ negligent acts) or agreed to in writing, shall any Contributor be
167
+ liable to You for damages, including any direct, indirect, special,
168
+ incidental, or consequential damages of any character arising as a
169
+ result of this License or out of the use or inability to use the
170
+ Work (including but not limited to damages for loss of goodwill,
171
+ work stoppage, computer failure or malfunction, or any and all
172
+ other commercial damages or losses), even if such Contributor
173
+ has been advised of the possibility of such damages.
174
+
175
+ 9. Accepting Warranty or Additional Liability. While redistributing
176
+ the Work or Derivative Works thereof, You may choose to offer,
177
+ and charge a fee for, acceptance of support, warranty, indemnity,
178
+ or other liability obligations and/or rights consistent with this
179
+ License. However, in accepting such obligations, You may act only
180
+ on Your own behalf and on Your sole responsibility, not on behalf
181
+ of any other Contributor, and only if You agree to indemnify,
182
+ defend, and hold each Contributor harmless for any liability
183
+ incurred by, or claims asserted against, such Contributor by reason
184
+ of your accepting any such warranty or additional liability.
185
+
186
+ END OF TERMS AND CONDITIONS
187
+
188
+ APPENDIX: How to apply the Apache License to your work.
189
+
190
+ To apply the Apache License to your work, attach the following
191
+ boilerplate notice, with the fields enclosed by brackets "[]"
192
+ replaced with your own identifying information. (Don't include
193
+ the brackets!) The text should be enclosed in the appropriate
194
+ comment syntax for the file format. We also recommend that a
195
+ file or class name and description of purpose be included on the
196
+ same "printed page" as the copyright notice for easier
197
+ identification within third-party archives.
198
+
199
+ Copyright [yyyy] [name of copyright owner]
200
+
201
+ Licensed under the Apache License, Version 2.0 (the "License");
202
+ you may not use this file except in compliance with the License.
203
+ You may obtain a copy of the License at
204
+
205
+ http://www.apache.org/licenses/LICENSE-2.0
206
+
207
+ Unless required by applicable law or agreed to in writing, software
208
+ distributed under the License is distributed on an "AS IS" BASIS,
209
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
210
+ See the License for the specific language governing permissions and
211
+ limitations under the License.
package/package.json CHANGED
@@ -1,6 +1,39 @@
1
1
  {
2
2
  "name": "@moxuli/moremote",
3
- "version": "0.0.0-stage",
4
- "stub": true,
5
- "description": "Temporary package placeholder for staged publishing"
6
- }
3
+ "version": "0.1.1",
4
+ "description": "Optional encrypted notification and scoped-action companion for Paseo",
5
+ "license": "Apache-2.0",
6
+ "type": "module",
7
+ "repository": {"type": "git", "url": "git+https://github.com/moxuli/moremote-cli.git"},
8
+ "homepage": "https://github.com/moxuli/moremote-cli#readme",
9
+ "bugs": {"url": "https://github.com/moxuli/moremote-cli/issues"},
10
+ "publishConfig": {"access": "public", "registry": "https://registry.npmjs.org"},
11
+ "moremote": {"updateProtocol": 1, "journalSchema": 1, "wireProtocol": 1},
12
+ "files": ["bin", "dist", "docs", "vectors", "licenses", "LICENSE", "NOTICE", "README.md"],
13
+ "engines": {
14
+ "node": ">=24.13.0 <25"
15
+ },
16
+ "bin": {
17
+ "moremote-cli": "bin/moremote-cli.js"
18
+ },
19
+ "scripts": {
20
+ "build": "tsc -p tsconfig.json",
21
+ "typecheck": "tsc --noEmit",
22
+ "test": "node --import tsx --test tests/*.test.ts",
23
+ "check": "npm run typecheck && npm test && npm run build",
24
+ "smoke:upgrade": "node scripts/smoke-upgrade.mjs"
25
+ },
26
+ "dependencies": {
27
+ "@getpaseo/client": "0.15.3",
28
+ "@getpaseo/protocol": "0.15.3",
29
+ "qrcode": "1.5.4"
30
+ },
31
+ "devDependencies": {
32
+ "@types/node": "24.10.1",
33
+ "@types/qrcode": "1.5.6",
34
+ "@types/ws": "8.18.1",
35
+ "tsx": "4.20.6",
36
+ "typescript": "5.9.3",
37
+ "ws": "8.20.0"
38
+ }
39
+ }
@@ -0,0 +1,6 @@
1
+ {
2
+ "description": "Synthetic public bearer framing vector; never use as a credential",
3
+ "bearer": "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA",
4
+ "textSha256Hex": "0f007385b6f9d4b7eeb2748605afe1a984a0a3bfa3f014d09e2a784ce9e5cd1a",
5
+ "decodedBytesSha256Hex": "66687aadf862bd776c8fc18b8e9f8e20089714856ee233b3902a591d0d5f2925"
6
+ }
@@ -0,0 +1,24 @@
1
+ {
2
+ "description": "Synthetic public cross-runtime v1 vector; fixed key/nonce are test data only",
3
+ "rootKeyHex": "1111111111111111111111111111111111111111111111111111111111111111",
4
+ "derivedKeyHex": "802882d6da6a89e409c5ba0c40020bc7f6606522bbe2515394040e6e3b9e81ab",
5
+ "aad": "[1,\"11111111-1111-4111-8111-111111111111\",\"22222222-2222-4222-8222-222222222222\",\"command\",1800000000000,1800000300000]",
6
+ "info": "[1,\"11111111-1111-4111-8111-111111111111\",\"command\"]",
7
+ "plaintext": "{\"type\":\"send\",\"agentId\":\"synthetic-agent\",\"text\":\"Hello 墨序里 👋\\n第二行\",\"messageId\":\"22222222-2222-4222-8222-222222222222\"}",
8
+ "payload": {
9
+ "type": "send",
10
+ "agentId": "synthetic-agent",
11
+ "text": "Hello 墨序里 👋\n第二行",
12
+ "messageId": "22222222-2222-4222-8222-222222222222"
13
+ },
14
+ "envelope": {
15
+ "version": 1,
16
+ "pairId": "11111111-1111-4111-8111-111111111111",
17
+ "id": "22222222-2222-4222-8222-222222222222",
18
+ "channel": "command",
19
+ "issuedAt": 1800000000000,
20
+ "expiresAt": 1800000300000,
21
+ "nonce": "IiIiIiIiIiIiIiIi",
22
+ "ciphertext": "qaN99ylekUe9PLLoupmXW_FWnTZ16hKsaEzrpitti-W51rEiYMu9440JW23MAwp9X7PS6mSjLSWNm_177nj05plEdAPpIY206C26agcpB_LD6S7gEiwgPCMT6TK-9y6OEXSnai21uwhAeC55CxW9cWjeMDFrBlI-IdbMIeeasBOYvZsTijpgaGHCOwSkim79a4NkJLvnYA"
23
+ }
24
+ }