Expose plan command in specfact-project manifest; update docs and add regression test#256
Expose plan command in specfact-project manifest; update docs and add regression test#256djm81 wants to merge 2 commits into
plan command in specfact-project manifest; update docs and add regression test#256Conversation
📝 WalkthroughPR
|
| Cohort / File(s) | Summary |
|---|---|
Documentation Updates docs/guides/marketplace.md, docs/reference/module-categories.md |
Updated bundle documentation to remove deprecated migrate command and add plan command to the project bundle's command list. |
Manifest Configuration packages/specfact-project/module-package.yaml |
Added plan to the commands list alongside project, updated version to 0.41.9, removed category and bundle_group_command metadata fields, and updated integrity checksums. |
Regression Test tests/unit/test_specfact_project_manifest_commands.py |
New unit test validating that the specfact-project manifest includes both project and plan command entries. |
Change Tracking & Specification openspec/CHANGE_ORDER.md, openspec/changes/project-02-plan-root-command-fix/* |
Formal change documentation including proposal, design notes, TDD evidence, specification requirements, and task checklist for the plan command fix. |
Estimated code review effort
🎯 2 (Simple) | ⏱️ ~10 minutes
Possibly related issues
- Issue
#255: Directly addressed by addingplanto thespecfact-projectmanifest's command list, enabling thespecfact planCLI command that was previously unavailable despite module installation. - Issue
#532: Related change addressing the same root cause through the same manifest fix and supporting regression test coverage.
Suggested labels
module, documentation, change-proposal
🚥 Pre-merge checks | ✅ 4 | ❌ 1
❌ Failed checks (1 warning)
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Docstring Coverage | Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. | Write docstrings for the functions missing them to satisfy the coverage threshold. |
✅ Passed checks (4 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | Title clearly describes the main changes (exposing plan command, updating docs, adding test) and uses a descriptive format aligned with conventional commits guidance. |
| Description check | ✅ Passed | Description covers motivation, implementation details, testing evidence, and maps well to the provided template with clear section organization and validation steps. |
| Linked Issues check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
✏️ Tip: You can configure your own custom pre-merge checks in the settings.
✨ Finishing Touches
📝 Generate docstrings
- Create stacked PR
- Commit on current branch
🧪 Generate unit tests (beta)
- Create PR with unit tests
- Commit unit tests in branch
codex/fix-specfact-project-module-bug
Review rate limit: 4/5 reviews remaining, refill in 12 minutes.
Comment @coderabbitai help to get the list of available commands and usage tips.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d3dadc18e1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| description: Official SpecFact project bundle package. | ||
| category: project | ||
| bundle_group_command: project | ||
| integrity: |
There was a problem hiding this comment.
This change drops bundle_group_command from the specfact-project manifest, but repo validation still treats that field as required (tools/validate_repo_manifests.py defines it in REQUIRED_KEYS). In contexts where YAML validation runs (e.g., hatch run yaml-lint via pre-commit/CI), this manifest now fails with a missing-key error, and any workflow expecting bundle-group metadata cannot rely on this package manifest anymore.
Useful? React with 👍 / 👎.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
packages/specfact-project/module-package.yaml (1)
1-30:⚠️ Potential issue | 🔴 CriticalRestore the required manifest metadata.
This manifest now omits
bundle_group_command, buttools/validate_repo_manifests.pystill treats that field as required, so validation will fail unless the validator is updated in the same PR. Theplancommand addition is fine; the missing metadata field needs to stay.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/specfact-project/module-package.yaml` around lines 1 - 30, Restore the missing required manifest field "bundle_group_command" in the package manifest (module-package.yaml); add the bundle_group_command entry back alongside the existing commands (e.g., matching the package's group/category or the existing "project"/"plan" semantics) so tools/validate_repo_manifests.py continues to pass validation, ensuring the key name is exactly "bundle_group_command" and populated with the same kind of value other official bundles use.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@openspec/changes/project-02-plan-root-command-fix/proposal.md`:
- Around line 1-9: Change the first heading "Why" from H2 to H1 (use a single
leading #) and ensure there is a blank line before and after each top-level
section heading ("Why", "What Changes", and "Impact") to satisfy markdownlint
MD041/MD022; update the proposal headings so they are separated by single empty
lines and the first heading is H1.
In `@openspec/changes/project-02-plan-root-command-fix/TDD_EVIDENCE.md`:
- Around line 4-5: Update the TDD_EVIDENCE.md to capture the true regression:
install the nold-ai/specfact-project bundle in the test workspace (instead of
showing "module not installed"), reproduce the failing symptom where the
installed bundle's metadata does not expose or delegate the root "plan" command,
and include a runtime verification step that runs `specfact plan --help`
(showing the missing/delegated output) to confirm the root plan command fails to
render; ensure the failing-before section explicitly states
"nold-ai/specfact-project installed but plan not delegated by registry" and
includes the exact CLI output from the verification run.
- Around line 3-21: The markdown headings in TDD_EVIDENCE.md (specifically the
headings "Failing-before evidence", "Implementation changes", "Passing-after
evidence", "Tooling verification", and "Runtime validation with linked local
module") lack surrounding blank lines and trigger markdownlint MD022; edit that
file to ensure there is a single blank line before and after each of those
headings so each heading is separated from surrounding content (i.e.,
insert/ensure an empty line above and below each of those heading lines).
---
Outside diff comments:
In `@packages/specfact-project/module-package.yaml`:
- Around line 1-30: Restore the missing required manifest field
"bundle_group_command" in the package manifest (module-package.yaml); add the
bundle_group_command entry back alongside the existing commands (e.g., matching
the package's group/category or the existing "project"/"plan" semantics) so
tools/validate_repo_manifests.py continues to pass validation, ensuring the key
name is exactly "bundle_group_command" and populated with the same kind of value
other official bundles use.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 298453e6-9dc7-4a61-bb97-75849dbb1619
📒 Files selected for processing (10)
docs/guides/marketplace.mddocs/reference/module-categories.mdopenspec/CHANGE_ORDER.mdopenspec/changes/project-02-plan-root-command-fix/TDD_EVIDENCE.mdopenspec/changes/project-02-plan-root-command-fix/design.mdopenspec/changes/project-02-plan-root-command-fix/proposal.mdopenspec/changes/project-02-plan-root-command-fix/specs/project-command-surface/spec.mdopenspec/changes/project-02-plan-root-command-fix/tasks.mdpackages/specfact-project/module-package.yamltests/unit/test_specfact_project_manifest_commands.py
📜 Review details
🧰 Additional context used
📓 Path-based instructions (5)
openspec/**/*.md
⚙️ CodeRabbit configuration file
openspec/**/*.md: Specification truth: proposal/tasks/spec deltas vs. bundle behavior, CHANGE_ORDER, and
drift vs. shipped modules or docs.
Files:
openspec/changes/project-02-plan-root-command-fix/tasks.mdopenspec/CHANGE_ORDER.mdopenspec/changes/project-02-plan-root-command-fix/specs/project-command-surface/spec.mdopenspec/changes/project-02-plan-root-command-fix/design.mdopenspec/changes/project-02-plan-root-command-fix/proposal.mdopenspec/changes/project-02-plan-root-command-fix/TDD_EVIDENCE.md
docs/**/*.md
⚙️ CodeRabbit configuration file
docs/**/*.md: User-facing and cross-site accuracy: Jekyll front matter, links per documentation-url-contract,
CLI examples matching bundled commands.
Files:
docs/reference/module-categories.mddocs/guides/marketplace.md
**/*.{js,ts,tsx,jsx,py,java,cs,go,rb,php,cpp,c,h}
📄 CodeRabbit inference engine (CLAUDE.md)
Preserve the clean-code compliance gate and its category references (naming, kiss, yagni, dry, and solid)
Files:
tests/unit/test_specfact_project_manifest_commands.py
tests/**/*.py
⚙️ CodeRabbit configuration file
tests/**/*.py: Contract-first and integration tests: migration suites, bundle validation, and flakiness.
Ensure changes to adapters or bridges have targeted coverage.
Files:
tests/unit/test_specfact_project_manifest_commands.py
packages/**/module-package.yaml
⚙️ CodeRabbit configuration file
packages/**/module-package.yaml: Validate metadata: name, version, commands, dependencies, and parity with packaged src.
Call out semver and signing implications when manifests or payloads change.
Files:
packages/specfact-project/module-package.yaml
🧠 Learnings (6)
📚 Learning: 2026-04-13T10:38:43.535Z
Learnt from: CR
Repo: nold-ai/specfact-cli-modules PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-13T10:38:43.535Z
Learning: Perform `spec -> tests -> failing evidence -> code -> passing evidence` in that order for behavior changes
Applied to files:
openspec/changes/project-02-plan-root-command-fix/tasks.mdopenspec/changes/project-02-plan-root-command-fix/TDD_EVIDENCE.md
📚 Learning: 2026-04-13T10:38:29.399Z
Learnt from: CR
Repo: nold-ai/specfact-cli-modules PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-13T10:38:29.399Z
Learning: When a change is paired with work in specfact-cli, review the paired public change artifacts there before widening scope or redefining shared workflow semantics
Applied to files:
openspec/changes/project-02-plan-root-command-fix/tasks.mdopenspec/CHANGE_ORDER.md
📚 Learning: 2026-04-13T10:38:22.848Z
Learnt from: CR
Repo: nold-ai/specfact-cli-modules PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2026-04-13T10:38:22.848Z
Learning: This repository enforces the clean-code review gate through hatch run specfact code review run --json --out .specfact/code-review.json
Applied to files:
openspec/changes/project-02-plan-root-command-fix/tasks.mddocs/reference/module-categories.md
📚 Learning: 2026-04-13T10:38:22.848Z
Learnt from: CR
Repo: nold-ai/specfact-cli-modules PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2026-04-13T10:38:22.848Z
Learning: Work belongs on feature/*, bugfix/*, hotfix/*, or chore/* branches, normally in a worktree rooted under ../specfact-cli-modules-worktrees/
Applied to files:
docs/reference/module-categories.mdopenspec/CHANGE_ORDER.mddocs/guides/marketplace.md
📚 Learning: 2026-04-13T10:38:22.848Z
Learnt from: CR
Repo: nold-ai/specfact-cli-modules PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2026-04-13T10:38:22.848Z
Learning: Refresh .specfact/backlog/github_hierarchy_cache.md with python scripts/sync_github_hierarchy_cache.py when GitHub hierarchy metadata is missing or stale before parent or blocker work
Applied to files:
docs/reference/module-categories.md
📚 Learning: 2026-04-13T10:38:43.535Z
Learnt from: CR
Repo: nold-ai/specfact-cli-modules PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-13T10:38:43.535Z
Learning: If GitHub hierarchy metadata is needed and `.specfact/backlog/github_hierarchy_cache.md` is missing or stale, refresh it with `python scripts/sync_github_hierarchy_cache.py`
Applied to files:
docs/reference/module-categories.md
🪛 markdownlint-cli2 (0.22.1)
openspec/changes/project-02-plan-root-command-fix/tasks.md
[warning] 1-1: First line in a file should be a top-level heading
(MD041, first-line-heading, first-line-h1)
openspec/changes/project-02-plan-root-command-fix/specs/project-command-surface/spec.md
[warning] 1-1: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 1-1: First line in a file should be a top-level heading
(MD041, first-line-heading, first-line-h1)
[warning] 2-2: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Above
(MD022, blanks-around-headings)
[warning] 2-2: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 5-5: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
openspec/changes/project-02-plan-root-command-fix/design.md
[warning] 1-1: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 1-1: First line in a file should be a top-level heading
(MD041, first-line-heading, first-line-h1)
openspec/changes/project-02-plan-root-command-fix/proposal.md
[warning] 1-1: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 1-1: First line in a file should be a top-level heading
(MD041, first-line-heading, first-line-h1)
[warning] 4-4: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 9-9: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
openspec/changes/project-02-plan-root-command-fix/TDD_EVIDENCE.md
[warning] 3-3: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 7-7: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 11-11: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 15-15: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 21-21: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🔇 Additional comments (9)
docs/reference/module-categories.md (1)
61-61: Looks aligned with the new command surface.The bundle contents list now includes
plan, which matches the manifest and spec updates.docs/guides/marketplace.md (1)
35-35: Bundle overview stays in sync.Listing
planhere keeps the marketplace docs aligned with the bundle manifest and command surface.openspec/changes/project-02-plan-root-command-fix/tasks.md (1)
1-4: Checklist order is fine.Spec, regression test, implementation/docs, and validation are sequenced sensibly for this change.
openspec/CHANGE_ORDER.md (1)
58-58: Correct module and order slot.The
project-runtime/02entry matches the change scope and dependency context.tests/unit/test_specfact_project_manifest_commands.py (1)
9-14: Good manifest-level regression coverage.This pins the bundle contract directly and should catch future command-surface regressions.
openspec/changes/project-02-plan-root-command-fix/design.md (1)
1-4: Design note matches the fix strategy.The manifest-first delegation explanation is clear and lines up with the regression-test approach.
openspec/changes/project-02-plan-root-command-fix/specs/project-command-surface/spec.md (1)
1-8: Spec captures the right contract.This cleanly constrains the bundle manifest to expose
projectandplan, which is the right observable requirement for the fix.openspec/changes/project-02-plan-root-command-fix/proposal.md (1)
2-7: Good manifest-first framing for the bundle↔core registry boundary.The proposal clearly ties the root cause to missing
commandsmetadata and includes the required manifest/docs/regression-test actions.As per coding guidelines, “When proposing runtime bundle command-surface fixes, tie the root cause to the manifest declaration gap ... then enumerate required actions: update the bundle manifest
commands, update the docs ... and add regression coverage...”.openspec/changes/project-02-plan-root-command-fix/TDD_EVIDENCE.md (1)
8-25: Implementation/passing/runtime evidence is well aligned to module manifest delegation behavior.This captures the manifest change, targeted regression test, quality gates, and linked-module runtime check for
specfact plan --help.As per coding guidelines, “Follow the design rationale that runtime command delegation is driven by
packages/*/module-package.yamlcommands... validated by a regression test that inspects bundle metadata.”
| ## Why | ||
| Issue #255 reports that `specfact plan` is not accessible even when `nold-ai/specfact-project` is installed. The project bundle manifest only declares `project` in `commands`, so runtime command registry never loads the plan delegate. | ||
|
|
||
| ## What Changes | ||
| - Add `plan` to `packages/specfact-project/module-package.yaml` commands list. | ||
| - Update docs that describe project bundle exposed command groups to include plan. | ||
| - Add regression coverage for manifest command declaration. | ||
|
|
||
| ## Impact |
There was a problem hiding this comment.
Fix heading structure to satisfy markdownlint (MD041/MD022).
Line 1 should be an H1, and headings at Line 1, Line 4, and Line 9 need surrounding blank lines.
Suggested markdown fix
-## Why
+# Proposal: project-02-plan-root-command-fix
+
+## Why
+
Issue `#255` reports that `specfact plan` is not accessible even when `nold-ai/specfact-project` is installed. The project bundle manifest only declares `project` in `commands`, so runtime command registry never loads the plan delegate.
## What Changes
+
- Add `plan` to `packages/specfact-project/module-package.yaml` commands list.
- Update docs that describe project bundle exposed command groups to include plan.
- Add regression coverage for manifest command declaration.
## Impact
+
- Affected spec: project-command-surface
- Affected code: packages/specfact-project/module-package.yaml, docs/guides/marketplace.md, docs/reference/module-categories.md, tests
- Tracking: https://github.com/nold-ai/specfact-cli-modules/issues/255🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 1-1: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 1-1: First line in a file should be a top-level heading
(MD041, first-line-heading, first-line-h1)
[warning] 4-4: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 9-9: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@openspec/changes/project-02-plan-root-command-fix/proposal.md` around lines 1
- 9, Change the first heading "Why" from H2 to H1 (use a single leading #) and
ensure there is a blank line before and after each top-level section heading
("Why", "What Changes", and "Impact") to satisfy markdownlint MD041/MD022;
update the proposal headings so they are separated by single empty lines and the
first heading is H1.
| ## Failing-before evidence | ||
| - `specfact plan --help` in a clean temp workspace without installed project module failed with: | ||
| - `Module 'nold-ai/specfact-project' is not installed.` | ||
|
|
||
| ## Implementation changes | ||
| - Added `plan` to `packages/specfact-project/module-package.yaml` `commands` list. | ||
| - Added regression test `tests/unit/test_specfact_project_manifest_commands.py`. | ||
|
|
||
| ## Passing-after evidence | ||
| - `pytest -q tests/unit/test_specfact_project_manifest_commands.py` → **passed**. | ||
| - `./scripts/pre-commit-quality-checks.sh` → **passed** in this environment. | ||
|
|
||
| ## Tooling verification | ||
| - OpenSpec npm install command verified from openspec.dev: | ||
| - `npm install -g @fission-ai/openspec@latest` | ||
| - `openspec --version` returned `1.3.1` after install. | ||
|
|
||
|
|
||
| ## Runtime validation with linked local module |
There was a problem hiding this comment.
Add blank lines around section headings to clear markdownlint MD022.
Headings at Line 3, Line 7, Line 11, Line 15, and Line 21 need surrounding blank lines.
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 3-3: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 7-7: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 11-11: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 15-15: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
[warning] 21-21: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@openspec/changes/project-02-plan-root-command-fix/TDD_EVIDENCE.md` around
lines 3 - 21, The markdown headings in TDD_EVIDENCE.md (specifically the
headings "Failing-before evidence", "Implementation changes", "Passing-after
evidence", "Tooling verification", and "Runtime validation with linked local
module") lack surrounding blank lines and trigger markdownlint MD022; edit that
file to ensure there is a single blank line before and after each of those
headings so each heading is separated from surrounding content (i.e.,
insert/ensure an empty line above and below each of those heading lines).
| - `specfact plan --help` in a clean temp workspace without installed project module failed with: | ||
| - `Module 'nold-ai/specfact-project' is not installed.` |
There was a problem hiding this comment.
Failing-before evidence does not capture the actual regression contract.
Line 4 and Line 5 show “module not installed,” but Issue #255 is about installed bundle metadata not exposing plan. Please record the failing symptom with nold-ai/specfact-project installed but plan not delegated by registry.
Suggested correction
-## Failing-before evidence
-- `specfact plan --help` in a clean temp workspace without installed project module failed with:
- - `Module 'nold-ai/specfact-project' is not installed.`
+## Failing-before evidence
+- With `nold-ai/specfact-project` installed (pre-fix manifest declaring only `project`), `specfact plan --help` failed because the root `plan` delegate was not registered from bundle metadata.As per coding guidelines, “Use this repo’s TDD-evidence pattern: (1) record the failing-before CLI symptom ... and (4) include runtime verification ... running specfact plan --help to confirm the root plan command renders.”
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - `specfact plan --help` in a clean temp workspace without installed project module failed with: | |
| - `Module 'nold-ai/specfact-project' is not installed.` | |
| - With `nold-ai/specfact-project` installed (pre-fix manifest declaring only `project`), `specfact plan --help` failed because the root `plan` delegate was not registered from bundle metadata. |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@openspec/changes/project-02-plan-root-command-fix/TDD_EVIDENCE.md` around
lines 4 - 5, Update the TDD_EVIDENCE.md to capture the true regression: install
the nold-ai/specfact-project bundle in the test workspace (instead of showing
"module not installed"), reproduce the failing symptom where the installed
bundle's metadata does not expose or delegate the root "plan" command, and
include a runtime verification step that runs `specfact plan --help` (showing
the missing/delegated output) to confirm the root plan command fails to render;
ensure the failing-before section explicitly states "nold-ai/specfact-project
installed but plan not delegated by registry" and includes the exact CLI output
from the verification run.
djm81
added
bug
|
Codex requires a new PR due to PR updates. |
1 participant
Motivation
specfact planwas not being routed when thenold-ai/specfact-projectbundle was installed because the bundle manifest did not declare theplancommand group.plandelegate.Description
plantopackages/specfact-project/module-package.yamlcommandslist and bumped the packageversionandintegritychecksum/signature.planas part of the project bundle indocs/guides/marketplace.mdanddocs/reference/module-categories.md.openspec/changes/project-02-plan-root-command-fix/with proposal, design, spec, tasks, and TDD evidence, and updatedopenspec/CHANGE_ORDER.md.tests/unit/test_specfact_project_manifest_commands.pythat asserts the manifest contains bothprojectandplan.Testing
pytest -q tests/unit/test_specfact_project_manifest_commands.pyand the test passed../scripts/pre-commit-quality-checks.shand the pre-commit quality checks passed.Codex Task