@jarel/myskills 0.1.0-beta.4 → 0.1.0-beta.6
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/LICENSE +202 -0
- package/README.md +138 -19
- package/dist/index.js +18184 -3386
- package/package.json +7 -5
package/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
package/README.md
CHANGED
|
@@ -25,17 +25,19 @@ Responsibilities:
|
|
|
25
25
|
- install/export/update/rollback packages
|
|
26
26
|
- submit drafts
|
|
27
27
|
- support maintainer/admin workflows through role-gated API calls
|
|
28
|
+
- enroll a personal Codex workspace and execute approved updates with an explicit companion command
|
|
28
29
|
- inspect an explicitly selected local Codex profile with a read-only metadata observation or health report
|
|
30
|
+
- create a dry-run-only work/team bootstrap plan from explicit approved roots and skill selectors
|
|
29
31
|
|
|
30
32
|
CLI tokens should be stored in the platform secret store where possible.
|
|
31
33
|
|
|
32
34
|
## Current Slice
|
|
33
35
|
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
36
|
+
This document describes the beta.6 CLI candidate. Use a CLI built from the same
|
|
37
|
+
release as the registry for managed updates and Codex workspace commands. The
|
|
38
|
+
beta.2 visibility compatibility shims remain available for existing clients.
|
|
39
|
+
Source versions and npm publication are separate from hosted deployment; the
|
|
40
|
+
API and web expose their deployed version and commit at `/version.json`.
|
|
39
41
|
|
|
40
42
|
### Beta.3 breaking security changes
|
|
41
43
|
|
|
@@ -81,6 +83,7 @@ myskills config get api-url
|
|
|
81
83
|
myskills config set api-url <url>
|
|
82
84
|
myskills config reset api-url
|
|
83
85
|
myskills config list
|
|
86
|
+
myskills bootstrap codex --dry-run --profile work --context <file> [--work-source-root <dir>] [--shared-source-root <dir>] --live-root <dir> --include-slug <slug> [--include-slug <slug>] --output <report.json>
|
|
84
87
|
myskills submit --path <file-directory-or-zip> [--api-url <url>] [--token <token>]
|
|
85
88
|
myskills review submissions [--api-url <url>] [--token <token>]
|
|
86
89
|
myskills review bundle <submission-id> [--platform <name>] [--output <file>] [--api-url <url>] [--token <token>]
|
|
@@ -111,6 +114,12 @@ myskills install <skill-slug> [--version <version>] [--platform <platform>] [--d
|
|
|
111
114
|
myskills list [--dir <install-root>]
|
|
112
115
|
myskills update [skill-slug] [--version <version>] [--platform <platform>] [--dir <install-root>]
|
|
113
116
|
myskills rollback <skill-slug> [--dir <install-root>]
|
|
117
|
+
myskills codex enroll --workspace <absolute-dir> --architecture-id <id> --environment-id <id> --profile-id <id> [--name <name>]
|
|
118
|
+
myskills codex observe --workspace <absolute-dir> [--upload] [--json]
|
|
119
|
+
myskills install <skill-slug> --version <version> --workspace <absolute-dir>
|
|
120
|
+
myskills update [skill-slug] [--version <version>] --workspace <absolute-dir>
|
|
121
|
+
myskills rollback <skill-slug> --workspace <absolute-dir>
|
|
122
|
+
myskills companion run-once --workspace <absolute-dir> --holder <name>
|
|
114
123
|
myskills token create --name <name> --scope <scope> [--scope <scope>]
|
|
115
124
|
myskills token list
|
|
116
125
|
myskills token revoke <token-id>
|
|
@@ -144,11 +153,11 @@ this command.
|
|
|
144
153
|
|
|
145
154
|
`architectures plan` and `architectures dry-run` accept a bounded observed
|
|
146
155
|
fixture and return a dry-run plan. The fixture is not an implicit target and
|
|
147
|
-
the command does not apply changes.
|
|
156
|
+
the command does not apply changes. General architecture graph execution remains
|
|
148
157
|
fixture-only, even though its API persistence and recovery/rollback evidence
|
|
149
|
-
can be stored in Postgres.
|
|
150
|
-
|
|
151
|
-
|
|
158
|
+
can be stored in Postgres. The separate Codex workspace and managed skill
|
|
159
|
+
operation commands below support one explicit filesystem installation path.
|
|
160
|
+
Each bounded architecture fixture run allows at most 500 steps and 2,004 append-only
|
|
152
161
|
receipts: a 1,002-receipt max-step lifecycle, one full apply/verify retry, and
|
|
153
162
|
two recovery/terminal receipts. Further retries require a new bounded run.
|
|
154
163
|
|
|
@@ -158,33 +167,143 @@ Those operations require the server's current-revision, organization-policy,
|
|
|
158
167
|
membership, exact-release, limit, idempotency, and MFA checks. This CLI does
|
|
159
168
|
not expose a second policy implementation or write command for them.
|
|
160
169
|
|
|
161
|
-
## Published And
|
|
170
|
+
## Published CLI And Local Builds
|
|
162
171
|
|
|
163
|
-
The
|
|
172
|
+
The published beta channel is installed with:
|
|
164
173
|
|
|
165
174
|
```bash
|
|
166
|
-
npm install -g @jarel/myskills@
|
|
175
|
+
npm install -g @jarel/myskills@beta
|
|
167
176
|
myskills --version
|
|
168
177
|
myskills login
|
|
169
178
|
```
|
|
170
179
|
|
|
171
|
-
|
|
180
|
+
The expected candidate version is `0.1.0-beta.6`. It includes the beta.5 managed
|
|
181
|
+
update and personal Codex workspace commands plus the dry-run-only work/team
|
|
182
|
+
bootstrap planner. To test repository changes before release, build and run them
|
|
183
|
+
locally:
|
|
172
184
|
|
|
173
185
|
```bash
|
|
174
|
-
npm
|
|
186
|
+
npm ci
|
|
187
|
+
npm run build
|
|
188
|
+
node apps/cli/dist/index.js --version
|
|
189
|
+
node apps/cli/dist/index.js login
|
|
190
|
+
npm pack -w @jarel/myskills
|
|
175
191
|
```
|
|
176
192
|
|
|
177
|
-
|
|
193
|
+
Use the resulting tarball for a fresh isolated installation, or run the bundle
|
|
194
|
+
directly. The release gate verifies the packed executable and Apache license.
|
|
195
|
+
Public npm publication is a separate release step.
|
|
178
196
|
|
|
179
197
|
`validate`, `scan`, and `submit` accept a manifest file, package directory, or local `.zip` package. `login` prompts for the API URL when one is not supplied; the default is the local API at `http://localhost:3001`, and custom hosted URLs can be entered manually. Successful login stores the selected API URL in local CLI config so later commands can omit `--api-url`. API URL resolution is `--api-url`, then `MYSKILLS_API_URL`, then saved config, then `http://localhost:3001`.
|
|
180
198
|
|
|
181
|
-
`login` supports an email/password session flow and an API-key flow.
|
|
199
|
+
`login` supports an email/password session flow and an API-key flow. Password
|
|
200
|
+
login handles MFA challenges and stores the verified session token. API-key
|
|
201
|
+
login validates the key with `/v1/me`. Token resolution is `--token`, then
|
|
202
|
+
`MYSKILLS_TOKEN`, then the stored token. The default store uses the platform
|
|
203
|
+
credential store through `@napi-rs/keyring`. Credential-store failures are
|
|
204
|
+
reported; a failed write does not silently store the credential in a file.
|
|
205
|
+
An existing legacy file credential can be read when the keyring entry is
|
|
206
|
+
confirmed absent. Explicit `MYSKILLS_TOKEN_STORE=file` or `MYSKILLS_TOKEN_FILE`
|
|
207
|
+
selects file storage with user-only permissions. A successful keyring write
|
|
208
|
+
clears the obsolete file entry.
|
|
209
|
+
|
|
210
|
+
`auth status` validates the token without printing it. `logout` revokes stored
|
|
211
|
+
sessions and clears local credentials. If a malformed keyring entry prevents
|
|
212
|
+
revocation, logout attempts local deletion and reports that remote revocation
|
|
213
|
+
is unconfirmed. It reports deletion failures. Stored API tokens are removed
|
|
214
|
+
locally and must be revoked with `token revoke`. Malformed file-store JSON
|
|
215
|
+
requires repair or removal of that file; other stored accounts are not silently
|
|
216
|
+
discarded.
|
|
182
217
|
|
|
183
218
|
`config get api-url`, `config set api-url <url>`, `config reset api-url`, and `config list` manage the saved API URL. `doctor` checks the CLI version, Node version, resolved API URL, `/health`, auth status, token-store backend, install-directory writability, and `/v1/capabilities`. If the CLI is pointed at the web app instead of the API, or a newer command is sent to an older server, command errors include concrete next steps and `--json` returns structured error codes.
|
|
184
219
|
|
|
185
|
-
`
|
|
186
|
-
|
|
187
|
-
|
|
220
|
+
`bootstrap codex --dry-run` is a work/team-only local planner. It requires an
|
|
221
|
+
explicit `work` context, a normalized HTTPS target origin, stable target
|
|
222
|
+
instance/workspace/actor identifiers, explicit source and target trust
|
|
223
|
+
compartments (`work`, `shared`, or `work+shared` for sources, and `work-team`
|
|
224
|
+
for the target), typed `work` and/or `shared` source roots, a target root, and
|
|
225
|
+
a positive `--include-slug` allowlist. The context must approve the computed
|
|
226
|
+
source-root type/digests and target-root digest. Personal, consumer, public,
|
|
227
|
+
and unclassified sources are rejected, and candidates are never selected by
|
|
228
|
+
implicit inventory discovery. A plan accepts at most eight selected candidates;
|
|
229
|
+
each candidate snapshot accepts at most 1,000 entries and 32 nested directory
|
|
230
|
+
levels. A one-skill work-owned canary is supported.
|
|
231
|
+
|
|
232
|
+
The context JSON must include `profile: "work"`, `targetOrigin`,
|
|
233
|
+
`instanceId`, one `tenantId` or `workspaceId`, `actorId`, the canonical trust
|
|
234
|
+
compartments, `approvedSourceRoots` entries of `{type, identityDigest}`, and
|
|
235
|
+
`approvedTargetRootIdentityDigest`.
|
|
236
|
+
|
|
237
|
+
The planner reads selected source and target content without network or
|
|
238
|
+
registry access. It opens each selected tree through a bootstrap-owned secure
|
|
239
|
+
snapshot reader, then hashes, parses, scans, and reports only those held bytes.
|
|
240
|
+
It writes only the explicitly requested new private report (`0600`) under a
|
|
241
|
+
user-controlled private parent. Reserved package manifests remain strict:
|
|
242
|
+
invalid or multiple manifests fail closed, and no metadata is relocated. The
|
|
243
|
+
full report contains the work binding, approved root digests, owning package
|
|
244
|
+
contract identifiers, candidate content identities, execution identities, the
|
|
245
|
+
exact target precondition (`absent` or `present-identical` with its expected
|
|
246
|
+
artifact identity), and private snapshots. Terminal output is a redacted DTO
|
|
247
|
+
with counts and digests; it does not contain paths, candidate names, inventory,
|
|
248
|
+
or private identifiers.
|
|
249
|
+
There is no apply, publishing, adoption, or target-write mode in this command.
|
|
250
|
+
`ready` means that the held snapshot passed deterministic checks only. It is
|
|
251
|
+
not approval to apply. Sensitive configuration and credential paths are
|
|
252
|
+
excluded before content enters the report, and heuristic scan-clean never
|
|
253
|
+
replaces explicit human content review. Any future executor must repeat the
|
|
254
|
+
retained source/target identity check immediately before its first write
|
|
255
|
+
(compare-and-swap) and require that review at that boundary.
|
|
256
|
+
|
|
257
|
+
`validate`, `scan`, and `submit` read one bounded snapshot of the local package.
|
|
258
|
+
`submit` sends those same validated and scanned text entries for directory and
|
|
259
|
+
ZIP inputs. Authors can inspect and withdraw submissions; maintainers fetch the
|
|
260
|
+
reviewed artifact and approval hash before approving, requesting changes,
|
|
261
|
+
rejecting, or publishing it. The browser shows review reasons and scan findings.
|
|
262
|
+
Corrections create another immutable version.
|
|
263
|
+
|
|
264
|
+
Published artifacts remain immutable. `skills edit` changes metadata;
|
|
265
|
+
`releases deprecate`, `unpublish`, `revoke`, `restore`, and `delete` change
|
|
266
|
+
server-owned lifecycle state. Deprecated releases remain installable. Hidden,
|
|
267
|
+
revoked, archived, or deleted releases cannot be installed or exported.
|
|
268
|
+
`export` verifies artifact size and SHA-256 before writing normalized paths.
|
|
269
|
+
|
|
270
|
+
`install`, `update`, and `rollback` share an exclusive install-root lock and
|
|
271
|
+
verify package bytes and current eligibility before promotion. Updates retain
|
|
272
|
+
a verified rollback snapshot. Interrupted transactions preserve unknown or
|
|
273
|
+
edited local bytes for investigation. Each installation binds the API origin
|
|
274
|
+
and registry instance ID. Legacy records without that identity are not adopted
|
|
275
|
+
automatically: keep their files as a backup, review the source, and install into
|
|
276
|
+
a new root. A registry change requires a separate root.
|
|
277
|
+
|
|
278
|
+
Local package intake, install, export, and rollback support macOS and Linux.
|
|
279
|
+
No-follow payload reads and writes, private staging directories, and drift
|
|
280
|
+
checks protect these operations. They do not isolate the workspace from a
|
|
281
|
+
hostile process already running as the same OS user. Other operating systems
|
|
282
|
+
can use the API's portable buffer upload path; native Windows filesystem
|
|
283
|
+
installation is unsupported.
|
|
284
|
+
|
|
285
|
+
### Personal Codex workspace
|
|
286
|
+
|
|
287
|
+
Create a personal architecture in the browser and note its architecture,
|
|
288
|
+
environment, and profile IDs. Enable MFA and sign in with a password session.
|
|
289
|
+
Enroll an existing absolute workspace directory using the command above.
|
|
290
|
+
Enrollment creates a user-owned target, grants consent, and stores a local
|
|
291
|
+
binding. A fresh workspace cannot attach to an existing target ID; that option
|
|
292
|
+
only confirms or resumes its existing local binding.
|
|
293
|
+
|
|
294
|
+
Use `--workspace` for all managed writes. Skills are installed under
|
|
295
|
+
`.agents/skills`, and records stay under `.myskills-app` in that workspace.
|
|
296
|
+
The CLI checks Codex compatibility and valid `SKILL.md` YAML frontmatter with a
|
|
297
|
+
matching name and text description. `--dir` cannot bypass an enrolled workspace's
|
|
298
|
+
binding. Team-shared skills can be installed when your account can read them;
|
|
299
|
+
team-owned execution targets are outside this adapter's beta scope.
|
|
300
|
+
|
|
301
|
+
`codex observe --upload` records verified filesystem state. Confirm separately
|
|
302
|
+
that Codex loaded the skill. To process one browser-queued update, supply a
|
|
303
|
+
separate token with `skills:read` and `targets:execute` through `MYSKILLS_TOKEN`
|
|
304
|
+
and run `companion run-once`. This command checks current authorization, consent,
|
|
305
|
+
policy, lease, and exact release identity. It does not start a background daemon.
|
|
306
|
+
Browser/device login and additional provider install adapters remain planned.
|
|
188
307
|
|
|
189
308
|
To change skill visibility, use the canonical `myskills sharing set
|
|
190
309
|
<skill-slug> --visibility <scope>` command. It accepts either
|