orro 0.2.2__tar.gz → 0.2.4__tar.gz

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 (14) hide show
  1. {orro-0.2.2/src/orro.egg-info → orro-0.2.4}/PKG-INFO +11 -11
  2. {orro-0.2.2 → orro-0.2.4}/README.md +10 -10
  3. {orro-0.2.2 → orro-0.2.4}/pyproject.toml +1 -1
  4. {orro-0.2.2 → orro-0.2.4}/setup.cfg +1 -1
  5. {orro-0.2.2 → orro-0.2.4/src/orro.egg-info}/PKG-INFO +11 -11
  6. {orro-0.2.2 → orro-0.2.4}/src/orro_wrapper/cli.py +4 -1
  7. {orro-0.2.2 → orro-0.2.4}/LICENSE +0 -0
  8. {orro-0.2.2 → orro-0.2.4}/src/orro.egg-info/SOURCES.txt +0 -0
  9. {orro-0.2.2 → orro-0.2.4}/src/orro.egg-info/dependency_links.txt +0 -0
  10. {orro-0.2.2 → orro-0.2.4}/src/orro.egg-info/entry_points.txt +0 -0
  11. {orro-0.2.2 → orro-0.2.4}/src/orro.egg-info/requires.txt +0 -0
  12. {orro-0.2.2 → orro-0.2.4}/src/orro.egg-info/top_level.txt +0 -0
  13. {orro-0.2.2 → orro-0.2.4}/src/orro_wrapper/__init__.py +0 -0
  14. {orro-0.2.2 → orro-0.2.4}/src/orro_wrapper/__main__.py +0 -0
{orro-0.2.2/src/orro.egg-info → orro-0.2.4}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: orro
3
- Version: 0.2.2
3
+ Version: 0.2.4
4
4
  Summary: Published ORRO product/distribution wrapper for pinned Depone and witnessd engines.
5
5
  Requires-Python: >=3.10
6
6
  Description-Content-Type: text/markdown
@@ -27,11 +27,11 @@ Today:
27
27
  - ORRO is the product and workflow surface for observed run and review.
28
28
  - This repository keeps ORRO docs, product boundary, locks, thin wrapper package metadata, assurance contract checks, and integration-surface policy.
29
29
  - The runnable `orro` command is ORRO-owned and delegates to witnessd.
30
- - The ORRO product line is published on PyPI through 0.2.1, while this repository
31
- packages the 0.2.2 release candidate. The post-release target state is: `orro`
32
- 0.2.2 is published on PyPI. It becomes true only after `v0.2.2` is tagged and
30
+ - The ORRO product line is published on PyPI through 0.2.3, while this repository
31
+ packages the 0.2.4 release candidate. The post-release target state is: `orro`
32
+ 0.2.4 is published on PyPI. It becomes true only after `v0.2.4` is tagged and
33
33
  the Trusted-Publishing workflow completes. Until then, a normal
34
- `pip install orro` installs 0.2.1.
34
+ `pip install orro` installs 0.2.3.
35
35
  - The local wrapper package exposes both `orro` and `orro-wrapper`.
36
36
 
37
37
  Current focus:
@@ -43,7 +43,7 @@ Current focus:
43
43
  ## Can I use ORRO today?
44
44
 
45
45
  Yes. The published ORRO product line is installable from PyPI at 0.2.1, and
46
- development dogfood can run the 0.2.2 source directly against pinned Depone and
46
+ development dogfood can run the 0.2.4 source directly against pinned Depone and
47
47
  witnessd checkouts.
48
48
 
49
49
  Current split:
@@ -84,7 +84,7 @@ migration.
84
84
  Current command source: the `orro` command is exposed by this ORRO package and
85
85
  delegates to `python -m orro`.
86
86
 
87
- The 0.2.2 package metadata declares `witnessd>=2.4.0,<3.0.0` while keeping Depone and
87
+ The 0.2.4 package metadata declares `witnessd>=2.4.0,<3.0.0` while keeping Depone and
88
88
  witnessd as separate engine repositories.
89
89
 
90
90
  ## Pinned Engine E2E
@@ -108,9 +108,9 @@ Engine-lock update discipline is documented in
108
108
  [`docs/engine-lock-update-process.md`](docs/engine-lock-update-process.md), and
109
109
  validated engine pairs are listed in
110
110
  [`docs/compatibility-matrix.md`](docs/compatibility-matrix.md). The `orro`
111
- product line is published on PyPI through 0.2.1; this repository sources 0.2.2,
111
+ product line is published on PyPI through 0.2.3; this repository sources 0.2.4,
112
112
  whose publication will be completed as a separate release step after the
113
- `v0.2.2` tag triggers the
113
+ `v0.2.4` tag triggers the
114
114
  Trusted-Publishing workflow. Repository metadata changes do not publish or
115
115
  rewrite an artifact.
116
116
 
@@ -146,8 +146,8 @@ metadata, not proof, not verifier truth, not package publish, not approval, and
146
146
  not assurance.
147
147
 
148
148
  The current command source is the ORRO-owned `orro` console script. The ORRO
