@oddington/cli 0.1.91 → 0.1.93
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 +20 -5
- package/dist/os.js +465 -437
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -70,6 +70,20 @@ containment. Setup and testing only read provider state; routine calls change
|
|
|
70
70
|
Dropbox immediately, independently of publication. Disconnect prevents new
|
|
71
71
|
delivery but does not revoke an already delivered token.
|
|
72
72
|
|
|
73
|
+
Edit an enabled Dropbox connection without repeating OAuth:
|
|
74
|
+
|
|
75
|
+
```sh
|
|
76
|
+
os connection update --workspace example --connection dropbox/business --name documents --root /
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
Use the current `provider/name`. Supply `--name`, `--root`, or both; omitted
|
|
80
|
+
fields keep their values. `/` means Dropbox's exact empty API root; other roots
|
|
81
|
+
must be existing absolute Dropbox folder paths. Without `--workspace`, update
|
|
82
|
+
uses your active workspace. Root changes verify access before an atomic edit and
|
|
83
|
+
invalidate earlier OS runtime authority. Name-only edits let started work
|
|
84
|
+
continue. The old name stops resolving: deliberately update declarations in
|
|
85
|
+
apps and routines to use the new name. App Folder storage cannot be edited here.
|
|
86
|
+
|
|
73
87
|
Dropbox storage backs the OS Files capability with a separate dedicated folder:
|
|
74
88
|
|
|
75
89
|
```sh
|
|
@@ -85,8 +99,8 @@ not register applications or handle OS app keys. Missing service setup names
|
|
|
85
99
|
either Dropbox connection authorization or Dropbox storage authorization.
|
|
86
100
|
|
|
87
101
|
The old `--access full-dropbox --root ...` connection flag remains a compatibility
|
|
88
|
-
alias.
|
|
89
|
-
points to the explicit Files storage command
|
|
102
|
+
alias. Omitting `--root` creates a connection at Dropbox's root. The
|
|
103
|
+
`--access app-folder` option points to the explicit Files storage command.
|
|
90
104
|
Older installed clients retain their explicit authorization semantics on the API.
|
|
91
105
|
Deployment operators must complete the credential-name cutover in
|
|
92
106
|
`server/dropbox-authorization-rollout.md` before deploying this server version.
|
|
@@ -783,14 +797,15 @@ there is no direct customer-item-to-call link in this slice. The [SDK example](h
|
|
|
783
797
|
shows a typed catch. Shared summaries and ordinary command JSON exclude answer
|
|
784
798
|
samples, prompts, reasoning and provider logs.
|
|
785
799
|
|
|
786
|
-
Keep an exact stable `@oddington/sdk` 0.1.x patch
|
|
800
|
+
Keep an exact stable `@oddington/sdk` 0.1.x patch supported by remote routines in root
|
|
787
801
|
`devDependencies`, with its declaration, lock and installed package agreeing.
|
|
788
802
|
Use compatible Node, the selected private ESM manifest and the shared frozen
|
|
789
803
|
lock. OS verifies only the selected installed graph, stages its confined bytes
|
|
790
804
|
and builds the same
|
|
791
805
|
executable unit used by deployment, preserving declared assets and SDK ownership.
|
|
792
|
-
Missing build tools,
|
|
793
|
-
packages report unavailable before business work.
|
|
806
|
+
Missing build tools, SDK features not yet available to remote routines, invalid
|
|
807
|
+
metadata or stale/unavailable packages report unavailable before business work.
|
|
808
|
+
The check names remote readiness separately from local readiness. Local Python dependency
|
|
794
809
|
provisioning is unsupported. Launch never repairs the workspace or falls back
|
|
795
810
|
from a broken modern manifest to legacy execution.
|
|
796
811
|
|