opdev 0.7.0a2__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 (41) hide show
  1. opdev-0.7.0a2/LICENSE +201 -0
  2. opdev-0.7.0a2/PKG-INFO +99 -0
  3. opdev-0.7.0a2/README.md +81 -0
  4. opdev-0.7.0a2/pyproject.toml +79 -0
  5. opdev-0.7.0a2/src/opdev/__init__.py +1 -0
  6. opdev-0.7.0a2/src/opdev/__main__.py +3 -0
  7. opdev-0.7.0a2/src/opdev/checks.py +300 -0
  8. opdev-0.7.0a2/src/opdev/cli.py +459 -0
  9. opdev-0.7.0a2/src/opdev/commands.py +76 -0
  10. opdev-0.7.0a2/src/opdev/config.py +278 -0
  11. opdev-0.7.0a2/src/opdev/document_catalog.py +107 -0
  12. opdev-0.7.0a2/src/opdev/document_review.py +115 -0
  13. opdev-0.7.0a2/src/opdev/documents.py +415 -0
  14. opdev-0.7.0a2/src/opdev/errors.py +5 -0
  15. opdev-0.7.0a2/src/opdev/files.py +82 -0
  16. opdev-0.7.0a2/src/opdev/init.py +87 -0
  17. opdev-0.7.0a2/src/opdev/junit.py +99 -0
  18. opdev-0.7.0a2/src/opdev/output.py +141 -0
  19. opdev-0.7.0a2/src/opdev/process.py +145 -0
  20. opdev-0.7.0a2/src/opdev/providers/__init__.py +1 -0
  21. opdev-0.7.0a2/src/opdev/providers/gitlab.py +374 -0
  22. opdev-0.7.0a2/src/opdev/publication.py +209 -0
  23. opdev-0.7.0a2/src/opdev/reports.py +512 -0
  24. opdev-0.7.0a2/src/opdev/requirements.py +642 -0
  25. opdev-0.7.0a2/src/opdev/resources/reports/report.css +158 -0
  26. opdev-0.7.0a2/src/opdev/resources/reports/report.html +27 -0
  27. opdev-0.7.0a2/src/opdev/resources/reports/report.js +110 -0
  28. opdev-0.7.0a2/src/opdev/resources/skills/opdev/SKILL.md +190 -0
  29. opdev-0.7.0a2/src/opdev/resources/skills/opdev/references/adoption.md +144 -0
  30. opdev-0.7.0a2/src/opdev/resources/skills/opdev/references/design.md +141 -0
  31. opdev-0.7.0a2/src/opdev/resources/skills/opdev/references/development.md +294 -0
  32. opdev-0.7.0a2/src/opdev/resources/skills/opdev/references/engineering.md +206 -0
  33. opdev-0.7.0a2/src/opdev/resources/skills/opdev/references/planning.md +101 -0
  34. opdev-0.7.0a2/src/opdev/resources/skills/opdev/references/publication.md +34 -0
  35. opdev-0.7.0a2/src/opdev/resources/templates/AGENTS.md +7 -0
  36. opdev-0.7.0a2/src/opdev/resources/templates/CLAUDE.md +6 -0
  37. opdev-0.7.0a2/src/opdev/resources/templates/guidance.md +36 -0
  38. opdev-0.7.0a2/src/opdev/snapshot.py +484 -0
  39. opdev-0.7.0a2/src/opdev/tracking.py +224 -0
  40. opdev-0.7.0a2/src/opdev/verification.py +234 -0
  41. opdev-0.7.0a2/src/opdev/version.py +45 -0
