specfuse 0.3.0__tar.gz → 0.3.2__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 (17) hide show
  1. {specfuse-0.3.0/specfuse.egg-info → specfuse-0.3.2}/PKG-INFO +16 -12
  2. {specfuse-0.3.0 → specfuse-0.3.2}/README.md +14 -10
  3. {specfuse-0.3.0 → specfuse-0.3.2}/pyproject.toml +2 -2
  4. {specfuse-0.3.0 → specfuse-0.3.2}/specfuse/cli.py +1 -1
  5. {specfuse-0.3.0 → specfuse-0.3.2/specfuse.egg-info}/PKG-INFO +16 -12
  6. {specfuse-0.3.0 → specfuse-0.3.2}/specfuse.egg-info/requires.txt +1 -1
  7. {specfuse-0.3.0 → specfuse-0.3.2}/LICENSE +0 -0
  8. {specfuse-0.3.0 → specfuse-0.3.2}/NOTICE +0 -0
  9. {specfuse-0.3.0 → specfuse-0.3.2}/setup.cfg +0 -0
  10. {specfuse-0.3.0 → specfuse-0.3.2}/specfuse/publish.py +0 -0
  11. {specfuse-0.3.0 → specfuse-0.3.2}/specfuse.egg-info/SOURCES.txt +0 -0
  12. {specfuse-0.3.0 → specfuse-0.3.2}/specfuse.egg-info/dependency_links.txt +0 -0
  13. {specfuse-0.3.0 → specfuse-0.3.2}/specfuse.egg-info/entry_points.txt +0 -0
  14. {specfuse-0.3.0 → specfuse-0.3.2}/specfuse.egg-info/top_level.txt +0 -0
  15. {specfuse-0.3.0 → specfuse-0.3.2}/tests/test_cli.py +0 -0
  16. {specfuse-0.3.0 → specfuse-0.3.2}/tests/test_entry_points.py +0 -0
  17. {specfuse-0.3.0 → specfuse-0.3.2}/tests/test_publish.py +0 -0
{specfuse-0.3.0/specfuse.egg-info → specfuse-0.3.2}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: specfuse
3
- Version: 0.3.0
3
+ Version: 0.3.2
4
4
  Summary: Specfuse umbrella CLI — bridges the pip-installed driver and the Claude Code plugin (init / upgrade).
5
5
  Author: Specfuse contributors
6
6
  License: Apache-2.0
@@ -17,7 +17,7 @@ Requires-Python: >=3.10
17
17
  Description-Content-Type: text/markdown
18
18
  License-File: LICENSE
19
19
  License-File: NOTICE
20
- Requires-Dist: specfuse-loop>=0.3.5
20
+ Requires-Dist: specfuse-loop>=0.3.12
21
21
  Provides-Extra: dev
22
22
  Requires-Dist: coverage>=7.0; extra == "dev"
23
23
  Requires-Dist: ruff>=0.6; extra == "dev"
@@ -61,20 +61,24 @@ This repo also ships the **`specfuse`** pip package — the umbrella CLI that br
61
61
  the pip-installed driver and this plugin:
62
62
 
63
63
  ```
64
- pipx install specfuse # recommended (CLI app); pulls specfuse-loop too
65
- pipx install 'specfuse[orchestrator]' # + the multi-repo orchestrator
66
- pipx install 'specfuse[authoring]' # + the spec-authoring kit
67
- pipx install 'specfuse[all]' # the whole suite in one command
68
- # gives you: specfuse / specfuse-loop / specfuse-lint (+ the extras' CLIs)
69
- # (quote the brackets — zsh globs them; or: python3 -m pip install 'specfuse[all]')
64
+ pipx install specfuse # driver only; gives specfuse / specfuse-loop / specfuse-lint
65
+ pipx install --include-deps 'specfuse[orchestrator]' # + the multi-repo orchestrator
66
+ pipx install --include-deps 'specfuse[authoring]' # + the spec-authoring kit
67
+ pipx install --include-deps 'specfuse[all]' # the whole suite in one command
70
68
  specfuse init <repo> # scaffold .specfuse/ + wire .claude/ (--dry-run previews)
71
69
  specfuse upgrade <repo> # overlay a newer scaffold, then pip-upgrade driver + CLI, point at /plugin update
72
70
  ```
73
71
 
