pactkit 2.9.1__tar.gz → 2.9.2__tar.gz

{pactkit-2.9.1 → pactkit-2.9.2}/.github/workflows/pactkit.yml

@@ -20,7 +20,7 @@ jobs:
       - name: Install dependencies
         run: |
           python -m pip install --upgrade pip
-          pip install -e ".[dev]" || pip install -e .
+          pip install -e ".[multilang]"
           pip install pytest ruff
           pactkit init
 

{pactkit-2.9.1 → pactkit-2.9.2}/.opencode/pactkit.yaml

@@ -1,81 +1,16 @@
 # PactKit Configuration
-# Edit this file to customize which components are deployed.
-# Remove items from a list to disable them. Default: all enabled.
+# All agents, commands, skills, and rules are deployed by default.
+# To exclude specific items, add an exclude list (e.g., exclude_skills: [pactkit-draw]).
 
 version: "2.9.1"
 stack: python
 root: .
 developer: "slim"
 
-# Agents — AI role definitions
-agents:
-  - code-explorer
-  - product-designer
-  - qa-engineer
-  - repo-maintainer
-  - security-auditor
-  - senior-developer
-  - system-architect
-  - system-medic
-  - visual-architect
-
-# Commands — PDCA playbooks
-commands:
-  - project-act
-  - project-check
-  - project-clarify
-  - project-design
-  - project-done
-  - project-hotfix
-  - project-init
-  - project-plan
-  - project-pr
-  - project-release
-  - project-sprint
-
-# Skills — tool scripts
-skills:
-  - pactkit-analyze
-  - pactkit-board
-  - pactkit-doctor
-  - pactkit-draw
-  - pactkit-release
-  - pactkit-review
-  - pactkit-scaffold
-  - pactkit-status
-  - pactkit-trace
-  - pactkit-visualize
-  - project-act
-  - project-check
-  - project-clarify
-  - project-design
-  - project-done
-  - project-hotfix
-  - project-init
-  - project-plan
-  - project-pr
-  - project-release
-  - project-sprint
-
-# Rules — constitution modules
-rules:
-  - 01-core-protocol
-  - 02-hierarchy-of-truth
-  - 03-file-atlas
-  - 04-routing-table
-  - 05-workflow-conventions
-  - 06-mcp-integration
-  - 07-shared-protocols
-  - 08-architecture-principles
-  - 09-sectional-write
-
 # CI/CD — set provider to github or gitlab to generate pipeline config
 ci:
   provider: github
-  # runner: ubuntu-latest
-  # language_version: "3.11"
-  # github_host: ""  # GHE server (empty = github.com)
-  # actions_ref: ""  # GHE actions prefix
+  install_cmd: "python -m pip install --upgrade pip\n          pip install -e \".[multilang]\"\n          pip install pytest ruff\n          pactkit init"
 
 # Issue Tracker — set provider to github to link stories to issues
 issue_tracker:

{pactkit-2.9.1 → pactkit-2.9.2}/CHANGELOG.md

