theoworks-sphinx-build 0.1.0__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 (25) hide show
  1. theoworks_sphinx_build-0.1.0/LICENSE +202 -0
  2. theoworks_sphinx_build-0.1.0/PKG-INFO +88 -0
  3. theoworks_sphinx_build-0.1.0/README.md +53 -0
  4. theoworks_sphinx_build-0.1.0/pyproject.toml +63 -0
  5. theoworks_sphinx_build-0.1.0/setup.cfg +4 -0
  6. theoworks_sphinx_build-0.1.0/src/theoworks_sphinx/__init__.py +32 -0
  7. theoworks_sphinx_build-0.1.0/src/theoworks_sphinx/_classify/__init__.py +53 -0
  8. theoworks_sphinx_build-0.1.0/src/theoworks_sphinx/_classify/directives.py +457 -0
  9. theoworks_sphinx_build-0.1.0/src/theoworks_sphinx/_classify/needs.py +214 -0
  10. theoworks_sphinx_build-0.1.0/src/theoworks_sphinx/_classify/prose.py +586 -0
  11. theoworks_sphinx_build-0.1.0/src/theoworks_sphinx/directive_images.py +309 -0
  12. theoworks_sphinx_build-0.1.0/src/theoworks_sphinx/directive_results.py +381 -0
  13. theoworks_sphinx_build-0.1.0/src/theoworks_sphinx/extension.py +80 -0
  14. theoworks_sphinx_build-0.1.0/src/theoworks_sphinx/schema_dump.py +102 -0
  15. theoworks_sphinx_build-0.1.0/src/theoworks_sphinx_build.egg-info/PKG-INFO +88 -0
  16. theoworks_sphinx_build-0.1.0/src/theoworks_sphinx_build.egg-info/SOURCES.txt +23 -0
  17. theoworks_sphinx_build-0.1.0/src/theoworks_sphinx_build.egg-info/dependency_links.txt +1 -0
  18. theoworks_sphinx_build-0.1.0/src/theoworks_sphinx_build.egg-info/requires.txt +10 -0
  19. theoworks_sphinx_build-0.1.0/src/theoworks_sphinx_build.egg-info/top_level.txt +1 -0
  20. theoworks_sphinx_build-0.1.0/tests/test_classify_vendored_source_drift.py +57 -0
  21. theoworks_sphinx_build-0.1.0/tests/test_directive_images.py +138 -0
  22. theoworks_sphinx_build-0.1.0/tests/test_extension_setup.py +50 -0
  23. theoworks_sphinx_build-0.1.0/tests/test_ip_boundary.py +154 -0
  24. theoworks_sphinx_build-0.1.0/tests/test_real_sphinx_build.py +100 -0
  25. theoworks_sphinx_build-0.1.0/tests/test_schema_dump.py +50 -0