opdev-0.7.0a2/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright [yyyy] [name of copyright owner]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
opdev-0.7.0a2/PKG-INFO ADDED
@@ -0,0 +1,99 @@
1
+ Metadata-Version: 2.4
2
+ Name: opdev
3
+ Version: 0.7.0a2
4
+ Summary: Configuration-driven software development workflow CLI
5
+ License-Expression: Apache-2.0
6
+ License-File: LICENSE
7
+ Classifier: Development Status :: 3 - Alpha
8
+ Classifier: Programming Language :: Python :: 3
9
+ Requires-Dist: pyyaml>=6.0.2,<7
10
+ Requires-Dist: defusedxml>=0.7.1,<1
11
+ Requires-Dist: markdown-it-py>=4,<5
12
+ Requires-Dist: psutil>=7,<8
13
+ Requires-Python: >=3.12
14
+ Project-URL: Documentation, https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/README.md
15
+ Project-URL: Issues, https://gitlab.com/stolenfootball-tools/opdev/-/issues
16
+ Project-URL: Source, https://gitlab.com/stolenfootball-tools/opdev
17
+ Description-Content-Type: text/markdown
18
+
19
+ # OpDev
20
+
21
+ OpDev gives developers and coding agents one way to run a project's tools, query
22
+ requirements and their tests, and manage work in GitLab. You choose the tools and
23
+ required checks in a configuration file; OpDev runs them and reports what passed,
24
+ failed or never ran.
25
+
26
+ The optional Codex and Claude Code plugin guides discovery, design approval,
27
+ phased planning and implementation. The CLI handles configured operations. Your
28
+ application can use any language; only OpDev itself needs Python.
29
+
30
+ **Alpha:** this is the active Python implementation, licensed under
31
+ [Apache-2.0](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/LICENSE). Download the matching CLI and plugin from the
32
+ [GitLab releases](https://gitlab.com/stolenfootball-tools/opdev/-/releases).
33
+ The earlier Rust implementation is [archived](https://gitlab.com/stolenfootball-tools/opdev-legacy).
34
+ Use an isolated environment and explicitly
35
+ select this version; existing Rust installations need a reviewed migration.
36
+ Claude Code package validation and behavioral testing are separate: Claude
37
+ behavioral testing remains **unverified**.
38
+
39
+ ## Start here
40
+
41
+ To try OpDev on a small project, follow [Getting started](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/getting-started.md).
42
+ The walkthrough sets up one real test, previews its command and runs it.
43
+
44
+ If you already have this checkout and [uv](https://docs.astral.sh/uv/getting-started/installation/),
45
+ you can inspect OpDev's own configuration first. Python 3.12+ is required; uv can
46
+ provision a compatible interpreter.
47
+
48
+ ```console
49
+ uv sync --locked
50
+ uv run --locked opdev commands
51
+ uv run --locked opdev check --plan
52
+ ```
53
+
54
+ These last two commands inspect configuration without running project tools.
55
+ After reviewing the configuration, try a focused check or query a requirement:
56
+
57
+ ```console
58
+ uv run --locked opdev lint
59
+ uv run --locked opdev requirement show REQ-03 --tree --tests
60
+ ```
61
+
62
+ ## How it fits your project
63
+
64
+ - **Configure once.** Define command arguments, directories and timeouts in
65
+ `.opdev/project.yaml`. Use your existing formatter, linter, test runner and build tools.
66
+ - **Check the right scope.** Use focused checks while iterating and `opdev check`
67
+ for every required check before integration. Native CI enforces remote checks.
68
+ - **Keep requirements concrete.** Store product obligations and direct test links
69
+ in `.opdev/requirements.json`; query the records you need through the CLI.
70
+ - **Track work remotely.** Keep phases, milestones, issues and progress in GitLab.
71
+ Keep current designs and requirements in Git, without a local backlog or evidence ledger.
72
+ - **Publish deliberately.** After explicit authorization, `opdev publish` runs
73
+ fresh checks against fixed inputs before invoking your configured publisher.
74
+
75
+ OpDev reports command outcomes and, with [JUnit validation](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/checks.md#validate-individual-tests-with-junit),
76
+ individual reported test results matched to explicit requirement mappings. It cannot
77
+ prove assertion adequacy or developer approval, or sandbox untrusted repository
78
+ commands. Those distinctions remain visible in its reports and workflow.
79
+
80
+ ## User documentation
81
+
82
+ | I want to… | Read |
83
+ | --- | --- |
84
+ | Set up a project and run a first test | [Getting started](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/getting-started.md) |
85
+ | Define tools and required checks | [Configuration](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/configuration.md) |
86
+ | Maintain development decisions and validate their structure | [Development documents](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/documentation.md) |
87
+ | Build, test, run, lint or format | [Development commands](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/commands.md) |
88
+ | Preview checks and understand failures | [Checks](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/checks.md) |
89
+ | Record requirements and link tests | [Requirements](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/requirements.md) |
90
+ | Export a run for review or audit | [Verification reports](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/reports.md) |
91
+ | Manage phases, milestones and issues | [Work tracking](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/work-tracking.md) |
92
+ | Verify inputs before publication | [Publication](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/publication.md) |
93
+ | Connect Codex, Claude Code or CI | [Integrations](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/integrations.md) |
94
+
95
+ These guides are OpDev's manual. OpDev does not create, organize or enforce user
96
+ documentation in your project; its content and location are your choice.
97
+
98
+ To contribute to OpDev, start with [.opdev/guidance.md](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/.opdev/guidance.md).
99
+ Implementation plans and progress belong in [GitLab issues](https://gitlab.com/stolenfootball-tools/opdev/-/issues).
@@ -0,0 +1,81 @@
1
+ # OpDev
2
+
3
+ OpDev gives developers and coding agents one way to run a project's tools, query
4
+ requirements and their tests, and manage work in GitLab. You choose the tools and
5
+ required checks in a configuration file; OpDev runs them and reports what passed,
6
+ failed or never ran.
7
+
8
+ The optional Codex and Claude Code plugin guides discovery, design approval,
9
+ phased planning and implementation. The CLI handles configured operations. Your
10
+ application can use any language; only OpDev itself needs Python.
11
+
12
+ **Alpha:** this is the active Python implementation, licensed under
13
+ [Apache-2.0](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/LICENSE). Download the matching CLI and plugin from the
14
+ [GitLab releases](https://gitlab.com/stolenfootball-tools/opdev/-/releases).
15
+ The earlier Rust implementation is [archived](https://gitlab.com/stolenfootball-tools/opdev-legacy).
16
+ Use an isolated environment and explicitly
17
+ select this version; existing Rust installations need a reviewed migration.
18
+ Claude Code package validation and behavioral testing are separate: Claude
19
+ behavioral testing remains **unverified**.
20
+
21
+ ## Start here
22
+
23
+ To try OpDev on a small project, follow [Getting started](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/getting-started.md).
24
+ The walkthrough sets up one real test, previews its command and runs it.
25
+
26
+ If you already have this checkout and [uv](https://docs.astral.sh/uv/getting-started/installation/),
27
+ you can inspect OpDev's own configuration first. Python 3.12+ is required; uv can
28
+ provision a compatible interpreter.
29
+
30
+ ```console
31
+ uv sync --locked
32
+ uv run --locked opdev commands
33
+ uv run --locked opdev check --plan
34
+ ```
35
+
36
+ These last two commands inspect configuration without running project tools.
37
+ After reviewing the configuration, try a focused check or query a requirement:
38
+
39
+ ```console
40
+ uv run --locked opdev lint
41
+ uv run --locked opdev requirement show REQ-03 --tree --tests
42
+ ```
43
+
44
+ ## How it fits your project
45
+
46
+ - **Configure once.** Define command arguments, directories and timeouts in
47
+ `.opdev/project.yaml`. Use your existing formatter, linter, test runner and build tools.
48
+ - **Check the right scope.** Use focused checks while iterating and `opdev check`
49
+ for every required check before integration. Native CI enforces remote checks.
50
+ - **Keep requirements concrete.** Store product obligations and direct test links
51
+ in `.opdev/requirements.json`; query the records you need through the CLI.
52
+ - **Track work remotely.** Keep phases, milestones, issues and progress in GitLab.
53
+ Keep current designs and requirements in Git, without a local backlog or evidence ledger.
54
+ - **Publish deliberately.** After explicit authorization, `opdev publish` runs
55
+ fresh checks against fixed inputs before invoking your configured publisher.
56
+
57
+ OpDev reports command outcomes and, with [JUnit validation](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/checks.md#validate-individual-tests-with-junit),
58
+ individual reported test results matched to explicit requirement mappings. It cannot
59
+ prove assertion adequacy or developer approval, or sandbox untrusted repository
60
+ commands. Those distinctions remain visible in its reports and workflow.
61
+
62
+ ## User documentation
63
+
64
+ | I want to… | Read |
65
+ | --- | --- |
66
+ | Set up a project and run a first test | [Getting started](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/getting-started.md) |
67
+ | Define tools and required checks | [Configuration](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/configuration.md) |
68
+ | Maintain development decisions and validate their structure | [Development documents](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/documentation.md) |
69
+ | Build, test, run, lint or format | [Development commands](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/commands.md) |
70
+ | Preview checks and understand failures | [Checks](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/checks.md) |
71
+ | Record requirements and link tests | [Requirements](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/requirements.md) |
72
+ | Export a run for review or audit | [Verification reports](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/reports.md) |
73
+ | Manage phases, milestones and issues | [Work tracking](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/work-tracking.md) |
74
+ | Verify inputs before publication | [Publication](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/publication.md) |
75
+ | Connect Codex, Claude Code or CI | [Integrations](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/docs/integrations.md) |
76
+
77
+ These guides are OpDev's manual. OpDev does not create, organize or enforce user
78
+ documentation in your project; its content and location are your choice.
79
+
80
+ To contribute to OpDev, start with [.opdev/guidance.md](https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/.opdev/guidance.md).
81
+ Implementation plans and progress belong in [GitLab issues](https://gitlab.com/stolenfootball-tools/opdev/-/issues).
@@ -0,0 +1,79 @@
1
+ [project]
2
+ name = "opdev"
3
+ version = "0.7.0a2"
4
+ description = "Configuration-driven software development workflow CLI"
5
+ readme = "README.md"
6
+ requires-python = ">=3.12"
7
+ license = "Apache-2.0"
8
+ license-files = ["LICENSE"]
9
+ classifiers = ["Development Status :: 3 - Alpha", "Programming Language :: Python :: 3"]
10
+ dependencies = [
11
+ "PyYAML>=6.0.2,<7",
12
+ "defusedxml>=0.7.1,<1",
13
+ "markdown-it-py>=4,<5",
14
+ "psutil>=7,<8",
15
+ ]
16
+
17
+ [project.urls]
18
+ Source = "https://gitlab.com/stolenfootball-tools/opdev"
19
+ Documentation = "https://gitlab.com/stolenfootball-tools/opdev/-/blob/main/README.md"
20
+ Issues = "https://gitlab.com/stolenfootball-tools/opdev/-/issues"
21
+
22
+ [project.scripts]
23
+ opdev = "opdev.cli:main"
24
+
25
+ [build-system]
26
+ requires = ["uv_build>=0.9.18,<0.10"]
27
+ build-backend = "uv_build"
28
+
29
+ [tool.uv.build-backend]
30
+ module-name = "opdev"
31
+
32
+ [dependency-groups]
33
+ dev = [
34
+ "pytest>=8,<10",
35
+ "ruff>=0.14,<1",
36
+ "mypy>=1.18,<2",
37
+ "types-PyYAML>=6,<7",
38
+ "types-psutil>=7,<8",
39
+ "types-defusedxml>=0.7,<1",
40
+ "unittest-xml-reporting>=3.2,<4",
41
+ "playwright>=1.56,<2",
42
+ "import-linter>=2,<3",
43
+ ]
44
+
45
+ [tool.pytest.ini_options]
46
+ testpaths = ["tests"]
47
+ addopts = "-ra --import-mode=importlib"
48
+
49
+ [tool.ruff]
50
+ target-version = "py312"
51
+ line-length = 100
52
+
53
+ [tool.ruff.lint]
54
+ select = ["E", "F", "I", "UP", "B", "C901", "RUF100"]
55
+
56
+ [tool.ruff.lint.mccabe]
57
+ max-complexity = 10
58
+
59
+ [tool.ruff.lint.per-file-ignores]
60
+ # Production-function complexity is separate from declarative test/fixture orchestration.
61
+ "tests/**" = ["C901"]
62
+ "tools/**" = ["C901"]
63
+
64
+ [tool.mypy]
65
+ python_version = "3.12"
66
+ strict = true
67
+ files = ["src/opdev"]
68
+
69
+ [tool.importlinter]
70
+ root_package = "opdev"
71
+
72
+ [[tool.importlinter.contracts]]
73
+ name = "Low-level effects stay independent of application features"
74
+ type = "forbidden"
75
+ source_modules = ["opdev.files", "opdev.process", "opdev.errors"]
76
+ forbidden_modules = ["opdev.*"]
77
+ # Presentable errors are the deliberately shared low-level dependency.
78
+ ignore_imports = ["opdev.files -> opdev.errors", "opdev.process -> opdev.errors"]
79
+ unmatched_ignore_imports_alerting = "error"
@@ -0,0 +1 @@
1
+ """Small, configuration-driven development operations."""
@@ -0,0 +1,3 @@
1
+ from opdev.cli import main
2
+
3
+ raise SystemExit(main())