@oddington/cli 0.1.60 → 0.1.62

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 +20 -9
  2. package/dist/os.js +263 -259
  3. package/package.json +2 -2
package/README.md CHANGED
@@ -599,9 +599,18 @@ provider connections retain their normal network and authority requirements;
599
599
  local execution may contact OS or providers.
600
600
 
601
601
  For modern local execution, install the workspace separately with Bun 1.3.14.
602
- Keep `@oddington/sdk` exactly 0.1.32 in root `devDependencies`, compatible Node,
603
- the selected private ESM manifest and the shared frozen lock. OS verifies only
604
- the selected installed graph, stages its confined bytes and builds the same
602
+ For a failed local Run, the terminal and JSON result identify its failed step
603
+ and known SDK error. Device-local `~/.os/<workspace>/runs/<run-id>/execution.json`
604
+ retains redacted exception messages, stacks, causes and failed OS operations.
605
+ Those details are not returned through app summaries. Use SDK 0.1.34 and CLI
606
+ 0.1.62 for this evidence; updating only the CLI does not replace the SDK frozen
607
+ into a customer routine or an earlier saved Run.
608
+
609
+ Keep an exact stable `@oddington/sdk` 0.1.x patch through 0.1.34 in root
610
+ `devDependencies`, with its declaration, lock and installed package agreeing.
611
+ Use compatible Node, the selected private ESM manifest and the shared frozen
612
+ lock. OS verifies only the selected installed graph, stages its confined bytes
613
+ and builds the same
605
614
  executable unit used by deployment, preserving declared assets and SDK ownership.
606
615
  Missing build tools, incompatible SDK, invalid metadata or stale/unavailable
607
616
  packages report unavailable before business work. Local Python dependency
@@ -658,12 +667,14 @@ returns their captured identities in `deleted`, and advances subsequent run
658
667
  reads to the exact prepared version. Files and durable Source uses remain
659
668
  retained. Deleted paths are sealed as absent: recreating one before
660
669
  `os routine publish <run>` invalidates publication before effects.
661
- Later publication rechecks the complete group at its captured base, applies one
662
- exact commit and waits for its exact hosted index. Interrupted Git or index
670
+ Later publication sends the retained group once to the guarded writer, which
671
+ validates its captured intent against the current authoritative head, applies
672
+ one ordinary commit and waits for its exact hosted index. Interrupted Git or index
663
673
  acknowledgements resume that same proposal and preserve the inspected identities.
664
674
 
665
- Publication applies exact Record history when present, retains Files, then
666
- publishes Asks in authored order followed by Digests. Each owning operation
675
+ Publication admits the member, workspace and Run once, uploads referenced or
676
+ explicitly retained local Files with their original IDs, applies Record changes
677
+ when present, then publishes Asks in authored order followed by Digests. Each owning operation
667
678
  validates its own work; a later failure preserves earlier confirmed effects.
668
679
  A Run without Record changes performs no Git freshness/checkout or Data gate.
669
680
  Publication preserves unrelated local work. Changed prepared bytes, authority
@@ -671,8 +682,8 @@ or conflicting Record history require repair and a new Run; publication never
671
682
  rebases inspected work.
672
683
  After interruption, repeat the same publish command with unchanged content.
673
684
  `publication.json` journals attempted operations and confirmed receipts
674
- separately from sealed intent. Fresh launches recover original commit, file and
675
- item identities. A published run reports its stored results. A killed owner
685
+ separately from sealed intent. Fresh launches resume only unconfirmed work using the original operation, File
686
+ and item identities. Confirmed receipts need no second owning-capability call. A published run reports its stored results. A killed owner
676
687
  leaves `preparing.lock`; inspect its recorded PID and root before removing a
677
688
  stale lock, and never remove a live owner's lock.
678
689