@oddington/cli 0.1.70 → 0.1.71

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 (3) hide show
  1. package/README.md +37 -2
  2. package/dist/os.js +402 -358
  3. package/package.json +2 -2
package/README.md CHANGED
@@ -26,6 +26,17 @@ If you have several workspaces, use ↑/↓ to highlight one and Enter to select
26
26
  Ctrl+C cancels without storing a new login. A single workspace is selected
27
27
  automatically; plain terminals retain the numbered-input fallback.
28
28
 
29
+ After workspace selection, login saves that workspace's repository locations
30
+ with your secure session. `os data push` uses those saved settings and ordinary
31
+ Git, without calling the OS API. Existing `os connection target list`, `add` and
32
+ `disable` commands, and `os repository add`, also save the selected workspace's
33
+ current locations. Until those settings are reloaded, the saved destination
34
+ remains in use; each push shows where it is going, and Git enforces current access
35
+ and branch rules.
36
+ Missing repository settings do not invalidate your login. Push stops with a hint
37
+ for the existing Git target and data repository commands; it never loads settings
38
+ automatically or requires a new sign-in just for repository setup.
39
+
29
40
  Run `os --help` or add `--help` to any command for the full command list.
30
41
  Commands print readable output by default. Add `--json` when another program
31
42
  will consume the result.
@@ -95,6 +106,30 @@ OS checks its collection schemas, saves the binding and starts preparing the dat
95
106
  The result reports `preparing` or `ready`; repeating the same command resumes setup.
96
107
  Configure the Git repository separately through Connections.
97
108
 
109
+ ## Push local data
110
+
111
+ ```sh
112
+ os data push project-management
113
+ os routine run supplier-invoices --input january.json --push
114
+ ```
115
+
116
+ `os data push` commits current file changes inside the selected data directory and
117
+ pushes them to its configured Git destination. It includes manual edits, schemas,
118
+ new files and deletions. Uncommitted files outside that directory stay untouched,
119
+ including staged code. With one matching data repository, you can omit its name.
120
+
121
+ Existing local commits are part of a normal Git push. If any change files outside
122
+ the selected data directory, OS lists them and asks for confirmation before
123
+ committing. Declining leaves your files and staging unchanged. With no data
124
+ changes to send, it does nothing. Use your ordinary Git identity and credentials;
125
+ your OS login saves the configured destination during workspace selection.
126
+
127
+ `--push` runs only after a successful local routine with one declared writable
128
+ data repository. It includes earlier local edits in that directory. If pushing
129
+ fails, the routine's result and local data commit are kept: retry `os data push`,
130
+ without rerunning the routine. Remote conflicts require normal Git recovery.
131
+ `--json` returns one structured outcome and never asks for confirmation.
132
+
98
133
  ## Repository schema types
99
134
 
100
135
  Inside a TypeScript code repository with a GitHub origin and named branch, run:
@@ -473,7 +508,7 @@ and frozen runtime graph; unrelated tooling and untouched legacy routines do
473
508
  not enlarge or invalidate it. The empty graph needs no customer dependency
474
509
  installation during deployment. Supported runtime packages are frozen registry
475
510
  imports; customer scripts, build hooks, aliases and SDK replacement are refused.
476
- See [frozen source admission](src/routine-deployment-source.md) for the bounded
511
+ See [frozen source validation](src/routine-deployment-source.md) for the bounded
477
512
  import and dependency contract.
478
513
 
479
514
  The command reports bounded deployment facts and safe failures. JSON stdout is
@@ -662,7 +697,7 @@ there is no direct customer-item-to-call link in this slice. The [SDK example](h
662
697
  shows a typed catch. Shared summaries and ordinary command JSON exclude answer
663
698
  samples, prompts, reasoning and provider logs.
664
699
 
665
- Keep an exact stable `@oddington/sdk` 0.1.x patch through 0.1.40 in root
700
+ Keep an exact stable `@oddington/sdk` 0.1.x patch through 0.1.41 in root
666
701
  `devDependencies`, with its declaration, lock and installed package agreeing.
667
702
  Use compatible Node, the selected private ESM manifest and the shared frozen
668
703
  lock. OS verifies only the selected installed graph, stages its confined bytes