149
- product line is published on PyPI through 0.2.1, and this repository prepares
150
- source version 0.2.2 with a `witnessd>=2.4.0,<3.0.0` dependency. The wrapper contains no
149
+ product line is published on PyPI through 0.2.3, and this repository prepares
150
+ source version 0.2.4 with a `witnessd>=2.4.0,<3.0.0` dependency. The wrapper contains no
151
151
  engine code and must not
152
152
  implement proofrun, proofcheck, scheduler, observer, fan-in, team-ledger, or
153
153
  verifier logic.
{orro-0.2.2 → orro-0.2.4}/README.md RENAMED
@@ -17,11 +17,11 @@ Today:
17
17
  - ORRO is the product and workflow surface for observed run and review.
18
18
  - This repository keeps ORRO docs, product boundary, locks, thin wrapper package metadata, assurance contract checks, and integration-surface policy.
19
19
  - The runnable `orro` command is ORRO-owned and delegates to witnessd.
20
- - The ORRO product line is published on PyPI through 0.2.1, while this repository
21
- packages the 0.2.2 release candidate. The post-release target state is: `orro`
22
- 0.2.2 is published on PyPI. It becomes true only after `v0.2.2` is tagged and
20
+ - The ORRO product line is published on PyPI through 0.2.3, while this repository
21
+ packages the 0.2.4 release candidate. The post-release target state is: `orro`
22
+ 0.2.4 is published on PyPI. It becomes true only after `v0.2.4` is tagged and
23
23
  the Trusted-Publishing workflow completes. Until then, a normal
24
- `pip install orro` installs 0.2.1.
24
+ `pip install orro` installs 0.2.3.
25
25
  - The local wrapper package exposes both `orro` and `orro-wrapper`.
26
26
 
27
27
  Current focus:
@@ -33,7 +33,7 @@ Current focus:
33
33
  ## Can I use ORRO today?
34
34
 
35
35
  Yes. The published ORRO product line is installable from PyPI at 0.2.1, and
36
- development dogfood can run the 0.2.2 source directly against pinned Depone and
36
+ development dogfood can run the 0.2.4 source directly against pinned Depone and
37
37
  witnessd checkouts.
38
38
 
39
39
  Current split:
@@ -74,7 +74,7 @@ migration.
74
74
  Current command source: the `orro` command is exposed by this ORRO package and
75
75
  delegates to `python -m orro`.
76
76
 
77
- The 0.2.2 package metadata declares `witnessd>=2.4.0,<3.0.0` while keeping Depone and
77
+ The 0.2.4 package metadata declares `witnessd>=2.4.0,<3.0.0` while keeping Depone and
78
78
  witnessd as separate engine repositories.
79
79
 
80
80
  ## Pinned Engine E2E
@@ -98,9 +98,9 @@ Engine-lock update discipline is documented in
98
98
  [`docs/engine-lock-update-process.md`](docs/engine-lock-update-process.md), and
99
99
  validated engine pairs are listed in
100
100
  [`docs/compatibility-matrix.md`](docs/compatibility-matrix.md). The `orro`
101
- product line is published on PyPI through 0.2.1; this repository sources 0.2.2,
101
+ product line is published on PyPI through 0.2.3; this repository sources 0.2.4,
102
102
  whose publication will be completed as a separate release step after the
103
- `v0.2.2` tag triggers the
103
+ `v0.2.4` tag triggers the
104
104
  Trusted-Publishing workflow. Repository metadata changes do not publish or
105
105
  rewrite an artifact.
106
106
 
@@ -136,8 +136,8 @@ metadata, not proof, not verifier truth, not package publish, not approval, and
136
136
  not assurance.
137
137
 
138
138
  The current command source is the ORRO-owned `orro` console script. The ORRO
139
- product line is published on PyPI through 0.2.1, and this repository prepares
140
- source version 0.2.2 with a `witnessd>=2.4.0,<3.0.0` dependency. The wrapper contains no
139
+ product line is published on PyPI through 0.2.3, and this repository prepares
140
+ source version 0.2.4 with a `witnessd>=2.4.0,<3.0.0` dependency. The wrapper contains no
141
141
  engine code and must not
142
142
  implement proofrun, proofcheck, scheduler, observer, fan-in, team-ledger, or
143
143
  verifier logic.
{orro-0.2.2 → orro-0.2.4}/pyproject.toml RENAMED
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "orro"
7
- version = "0.2.2"
7
+ version = "0.2.4"
8
8
  description = "Published ORRO product/distribution wrapper for pinned Depone and witnessd engines."
9
9
  readme = "README.md"
10
10
  requires-python = ">=3.10"
{orro-0.2.2 → orro-0.2.4}/setup.cfg RENAMED
@@ -1,6 +1,6 @@
1
1
  [metadata]
2
2
  name = orro
3
- version = 0.2.2
3
+ version = 0.2.4
4
4
  description = Published ORRO product/distribution wrapper for pinned Depone and witnessd engines.
5
5
  long_description = file: README.md
6
6
  long_description_content_type = text/markdown
{orro-0.2.2 → orro-0.2.4/src/orro.egg-info}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: orro
3
- Version: 0.2.2
3
+ Version: 0.2.4
4
4
  Summary: Published ORRO product/distribution wrapper for pinned Depone and witnessd engines.