@@ -4,6 +4,13 @@ All notable changes to PactKit will be documented in this file.
 
 Format follows [Keep a Changelog](https://keepachangelog.com/).
 
+## [2.9.2] - 2026-03-30
+
+### Fixed
+- **FormatProfile.excluded_commands** — `project-sprint` excluded for OpenCode/Codex (requires subagent team, Claude Code only). Doctor `check_config_drift` now respects format-level exclusions.
+- **Redundant pactkit.yaml component lists** — Removed explicit agents/commands/skills/rules lists from `.opencode/pactkit.yaml` (absence = deploy all).
+- **Orphaned spec cleanup** — Removed 7 pre-developer-prefix spec files that were already archived under old IDs.
+
 ## [2.9.1] - 2026-03-30
 
 ### Added

{pactkit-2.9.1 → pactkit-2.9.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pactkit
-Version: 2.9.1
+Version: 2.9.2
 Summary: Spec-driven agentic DevOps toolkit for AI coding assistants
 Project-URL: Homepage, https://pactkit.dev
 Project-URL: Repository, https://github.com/pactkit/pactkit-public

{pactkit-2.9.1 → pactkit-2.9.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "pactkit"
-version = "2.9.1"
+version = "2.9.2"
 description = "Spec-driven agentic DevOps toolkit for AI coding assistants"
 readme = "README.md"
 license = "MIT"

{pactkit-2.9.1 → pactkit-2.9.2}/src/pactkit/__init__.py

@@ -1,3 +1,3 @@
 """PactKit - Spec-driven agentic DevOps toolkit."""
 
-__version__ = "2.9.1"
+__version__ = "2.9.2"

{pactkit-2.9.1 → pactkit-2.9.2}/src/pactkit/doctor.py

@@ -76,6 +76,18 @@ def check_config_drift(project_root: Path) -> dict:
     config_dir = yaml_path.parent  # .claude/ or .opencode/ or .codex/
     missing: list[dict] = []
 
+    # Detect format from yaml path to get format-level excluded commands
+    _format_excluded_commands: frozenset = frozenset()
+    try:
+        from pactkit.profiles import FORMAT_PROFILES
+        dir_name = config_dir.name  # e.g. ".claude", ".opencode", ".codex"
+        for prof in FORMAT_PROFILES.values():
+            if prof.project_config_dir == dir_name:
+                _format_excluded_commands = prof.excluded_commands
+                break
+    except Exception:
+        pass
+
     # Files are deployed globally (e.g., ~/.claude/, ~/.config/opencode/, ~/.codex/),
     # not per-project. Check all known global deploy directories + project-local.
     home = Path.home()
@@ -110,6 +122,9 @@ def check_config_drift(project_root: Path) -> dict:
         if not isinstance(declared, list):
             continue
         for item in declared:
+            # Skip format-level excluded commands (e.g., project-sprint for opencode/codex)
+            if key == "commands" and item in _format_excluded_commands:
+                continue
             if not _exists_in_any(subdir, f"{item}{suffix}"):
                 missing.append({"type": key.rstrip("s"), "name": item})
 
@@ -117,6 +132,9 @@ def check_config_drift(project_root: Path) -> dict:
     declared_skills = data.get("skills")
     if isinstance(declared_skills, list):
         for skill in declared_skills:
+            # Skip format-level excluded commands deployed as skills
+            if skill in _format_excluded_commands:
+                continue
             if not _dir_or_file_in_any("skills", skill):
                 missing.append({"type": "skill", "name": skill})
 

{pactkit-2.9.1 → pactkit-2.9.2}/src/pactkit/profiles.py

@@ -88,6 +88,10 @@ class FormatProfile:
     excluded_agent_fields: frozenset
     """Agent YAML fields to exclude for this format. Replaces CLAUDE_ONLY_FIELDS."""
 
+    # Exclusions
+    excluded_commands: frozenset
+    """Commands not applicable to this format (e.g., project-sprint needs subagent team)."""
+
     # Capabilities
     has_custom_commands: bool
     """Whether the tool supports custom slash commands."""
@@ -121,6 +125,7 @@ FORMAT_PROFILES: dict[str, FormatProfile] = {
         agent_format="md",
         rules_import_style="@import",
         excluded_agent_fields=frozenset(),  # Classic: include all fields
+        excluded_commands=frozenset(),  # Classic: all commands supported
         has_custom_commands=True,
         supports_model_routing=False,
         supports_mcp=True,
@@ -141,6 +146,7 @@ FORMAT_PROFILES: dict[str, FormatProfile] = {
         agent_format="md",
         rules_import_style="instructions",
         excluded_agent_fields=frozenset({"permissionMode", "memory", "skills"}),
+        excluded_commands=frozenset({"project-sprint"}),
         has_custom_commands=True,
         supports_model_routing=True,
         supports_mcp=True,
@@ -161,6 +167,7 @@ FORMAT_PROFILES: dict[str, FormatProfile] = {
         agent_format="md",
         rules_import_style="inline",
         excluded_agent_fields=frozenset({"permissionMode", "memory", "skills", "hooks"}),
+        excluded_commands=frozenset({"project-sprint"}),
         has_custom_commands=True,
         supports_model_routing=False,
         supports_mcp=True,

pactkit-2.9.1/docs/specs/BUG-slim-007.md

@@ -1,138 +0,0 @@
-# BUG-slim-007: W007 substring matching causes false negatives and inconsistency
-
-| Field | Value |
-|-------|-------|
-| ID | BUG-slim-007 |
-| Status | Draft |
-| Priority | P1 |
-| Release | 2.3.6 |
-| Origin | Cross-model code review (2026-03-24) |
-
-## Background
-
-W007 (Req-AC coverage check) was introduced in STORY-slim-024 (v2.3.4) and patched in v2.3.5 to use `SPEC_RFC_KEYWORDS` instead of hardcoded `SHOULD`. Code review found that the implementation uses Python `in` (substring) matching in two places where word-boundary regex is required, plus a pattern divergence from the canonical source.
-
-### Bug 1: R{N} coverage check — substring false negative
-
-`spec_linter.py:241`:
-```python
-if req_id.lower() not in ac_lower:
-```
-
-When AC section mentions `R10`, the string `"r1"` is a substring of `"r10"` — so `R1` is falsely reported as covered. Similarly `"r1" in "r12"`, `"r2" in "r20"`, etc. Also non-R prefixed text like `"CR1"`, `"ERROR1"`, `"PR1"` would suppress W007 for `R1`.
-
-**Impact**: Any spec with 10+ requirements silently passes W007 for R1-R9 when R10+ exists in AC. This directly undermines W007's purpose.
-
-### Bug 2: RFC keyword detection — substring inconsistency with W003
-
-`spec_linter.py:244`:
-```python
-found_keyword = next((kw for kw in SPEC_RFC_KEYWORDS if kw in req_upper), None)
-```
-
-W003 at line 172 uses `_RFC2119.search(body)` which is `SPEC_RFC_PATTERN` — a compiled regex with `\b` word boundaries. W007 uses plain `kw in req_upper` (substring). This means `"MAYONNAISE"` matches `MAY`, `"SHALLOW"` matches `SHALL`, etc.
-
-Two rules in the same file detecting RFC 2119 keywords with different strategies is a consistency violation.
-
-### Bug 3: _REQ_ID_PATTERN diverges from SPEC_REQUIREMENT_PATTERN
-
-`spec_linter.py:203`:
-```python
-_REQ_ID_PATTERN = re.compile(r"###\s+(R\d+)[:\s]", re.MULTILINE)
-```
-
-`schemas.py:32`:
-```python
-SPEC_REQUIREMENT_PATTERN = r"### R\d+[:\s]"
-```
-
-E004 uses `SPEC_REQUIREMENT_PATTERN` (literal single space after `###`), while W007 uses `_REQ_ID_PATTERN` (`\s+` — allows tab, multiple spaces). A heading `###  R1:` (double space) would be found by W007 but missed by E004. Both patterns should derive from the same canonical source.
-
-## Requirements
-
-### R1: Word-boundary matching for R{N} coverage (MUST)
-
-W007 MUST use word-boundary regex to check whether an R{N} ID appears in the AC section. `R1` MUST NOT match `R10`, `R12`, `CR1`, `ERROR1`, or any other superstring.
-
-Pattern: `re.search(rf"\b{req_id}\b", ac_section, re.IGNORECASE)`
-
-### R2: Word-boundary matching for RFC 2119 keywords (MUST)
-
-W007's RFC 2119 keyword detection MUST use `SPEC_RFC_PATTERN` (from `schemas.py`) — the same compiled regex with `\b` word boundaries that W003 already uses. `MAY` MUST NOT match `MAYONNAISE`.
-
-### R3: _REQ_ID_PATTERN MUST derive from SPEC_REQUIREMENT_PATTERN (SHOULD)
-
-`_REQ_ID_PATTERN` SHOULD be constructed from `SPEC_REQUIREMENT_PATTERN` or share the same whitespace semantics, so that E004 and W007 agree on what constitutes a valid `### R{N}` heading.
-
-If intentional divergence is needed (e.g., W007 is more tolerant), document the reason inline.
-
-### R4: Test coverage for multi-digit R{N} (MUST)
-
-Tests MUST include a spec with R1 through R10+ where only R10 is referenced in AC, to verify R1 is correctly flagged as uncovered.
-
-### R5: Test coverage for all 7 RFC 2119 keywords (SHOULD)
-
-Tests SHOULD cover all 7 keywords from `SPEC_RFC_KEYWORDS`, not just MUST/SHOULD/MAY. Tests SHOULD also cover the no-keyword case (empty emphasis).
-
-## Acceptance Criteria
-
-### AC1: R1 not falsely covered by R10 (R1, R4)
-
-- **Given** a spec with `### R1: First` and `### R10: Tenth` in Requirements
-- **When** AC section mentions only `R10` (not `R1`)
-- **Then** W007 fires for R1 with message "Requirement R1 has no corresponding AC reference"
-- **And** W007 does NOT fire for R10
-
-### AC2: Non-R prefix text does not suppress W007 (R1)
-
-- **Given** a spec with `### R1: Something` in Requirements
-- **When** AC section contains `ERROR1` or `CR1` but not standalone `R1`
-- **Then** W007 fires for R1
-
-### AC3: RFC keyword word-boundary (R2)
-
-- **Given** a spec with unreferenced `### R1: The system MAYONNAISE handler`
-- **When** spec linter runs
-- **Then** W007 message does NOT contain `(MAY)` — substring `MAY` inside `MAYONNAISE` is not a match
-- **And** emphasis is empty (no RFC keyword found)
-
-### AC4: All 7 RFC keywords detected (R2, R5)
-
-- **Given** specs with unreferenced requirements containing each of: MUST, SHOULD, MAY, SHALL, REQUIRED, RECOMMENDED, OPTIONAL
-- **When** spec linter runs
-- **Then** each W007 message contains the correct keyword in parentheses: `(MUST)`, `(SHOULD)`, etc.
-
-### AC5: W003 and W007 use same detection mechanism (R2)
-
-- **Given** the spec_linter.py source code
-- **When** inspecting both W003 and W007 RFC 2119 detection
-- **Then** both use `SPEC_RFC_PATTERN` (or `_RFC2119` alias) for matching — no plain `kw in string`
-
-### AC6: Existing tests still pass (regression)
-
-- **Given** all pre-existing tests in test_story_slim024.py and test_story042_spec_linter.py
-- **When** running the full test suite
-- **Then** all tests pass — no regressions from word-boundary change
-
-## Implementation Steps
-
-| Step | File | Action | Dependencies | Risk |
-|------|------|--------|-------------|------|
-| 1 | `src/pactkit/skills/spec_linter.py:241` | Replace `req_id.lower() not in ac_lower` with `re.search(rf"\b{re.escape(req_id)}\b", ac_section, re.IGNORECASE)` | None | Low |
-| 2 | `src/pactkit/skills/spec_linter.py:244` | Replace `next((kw for kw in SPEC_RFC_KEYWORDS if kw in req_upper), None)` with `SPEC_RFC_PATTERN.search(req_body)` using match group | Step 1 | Low |
-| 3 | `src/pactkit/skills/spec_linter.py:203` | Add inline comment documenting why `_REQ_ID_PATTERN` uses `\s+` vs `SPEC_REQUIREMENT_PATTERN`'s literal space, or unify | None | Low |
-| 4 | `tests/unit/test_story_slim024.py` | Add R10 multi-digit test (AC1), non-R-prefix test (AC2), MAYONNAISE test (AC3), all-7-keywords test (AC4), no-keyword test (AC5 empty emphasis) | Steps 1-2 | Low |
-| 5 | `tests/unit/test_story_slim024.py` | Migrate from `tempfile.NamedTemporaryFile(delete=False)` to pytest `tmp_path` fixture (consistency with test_story042) | None | Low |
-
-## Security Scope
-
-| Check | Applicable | Reason |
-|-------|------------|--------|
-| SEC-1~8 | No | Lint rule logic change, no I/O or auth |
-
-## Out of Scope
-
-- `_section_text()` returning heading line (fragile but extremely unlikely to cause false suppression)
-- Sectional write rule 150 vs 300 inconsistency in `rules.py:359` (trivial fix, separate commit)
-- `config.py:961` api_spec empty string default (docs already fixed, code default is cosmetic)
-- Board archive section ordering (functional, not a bug)