74
- > Extras are only re-resolved on a fresh install — to add one to an existing
75
- > install, use `pipx install --force 'specfuse[all]'` (or `pipx inject specfuse
76
- > specfuse-orchestrator specfuse-authoring`). `pipx upgrade` alone won't pull a
77
- > newly-added extra.
72
+ > **`--include-deps` is required for the extras' CLIs.** pipx only exposes the main
73
+ > package's own console scripts; the orchestrator/authoring commands
74
+ > (`specfuse-orchestrator`, `specfuse-poller`, `specfuse-authoring`, …) live in the
75
+ > extra packages, so `--include-deps` is what surfaces them on PATH. Without it the
76
+ > extra is *installed* but its commands aren't linked.
77
+ >
78
+ > **Quote the brackets** — zsh globs them (`'specfuse[all]'`). And extras are only
79
+ > re-resolved on a *fresh* install — to add one to an existing install use
80
+ > `pipx install --force --include-deps 'specfuse[all]'`; `pipx upgrade` alone won't
81
+ > pull a newly-added extra.
78
82
 
79
83
  > A bare `pip install` into a system Python is blocked on PEP-668
80
84
  > externally-managed environments (Debian/Ubuntu, Homebrew). Use `pipx` (then
{specfuse-0.3.0 → specfuse-0.3.2}/README.md RENAMED
@@ -29,20 +29,24 @@ This repo also ships the **`specfuse`** pip package — the umbrella CLI that br
29
29
  the pip-installed driver and this plugin:
30
30
 
31
31
  ```
32
- pipx install specfuse # recommended (CLI app); pulls specfuse-loop too
33
- pipx install 'specfuse[orchestrator]' # + the multi-repo orchestrator
34
- pipx install 'specfuse[authoring]' # + the spec-authoring kit
35
- pipx install 'specfuse[all]' # the whole suite in one command
36
- # gives you: specfuse / specfuse-loop / specfuse-lint (+ the extras' CLIs)
37
- # (quote the brackets — zsh globs them; or: python3 -m pip install 'specfuse[all]')
32
+ pipx install specfuse # driver only; gives specfuse / specfuse-loop / specfuse-lint
33
+ pipx install --include-deps 'specfuse[orchestrator]' # + the multi-repo orchestrator
34
+ pipx install --include-deps 'specfuse[authoring]' # + the spec-authoring kit
35
+ pipx install --include-deps 'specfuse[all]' # the whole suite in one command
38
36
  specfuse init <repo> # scaffold .specfuse/ + wire .claude/ (--dry-run previews)
39
37
  specfuse upgrade <repo> # overlay a newer scaffold, then pip-upgrade driver + CLI, point at /plugin update
40
38
  ```
41
39
 
42
- > Extras are only re-resolved on a fresh install — to add one to an existing
43
- > install, use `pipx install --force 'specfuse[all]'` (or `pipx inject specfuse
44
- > specfuse-orchestrator specfuse-authoring`). `pipx upgrade` alone won't pull a
45
- > newly-added extra.
40
+ > **`--include-deps` is required for the extras' CLIs.** pipx only exposes the main
41
+ > package's own console scripts; the orchestrator/authoring commands
42
+ > (`specfuse-orchestrator`, `specfuse-poller`, `specfuse-authoring`, …) live in the
43
+ > extra packages, so `--include-deps` is what surfaces them on PATH. Without it the
44
+ > extra is *installed* but its commands aren't linked.
45
+ >
46
+ > **Quote the brackets** — zsh globs them (`'specfuse[all]'`). And extras are only
47
+ > re-resolved on a *fresh* install — to add one to an existing install use
48
+ > `pipx install --force --include-deps 'specfuse[all]'`; `pipx upgrade` alone won't
49
+ > pull a newly-added extra.
46
50
 
47
51
  > A bare `pip install` into a system Python is blocked on PEP-668
48
52
  > externally-managed environments (Debian/Ubuntu, Homebrew). Use `pipx` (then
{specfuse-0.3.0 → specfuse-0.3.2}/pyproject.toml RENAMED
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "specfuse"
7
- version = "0.3.0"
7
+ version = "0.3.2"
8
8
  description = "Specfuse umbrella CLI — bridges the pip-installed driver and the Claude Code plugin (init / upgrade)."
9
9
  readme = "README.md"
10
10
  requires-python = ">=3.10"
@@ -25,7 +25,7 @@ classifiers = [
25
25
  # `specfuse.loop.scaffold`, which only exists in specfuse-loop 0.3.0+ (added by
26
26
  # FEAT-2026-0026). A 0.2.x driver would import-fail at `specfuse init`.
27
27
  dependencies = [
28
- "specfuse-loop>=0.3.5",
28
+ "specfuse-loop>=0.3.12",
29
29
  ]
30
30
 
31
31
  [project.optional-dependencies]
{specfuse-0.3.0 → specfuse-0.3.2}/specfuse/cli.py RENAMED
@@ -32,7 +32,7 @@ from pathlib import Path
32
32
 
33
33
  from specfuse.loop import scaffold
34
34
 
35
- __version__ = "0.3.0"
35
+ __version__ = "0.3.2"
36
36
 
37
37
  MARKETPLACE = "specfuse/specfuse"
38
38
  PLUGIN = "specfuse@specfuse"
{specfuse-0.3.0 → specfuse-0.3.2/specfuse.egg-info}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: specfuse
3
- Version: 0.3.0
3
+ Version: 0.3.2
4
4
  Summary: Specfuse umbrella CLI — bridges the pip-installed driver and the Claude Code plugin (init / upgrade).
5
5
  Author: Specfuse contributors
6
6
  License: Apache-2.0
@@ -17,7 +17,7 @@ Requires-Python: >=3.10
17
17
  Description-Content-Type: text/markdown
18
18
  License-File: LICENSE
19
19
  License-File: NOTICE
20
- Requires-Dist: specfuse-loop>=0.3.5
20
+ Requires-Dist: specfuse-loop>=0.3.12
21
21
  Provides-Extra: dev
22
22
  Requires-Dist: coverage>=7.0; extra == "dev"
23
23
  Requires-Dist: ruff>=0.6; extra == "dev"
@@ -61,20 +61,24 @@ This repo also ships the **`specfuse`** pip package — the umbrella CLI that br
61
61
  the pip-installed driver and this plugin:
62
62
 
63
63
  ```
64
- pipx install specfuse # recommended (CLI app); pulls specfuse-loop too
65
- pipx install 'specfuse[orchestrator]' # + the multi-repo orchestrator
66
- pipx install 'specfuse[authoring]' # + the spec-authoring kit
67
- pipx install 'specfuse[all]' # the whole suite in one command
68
- # gives you: specfuse / specfuse-loop / specfuse-lint (+ the extras' CLIs)
69
- # (quote the brackets — zsh globs them; or: python3 -m pip install 'specfuse[all]')
64
+ pipx install specfuse # driver only; gives specfuse / specfuse-loop / specfuse-lint
65
+ pipx install --include-deps 'specfuse[orchestrator]' # + the multi-repo orchestrator
66
+ pipx install --include-deps 'specfuse[authoring]' # + the spec-authoring kit
67
+ pipx install --include-deps 'specfuse[all]' # the whole suite in one command
70
68
  specfuse init <repo> # scaffold .specfuse/ + wire .claude/ (--dry-run previews)
71
69
  specfuse upgrade <repo> # overlay a newer scaffold, then pip-upgrade driver + CLI, point at /plugin update
72
70
  ```
73
71
 
74
- > Extras are only re-resolved on a fresh install — to add one to an existing
75
- > install, use `pipx install --force 'specfuse[all]'` (or `pipx inject specfuse
76
- > specfuse-orchestrator specfuse-authoring`). `pipx upgrade` alone won't pull a
77
- > newly-added extra.
72
+ > **`--include-deps` is required for the extras' CLIs.** pipx only exposes the main
73
+ > package's own console scripts; the orchestrator/authoring commands
74
+ > (`specfuse-orchestrator`, `specfuse-poller`, `specfuse-authoring`, …) live in the
75
+ > extra packages, so `--include-deps` is what surfaces them on PATH. Without it the
76
+ > extra is *installed* but its commands aren't linked.
77
+ >
78
+ > **Quote the brackets** — zsh globs them (`'specfuse[all]'`). And extras are only
79
+ > re-resolved on a *fresh* install — to add one to an existing install use
80
+ > `pipx install --force --include-deps 'specfuse[all]'`; `pipx upgrade` alone won't
81
+ > pull a newly-added extra.
78
82
 
79
83
  > A bare `pip install` into a system Python is blocked on PEP-668
80
84
  > externally-managed environments (Debian/Ubuntu, Homebrew). Use `pipx` (then
{specfuse-0.3.0 → specfuse-0.3.2}/specfuse.egg-info/requires.txt RENAMED
@@ -1,4 +1,4 @@
1
- specfuse-loop>=0.3.5
1
+ specfuse-loop>=0.3.12
2
2
 
3
3
  [all]
4
4
  specfuse-orchestrator>=0.3.0
{specfuse-0.3.0 → specfuse-0.3.2}/LICENSE RENAMED
File without changes
{specfuse-0.3.0 → specfuse-0.3.2}/NOTICE RENAMED
File without changes
{specfuse-0.3.0 → specfuse-0.3.2}/setup.cfg RENAMED
File without changes
{specfuse-0.3.0 → specfuse-0.3.2}/specfuse/publish.py RENAMED
File without changes
{specfuse-0.3.0 → specfuse-0.3.2}/tests/test_cli.py RENAMED
File without changes
{specfuse-0.3.0 → specfuse-0.3.2}/tests/test_publish.py RENAMED
File without changes