5
5
  Requires-Python: >=3.10
6
6
  Description-Content-Type: text/markdown
@@ -27,11 +27,11 @@ Today:
27
27
  - ORRO is the product and workflow surface for observed run and review.
28
28
  - This repository keeps ORRO docs, product boundary, locks, thin wrapper package metadata, assurance contract checks, and integration-surface policy.
29
29
  - The runnable `orro` command is ORRO-owned and delegates to witnessd.
30
- - The ORRO product line is published on PyPI through 0.2.1, while this repository
31
- packages the 0.2.2 release candidate. The post-release target state is: `orro`
32
- 0.2.2 is published on PyPI. It becomes true only after `v0.2.2` is tagged and
30
+ - The ORRO product line is published on PyPI through 0.2.3, while this repository
31
+ packages the 0.2.4 release candidate. The post-release target state is: `orro`
32
+ 0.2.4 is published on PyPI. It becomes true only after `v0.2.4` is tagged and
33
33
  the Trusted-Publishing workflow completes. Until then, a normal
34
- `pip install orro` installs 0.2.1.
34
+ `pip install orro` installs 0.2.3.
35
35
  - The local wrapper package exposes both `orro` and `orro-wrapper`.
36
36
 
37
37
  Current focus:
@@ -43,7 +43,7 @@ Current focus:
43
43
  ## Can I use ORRO today?
44
44
 
45
45
  Yes. The published ORRO product line is installable from PyPI at 0.2.1, and
46
- development dogfood can run the 0.2.2 source directly against pinned Depone and
46
+ development dogfood can run the 0.2.4 source directly against pinned Depone and
47
47
  witnessd checkouts.
48
48
 
49
49
  Current split:
@@ -84,7 +84,7 @@ migration.
84
84
  Current command source: the `orro` command is exposed by this ORRO package and
85
85
  delegates to `python -m orro`.
86
86
 
87
- The 0.2.2 package metadata declares `witnessd>=2.4.0,<3.0.0` while keeping Depone and
87
+ The 0.2.4 package metadata declares `witnessd>=2.4.0,<3.0.0` while keeping Depone and
88
88
  witnessd as separate engine repositories.
89
89
 
90
90
  ## Pinned Engine E2E
@@ -108,9 +108,9 @@ Engine-lock update discipline is documented in
108
108
  [`docs/engine-lock-update-process.md`](docs/engine-lock-update-process.md), and
109
109
  validated engine pairs are listed in
110
110
  [`docs/compatibility-matrix.md`](docs/compatibility-matrix.md). The `orro`
111
- product line is published on PyPI through 0.2.1; this repository sources 0.2.2,
111
+ product line is published on PyPI through 0.2.3; this repository sources 0.2.4,
112
112
  whose publication will be completed as a separate release step after the
113
- `v0.2.2` tag triggers the
113
+ `v0.2.4` tag triggers the
114
114
  Trusted-Publishing workflow. Repository metadata changes do not publish or
115
115
  rewrite an artifact.
116
116
 
@@ -146,8 +146,8 @@ metadata, not proof, not verifier truth, not package publish, not approval, and
146
146
  not assurance.
147
147
 
148
148
  The current command source is the ORRO-owned `orro` console script. The ORRO
149
- product line is published on PyPI through 0.2.1, and this repository prepares
150
- source version 0.2.2 with a `witnessd>=2.4.0,<3.0.0` dependency. The wrapper contains no
149
+ product line is published on PyPI through 0.2.3, and this repository prepares
150
+ source version 0.2.4 with a `witnessd>=2.4.0,<3.0.0` dependency. The wrapper contains no
151
151
  engine code and must not
152
152
  implement proofrun, proofcheck, scheduler, observer, fan-in, team-ledger, or
153
153
  verifier logic.
{orro-0.2.2 → orro-0.2.4}/src/orro_wrapper/cli.py RENAMED
@@ -121,7 +121,10 @@ def parse_args(argv: list[str]) -> argparse.Namespace:
121
121
  parser = argparse.ArgumentParser(
122
122
  description="ORRO product command.",
123
123
  epilog="""Evidence workflow (delegated to the pinned witnessd engine):
124
- init, scout, flowplan, proofrun, proofcheck, handoff, team
124
+ init, scout, flow, flowplan, proofrun, proofcheck, handoff, team
125
+
126
+ Run the guided workflow end-to-end (init -> scout -> flowplan -> proofrun -> proofcheck) with:
127
+ orro flow <goal>
125
128
 
126
129
  Run a workflow command through the engine with:
127
130
  orro delegate -- <command>
{orro-0.2.2 → orro-0.2.4}/LICENSE RENAMED
File without changes
{orro-0.2.2 → orro-0.2.4}/src/orro.egg-info/SOURCES.txt RENAMED
File without changes
{orro-0.2.2 → orro-0.2.4}/src/orro_wrapper/__init__.py RENAMED
File without changes
{orro-0.2.2 → orro-0.2.4}/src/orro_wrapper/__main__.py RENAMED
File without changes