@@ -0,0 +1,202 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright 2026 TheoWorks
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
@@ -0,0 +1,88 @@
1
+ Metadata-Version: 2.4
2
+ Name: theoworks-sphinx-build
3
+ Version: 0.1.0
4
+ Summary: The minimum TheoWorks Sphinx extension for a customer's own sphinx-build: emits theoworks-schema.json and (optionally) the diagram-image + computed-directive-result manifests, with zero crown-jewel IP
5
+ Author: TheoWorks
6
+ License-Expression: Apache-2.0
7
+ Project-URL: Homepage, https://theoworks.io
8
+ Project-URL: Source, https://gitlab.com/theoworks/theoworks
9
+ Keywords: sphinx,sphinx-needs,requirements,ASPICE,traceability
10
+ Classifier: Development Status :: 4 - Beta
11
+ Classifier: Framework :: Sphinx
12
+ Classifier: Framework :: Sphinx :: Extension
13
+ Classifier: Intended Audience :: Developers
14
+ Classifier: Operating System :: OS Independent
15
+ Classifier: Programming Language :: Python :: 3
16
+ Classifier: Programming Language :: Python :: 3.10
17
+ Classifier: Programming Language :: Python :: 3.11
18
+ Classifier: Programming Language :: Python :: 3.12
19
+ Classifier: Programming Language :: Python :: 3.13
20
+ Classifier: Programming Language :: Python :: 3.14
21
+ Classifier: Topic :: Documentation :: Sphinx
22
+ Classifier: Topic :: Software Development :: Documentation
23
+ Requires-Python: >=3.10
24
+ Description-Content-Type: text/markdown
25
+ License-File: LICENSE
26
+ Provides-Extra: extension
27
+ Requires-Dist: sphinx>=7.4; extra == "extension"
28
+ Requires-Dist: sphinx-needs>=8.1.1; extra == "extension"
29
+ Provides-Extra: dev
30
+ Requires-Dist: pytest>=8; extra == "dev"
31
+ Requires-Dist: sphinx>=7.4; extra == "dev"
32
+ Requires-Dist: sphinx-needs>=8.1.1; extra == "dev"
33
+ Requires-Dist: PyYAML; extra == "dev"
34
+ Dynamic: license-file
35
+
36
+ # theoworks-sphinx-build
37
+
38
+ The **minimum** [TheoWorks](https://theoworks.io) Sphinx extension for a
39
+ customer's own `sphinx-build`. It runs inside a
40
+ [sphinx-needs](https://sphinx-needs.readthedocs.io) build and emits exactly
41
+ the artifacts that genuinely require an in-build render:
42
+
43
+ - `theoworks-schema.json` — the RESOLVED `needs_*` metamodel, captured after
44
+ every extension's `setup()` has run (so an extension-registered metamodel,
45
+ e.g. a bundle bringing its own `needs_types`, is recoverable even though it
46
+ never appears as a `conf.py` literal).
47
+ - `theoworks-directive-images.json` — the needuml/needsequence
48
+ diagram-image location manifest (only when PlantUML rendered one).
49
+ - `theoworks-directive-results.json` — the computed needtable/needlist/
50
+ needextract/needbar/needpie result manifest (only when a computed
51
+ directive occurs).
52
+
53
+ This is deliberately **not** the full TheoWorks toolchain. `theoworks
54
+ init` / `validate` / `trace` / `build-index`, the rich needs-graph read
55
+ model, and the byte-stable RST editor all live in the proprietary
56
+ `theoworks-cli` image / self-host server / VS Code extension — never in this
57
+ package. `theoworks-sphinx-build` ships zero of that surface; its only
58
+ dependency on TheoWorks IP is a small, vendored directive-block scanner +
59
+ two content-address hashes (never the byte-stable serializer, validation, or
60
+ packs).
61
+
62
+ ## Install
63
+
64
+ ```bash
65
+ pip install theoworks-sphinx-build
66
+ ```
67
+
68
+ ## Usage
69
+
70
+ Add the extension to your project's `conf.py` (after `sphinx_needs`) — note
71
+ the **importable module name stays `theoworks_sphinx`**, even though the
72
+ PyPI distribution is `theoworks-sphinx-build` (so an existing
73
+ `extensions = [..., "theoworks_sphinx"]`, including anything TheoWorks has
74
+ already scaffolded for you, keeps working unchanged):
75
+
76
+ ```python
77
+ extensions = ["sphinx_needs", "theoworks_sphinx"]
78
+ ```
79
+
80
+ Then build as usual:
81
+
82
+ ```bash
83
+ sphinx-build -b html docs public
84
+ ```
85
+
86
+ If the package is not installed, a TheoWorks-scaffolded `conf.py` degrades
87
+ gracefully — the build still succeeds and still produces `needs.json` (the
88
+ floor); you only lose the richer previews above.
@@ -0,0 +1,53 @@
1
+ # theoworks-sphinx-build
2
+
3
+ The **minimum** [TheoWorks](https://theoworks.io) Sphinx extension for a
4
+ customer's own `sphinx-build`. It runs inside a
5
+ [sphinx-needs](https://sphinx-needs.readthedocs.io) build and emits exactly
6
+ the artifacts that genuinely require an in-build render:
7
+
8
+ - `theoworks-schema.json` — the RESOLVED `needs_*` metamodel, captured after
9
+ every extension's `setup()` has run (so an extension-registered metamodel,
10
+ e.g. a bundle bringing its own `needs_types`, is recoverable even though it
11
+ never appears as a `conf.py` literal).
12
+ - `theoworks-directive-images.json` — the needuml/needsequence
13
+ diagram-image location manifest (only when PlantUML rendered one).
14
+ - `theoworks-directive-results.json` — the computed needtable/needlist/
15
+ needextract/needbar/needpie result manifest (only when a computed
16
+ directive occurs).
17
+
18
+ This is deliberately **not** the full TheoWorks toolchain. `theoworks
19
+ init` / `validate` / `trace` / `build-index`, the rich needs-graph read
20
+ model, and the byte-stable RST editor all live in the proprietary
21
+ `theoworks-cli` image / self-host server / VS Code extension — never in this
22
+ package. `theoworks-sphinx-build` ships zero of that surface; its only
23
+ dependency on TheoWorks IP is a small, vendored directive-block scanner +
24
+ two content-address hashes (never the byte-stable serializer, validation, or
25
+ packs).
26
+
27
+ ## Install
28
+
29
+ ```bash
30
+ pip install theoworks-sphinx-build
31
+ ```
32
+
33
+ ## Usage
34
+
35
+ Add the extension to your project's `conf.py` (after `sphinx_needs`) — note
36
+ the **importable module name stays `theoworks_sphinx`**, even though the
37
+ PyPI distribution is `theoworks-sphinx-build` (so an existing
38
+ `extensions = [..., "theoworks_sphinx"]`, including anything TheoWorks has
39
+ already scaffolded for you, keeps working unchanged):
40
+
41
+ ```python
42
+ extensions = ["sphinx_needs", "theoworks_sphinx"]
43
+ ```
44
+
45
+ Then build as usual:
46
+
47
+ ```bash
48
+ sphinx-build -b html docs public
49
+ ```
50
+
51
+ If the package is not installed, a TheoWorks-scaffolded `conf.py` degrades
52
+ gracefully — the build still succeeds and still produces `needs.json` (the
53
+ floor); you only lose the richer previews above.
@@ -0,0 +1,63 @@
1
+ [build-system]
2
+ requires = ["setuptools>=77"]
3
+ build-backend = "setuptools.build_meta"
4
+
5
+ [project]
6
+ name = "theoworks-sphinx-build"
7
+ version = "0.1.0"
8
+ description = "The minimum TheoWorks Sphinx extension for a customer's own sphinx-build: emits theoworks-schema.json and (optionally) the diagram-image + computed-directive-result manifests, with zero crown-jewel IP"
9
+ readme = "README.md"
10
+ license = "Apache-2.0"
11
+ license-files = ["LICENSE"]
12
+ requires-python = ">=3.10"
13
+ authors = [{ name = "TheoWorks" }]
14
+ keywords = ["sphinx", "sphinx-needs", "requirements", "ASPICE", "traceability"]
15
+ # Deliberately []: this package never depends on theoworks-core (or any other
16
+ # TheoWorks package). Its bounded "classify subset" (directive-block scan +
17
+ # content-hash) is a VENDORED copy inside theoworks_sphinx._classify, not an
18
+ # import — §4.2. sphinx/sphinx-needs are the customer's own build's
19
+ # dependency, not this package's (see the `extension` extra below) — mirrors
20
+ # how the (now-unpublished) theoworks-sphinx package always treated them.
21
+ dependencies = []
22
+ classifiers = [
23
+ "Development Status :: 4 - Beta",
24
+ "Framework :: Sphinx",
25
+ "Framework :: Sphinx :: Extension",
26
+ "Intended Audience :: Developers",
27
+ "Operating System :: OS Independent",
28
+ "Programming Language :: Python :: 3",
29
+ "Programming Language :: Python :: 3.10",
30
+ "Programming Language :: Python :: 3.11",
31
+ "Programming Language :: Python :: 3.12",
32
+ "Programming Language :: Python :: 3.13",
33
+ "Programming Language :: Python :: 3.14",
34
+ "Topic :: Documentation :: Sphinx",
35
+ "Topic :: Software Development :: Documentation",
36
+ ]
37
+
38
+ [project.urls]
39
+ Homepage = "https://theoworks.io"
40
+ Source = "https://gitlab.com/theoworks/theoworks"
41
+
42
+ [project.optional-dependencies]
43
+ # Mirrors theoworks-sphinx's own `[extension]` extra (same reasoning: Sphinx
44
+ # itself must be running for an extension to load at all, and extension.py
45
+ # imports neither sphinx nor sphinx_needs at module level, so this package
46
+ # stays importable/testable without either installed). A customer's own
47
+ # sphinx-build already supplies both; this extra exists for anyone installing
48
+ # theoworks-sphinx-build standalone (e.g. to run a real build locally) who
49
+ # wants pip to pull a floor-conforming pair in the same resolution.
50
+ #
51
+ # sphinx-needs support floor >=8.1.1 — the same floor the scaffold's generated CI declares.
52
+ extension = ["sphinx>=7.4", "sphinx-needs>=8.1.1"]
53
+ dev = ["pytest>=8", "sphinx>=7.4", "sphinx-needs>=8.1.1", "PyYAML"]
54
+
55
+ [tool.setuptools.packages.find]
56
+ where = ["src"]
57
+
58
+ [tool.pytest.ini_options]
59
+ pythonpath = ["src"]
60
+ testpaths = ["tests"]
61
+ markers = [
62
+ "slow: real Sphinx build; slower than pure unit tests",
63
+ ]
@@ -0,0 +1,4 @@
1
+ [egg_info]
2
+ tag_build =
3
+ tag_date = 0
4
+
@@ -0,0 +1,32 @@
1
+ """``theoworks-sphinx-build`` — the ONE minimum TheoWorks PyPI package (ADR-0281).
2
+
3
+ Distributed on PyPI as ``theoworks-sphinx-build``; the **importable module
4
+ stays named** ``theoworks_sphinx`` (ADR-0281 §3) so an existing
5
+ ``extensions = [..., "theoworks_sphinx"]`` — including every project
6
+ TheoWorks has already scaffolded — keeps working unchanged. Only the
7
+ distribution name and its contents differ from the (now proprietary,
8
+ unpublished) full ``theoworks-sphinx`` package: this one registers ONLY the
9
+ three render-bound, core-free-of-crown-jewel hooks (schema dump + the two
10
+ directive manifests, ADR-0281 §4) — never the rich extractor, never the
11
+ byte-stable serializer/validation/packs.
12
+ """
13
+ from __future__ import annotations
14
+
15
+ __version__ = "0.1.0"
16
+
17
+ from .directive_images import MANIFEST_NAME as DIRECTIVE_IMAGES_MANIFEST_NAME
18
+ from .directive_results import MANIFEST_NAME as DIRECTIVE_RESULTS_MANIFEST_NAME
19
+ from .schema_dump import SCHEMA_DUMP_NAME, build_dump, write_dump
20
+
21
+ __all__ = [
22
+ "SCHEMA_DUMP_NAME", "build_dump", "write_dump",
23
+ "DIRECTIVE_IMAGES_MANIFEST_NAME", "DIRECTIVE_RESULTS_MANIFEST_NAME",
24
+ "setup",
25
+ ]
26
+
27
+
28
+ def setup(app):
29
+ """Sphinx entry point (re-exported from .extension)."""
30
+ from .extension import setup as _setup
31
+
32
+ return _setup(app)
@@ -0,0 +1,53 @@
1
+ """The bounded, low-IP "classify subset" (ADR-0281 §4.1/§4.2 Option B).
2
+
3
+ **What this is.** ``needs.py`` / ``prose.py`` / ``directives.py`` in this
4
+ subpackage are **byte-identical vendored copies** of the same-named modules in
5
+ ``packages/theoworks-core/src/theoworks_core/`` — a directive-block scanner
6
+ (``iter_need_blocks``/``parse_need``) plus two content-address hashes
7
+ (``directive_image_key``/``directive_result_key``/``directive_structure``).
8
+ Vendored, not imported, **on purpose**: importing ``theoworks_core`` (even a
9
+ single submodule) executes ``theoworks_core/__init__.py``, which eagerly
10
+ imports every module in the package — including the byte-stable RST
11
+ round-trip serializer (ADR-0035), ``validate.py``, ``pack.py``, and
12
+ ``trace.py`` (the crown jewel). A customer who ``pip install``s
13
+ ``theoworks-sphinx-build`` must never receive that surface, so this
14
+ subpackage is entirely self-contained: it imports nothing from
15
+ ``theoworks_core`` and nothing from ``theoworks_sphinx``'s own rich sibling
16
+ package. See ``theoworks_sphinx_build`` test suite's IP-boundary test for the
17
+ enforcement.
18
+
19
+ **Why vendored copies instead of a re-export.** ``directives.py`` imports only
20
+ ``.needs`` and ``.prose`` (confirmed by reading their import lines — both are
21
+ stdlib-only, `re`/`dataclasses`). That subgraph is genuinely separable from
22
+ the rest of ``theoworks_core``, but Python has no way to import "only these
23
+ three submodules" of a package without first running that package's
24
+ ``__init__.py``. Vendoring the three files verbatim is the only mechanism
25
+ that ships a wheel provably free of the crown jewel while staying byte-exact
26
+ with the editor client's own parse (the key correctness property ADR-0072 /
27
+ ADR-0209 depend on: the manifest's key must match what
28
+ ``theoworks-ui-editor`` computes for the same directive content).
29
+
30
+ **Anti-drift protection.** Because this is a physical copy rather than a
31
+ single source of truth, ``tests/test_classify_vendored.drift_test.py`` in
32
+ this package asserts the three files remain byte-identical to their
33
+ ``theoworks_core`` originals (a monorepo-only check — the drift guard reads
34
+ the sibling package's source tree directly; it is a source-shape assertion,
35
+ not a behavioral one). The REAL behavioral coverage — that the keys these
36
+ functions produce match what the editor computes, and that the manifests
37
+ this subset drives are correct — lives in
38
+ ``theoworks_sphinx_build``'s own real-``sphinx-build`` integration test and
39
+ in ``theoworks-ui-editor``'s own directive-key parity tests; this drift guard
40
+ only prevents the vendored copy from silently diverging from its source.
41
+ """
42
+ from __future__ import annotations
43
+
44
+ from .directives import directive_image_key, directive_result_key, directive_structure
45
+ from .needs import iter_need_blocks, parse_need
46
+
47
+ __all__ = [
48
+ "iter_need_blocks",
49
+ "parse_need",
50
+ "directive_structure",
51
+ "directive_image_key",
52
+ "directive_result_key",
53
+ ]