raise-cli 2.2.1__py3-none-any.whl

raise_cli/publish/version.py

@@ -0,0 +1,172 @@
+"""Version parsing, validation, and bumping for PEP 440 compliance."""
+
+from __future__ import annotations
+
+import re
+from dataclasses import dataclass
+from pathlib import Path
+from typing import Literal
+
+# PEP 440 pattern: N.N.N[{a|b|rc}N]
+_PEP440_RE = re.compile(
+    r"^(?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)"
+    r"(?:(?P<pre_type>a|b|rc)(?P<pre_num>\d+))?$"
+)
+
+BumpType = Literal["major", "minor", "patch", "alpha", "beta", "rc", "release"]
+
+
+@dataclass(frozen=True)
+class VersionInfo:
+    """Parsed PEP 440 version."""
+
+    major: int
+    minor: int
+    patch: int
+    pre_type: str | None = None
+    pre_num: int | None = None
+
+    def __str__(self) -> str:
+        base = f"{self.major}.{self.minor}.{self.patch}"
+        if self.pre_type is not None and self.pre_num is not None:
+            return f"{base}{self.pre_type}{self.pre_num}"
+        return base
+
+    @property
+    def is_prerelease(self) -> bool:
+        """Check if this is a pre-release version."""
+        return self.pre_type is not None
+
+
+def is_pep440(version: str) -> bool:
+    """Check if a version string is PEP 440 compliant.
+
+    Args:
+        version: Version string to validate.
+
+    Returns:
+        True if the version is valid PEP 440.
+    """
+    return _PEP440_RE.match(version) is not None
+
+
+def parse_version(version: str) -> VersionInfo:
+    """Parse a PEP 440 version string into components.
+
+    Args:
+        version: Version string to parse.
+
+    Returns:
+        Parsed version info.
+
+    Raises:
+        ValueError: If the version is not valid PEP 440.
+    """
+    match = _PEP440_RE.match(version)
+    if not match:
+        msg = f"'{version}' is not a valid PEP 440 version"
+        raise ValueError(msg)
+
+    pre_type = match.group("pre_type")
+    pre_num_str = match.group("pre_num")
+
+    return VersionInfo(
+        major=int(match.group("major")),
+        minor=int(match.group("minor")),
+        patch=int(match.group("patch")),
+        pre_type=pre_type,
+        pre_num=int(pre_num_str) if pre_num_str is not None else None,
+    )
+
+
+def bump_version(current: str, bump_type: BumpType) -> str:
+    """Bump a version string according to the bump type.
+
+    Args:
+        current: Current version string (must be PEP 440 compliant).
+        bump_type: Type of bump to apply.
+
+    Returns:
+        New version string.
+
+    Raises:
+        ValueError: If the current version is not valid PEP 440.
+    """
+    v = parse_version(current)
+
+    if bump_type == "major":
+        return str(VersionInfo(major=v.major + 1, minor=0, patch=0))
+
+    if bump_type == "minor":
+        return str(VersionInfo(major=v.major, minor=v.minor + 1, patch=0))
+
+    if bump_type == "patch":
+        return str(VersionInfo(major=v.major, minor=v.minor, patch=v.patch + 1))
+
+    if bump_type == "alpha":
+        if v.pre_type == "a":
+            return str(
+                VersionInfo(v.major, v.minor, v.patch, "a", (v.pre_num or 0) + 1)
+            )
+        # From stable or other pre-release: next patch alpha
+        if v.pre_type is None:
+            return str(VersionInfo(v.major, v.minor, v.patch + 1, "a", 1))
+        return str(VersionInfo(v.major, v.minor, v.patch, "a", 1))
+
+    if bump_type == "beta":
+        if v.pre_type == "b":
+            return str(
+                VersionInfo(v.major, v.minor, v.patch, "b", (v.pre_num or 0) + 1)
+            )
+        return str(VersionInfo(v.major, v.minor, v.patch, "b", 1))
+
+    if bump_type == "rc":
+        if v.pre_type == "rc":
+            return str(
+                VersionInfo(v.major, v.minor, v.patch, "rc", (v.pre_num or 0) + 1)
+            )
+        return str(VersionInfo(v.major, v.minor, v.patch, "rc", 1))
+
+    # bump_type == "release"
+    return str(VersionInfo(v.major, v.minor, v.patch))
+
+
+def sync_version_files(
+    new_version: str,
+    *,
+    pyproject_path: Path,
+    init_path: Path,
+) -> None:
+    """Update version in pyproject.toml and __init__.py.
+
+    Args:
+        new_version: New version string (must be PEP 440 compliant).
+        pyproject_path: Path to pyproject.toml.
+        init_path: Path to __init__.py.
+
+    Raises:
+        ValueError: If the new version is not valid PEP 440.
+    """
+    if not is_pep440(new_version):
+        msg = f"'{new_version}' is not a valid PEP 440 version"
+        raise ValueError(msg)
+
+    # Update pyproject.toml
+    pyproject_content = pyproject_path.read_text(encoding="utf-8")
+    pyproject_content = re.sub(
+        r'version\s*=\s*"[^"]*"',
+        f'version = "{new_version}"',
+        pyproject_content,
+        count=1,
+    )
+    pyproject_path.write_text(pyproject_content, encoding="utf-8")
+
+    # Update __init__.py
+    init_content = init_path.read_text(encoding="utf-8")
+    init_content = re.sub(
+        r'__version__\s*=\s*"[^"]*"',
+        f'__version__ = "{new_version}"',
+        init_content,
+        count=1,
+    )
+    init_path.write_text(init_content, encoding="utf-8")

raise_cli/rai_base/__init__.py

@@ -0,0 +1,22 @@
+"""Base Rai package for distribution.
+
+This package contains the base identity, patterns, and methodology
+that ship with raise-cli. On `raise init`, these files are copied
+to the project's `.raise/rai/` directory.
+
+Contents:
+    identity/       Base identity files (core.md, perspective.md)
+    memory/         Base patterns (patterns-base.jsonl) [F14.2]
+    framework/      Methodology definition (methodology.yaml) [F14.3]
+
+Usage:
+    from importlib.resources import files
+
+    base_files = files("raise_cli.rai_base")
+    identity_dir = base_files / "identity"
+    core_md = (identity_dir / "core.md").read_text(encoding="utf-8")
+"""
+
+from __future__ import annotations
+
+__version__ = "1.0.0"

raise_cli/rai_base/framework/__init__.py

@@ -0,0 +1,7 @@
+"""Base framework files for distribution.
+
+Contains:
+    methodology.yaml  Skills, gates, and process rules
+"""
+
+from __future__ import annotations

raise_cli/rai_base/framework/methodology.yaml

@@ -0,0 +1,233 @@
+# RaiSE Methodology Definition
+# Used to generate MEMORY.md Part 1 (static process knowledge)
+version: 1
+
+# =============================================================================
+# Work Lifecycle
+# =============================================================================
+lifecycle:
+  epic:
+    phases: [start, design, plan, implement, close]
+    flow: "/rai-epic-start → /rai-epic-design → /rai-epic-plan → [stories] → /rai-epic-close"
+
+  story:
+    phases: [start, design, plan, implement, review, close]
+    flow: "/rai-story-start → /rai-story-design* → /rai-story-plan → /rai-story-implement → /rai-story-review → /rai-story-close"
+    note: "*design optional for S/XS stories"
+
+  session:
+    phases: [start, work, close]
+    flow: "/rai-session-start → [work] → /rai-session-close"
+
+# =============================================================================
+# Skills by Category
+# =============================================================================
+skills:
+  session:
+    - name: /rai-session-start
+      purpose: Load memory, analyze progress, propose focused work
+      when: Beginning of any working session
+      adapts_to: Shu/Ha/Ri experience level
+
+    - name: /rai-session-close
+      purpose: Capture learnings, update memory, log session
+      when: End of working session
+      creates: Session record, pattern updates
+
+  epic:
+    - name: /rai-epic-start
+      purpose: Initialize epic scope and directory structure
+      when: Starting a new epic
+      creates: Epic directory, scope document, tracker entry
+
+    - name: /rai-epic-design
+      purpose: Design epic scope, stories, architecture
+      when: After epic initialized
+      creates: Epic scope document with story breakdown
+
+    - name: /rai-epic-plan
+      purpose: Sequence stories with milestones and dependencies
+      when: After epic design approved
+      creates: Implementation roadmap
+
+    - name: /rai-epic-close
+      purpose: Epic retrospective, metrics capture, tracking update
+      when: All stories complete
+      creates: Retrospective, tracking update
+
+  story:
+    - name: /rai-story-start
+      purpose: Create story branch and scope commit
+      when: Starting a new story
+      creates: Story branch from dev, scope documentation
+
+    - name: /rai-story-design
+      purpose: Create lean specification for complex stories
+      when: Story has >3 components or needs architectural decisions
+      creates: Design spec optimized for AI alignment
+      optional_for: S/XS sized stories
+
+    - name: /rai-story-plan
+      purpose: Decompose into atomic executable tasks
+      when: After design (or directly for simple stories)
+      creates: Task list with dependencies
+
+    - name: /rai-story-implement
+      purpose: Execute tasks with TDD and validation gates
+      when: Plan exists
+      creates: Working code, tests, documentation
+
+    - name: /rai-story-review
+      purpose: Extract learnings, identify improvements
+      when: Implementation complete
+      creates: Retrospective, pattern updates
+
+    - name: /rai-story-close
+      purpose: Verify, merge, cleanup
+      when: Review complete
+      creates: Merged code, deleted branch
+
+  discovery:
+    - name: /rai-discover-start
+      purpose: Initialize codebase discovery
+      when: Setting up discovery for a codebase
+      creates: Discovery context file
+
+    - name: /rai-discover-scan
+      purpose: Extract symbols and synthesize descriptions
+      when: After discovery initialized
+      creates: Draft component catalog (YAML)
+
+    - name: /rai-discover-validate
+      purpose: Human review of synthesized descriptions, then export to graph format
+      when: After scan complete
+      creates: Validated component catalog + JSON for graph integration
+
+  meta:
+    - name: /rai-skill-create
+      purpose: Create new skills with framework integration
+      when: Adding workflow automation
+      creates: Skill directory with prompt.md
+
+  other:
+    - name: /rai-research
+      purpose: Epistemologically rigorous research
+      when: Before ADRs, evaluating approaches, unfamiliar domains
+      creates: Evidence catalog with triangulated claims
+
+    - name: /rai-debug
+      purpose: Root cause analysis using lean methods
+      when: Encountering unexpected behavior or defects
+      method: 5 Whys, Ishikawa diagram, Gemba
+
+    - name: /rai-framework-sync
+      purpose: Sync framework files across locations
+      when: Framework updates need propagation
+
+# =============================================================================
+# Gates (Poka-Yoke)
+# =============================================================================
+gates:
+  blocking:
+    - before: Epic design
+      require: Epic directory and scope initialized
+      enforced_by: /rai-epic-start
+      rationale: Epics need scope before design work begins
+
+    - before: Story work
+      require: Story branch and scope commit
+      enforced_by: /rai-story-start
+      rationale: Traceability from first commit
+
+    - before: Implementation
+      require: Plan exists
+      enforced_by: /rai-story-plan
+      rationale: No coding without decomposed tasks
+
+    - before: Story close
+      require: Retrospective complete
+      enforced_by: /rai-story-review
+      rationale: Learning is part of done
+
+    - before: Epic close
+      require: Epic retrospective complete
+      enforced_by: /rai-epic-close
+      rationale: Meso-layer learning captured
+
+  quality:
+    - gate: Tests pass
+      when: Before any commit
+      rationale: TDD is non-negotiable
+
+    - gate: Type checks pass
+      when: Before any commit
+      tool: pyright --strict
+
+    - gate: Linting passes
+      when: Before any commit
+      tool: ruff check && ruff format
+
+# =============================================================================
+# Principles (Critical Rules)
+# =============================================================================
+principles:
+  process:
+    - name: TDD Always
+      rule: RED-GREEN-REFACTOR, no exceptions
+      rationale: Tests are specification, not afterthought
+
+    - name: Commit After Task
+      rule: Commit after each completed task, not just story end
+      rationale: Enables recovery, shows progress
+
+    - name: Full Skill Cycle
+      rule: Use skills even for small stories
+      rationale: Structure helps; overhead is minimal
+
+    - name: Ask Before Subagents
+      rule: Get permission before spawning subagents
+      rationale: Inference economy - AI computation is precious
+
+    - name: Delete Branches After Merge
+      rule: Clean up merged branches immediately
+      rationale: Prevent accumulation, reduce confusion
+
+  collaboration:
+    - name: HITL Default
+      rule: Pause after significant work for human review
+      rationale: Slow is smooth, smooth is fast
+
+    - name: Direct Communication
+      rule: No praise-padding, say what needs saying
+      rationale: Efficiency and respect for time
+
+    - name: Redirect When Dispersing
+      rule: Gently redirect tangents to parking lot
+      rationale: Maintain focus on stated goal
+
+  technical:
+    - name: Type Everything
+      rule: Type annotations on all code
+      rationale: Pyright strict is the standard
+
+    - name: Pydantic Models
+      rule: Use Pydantic for all data structures
+      rationale: Validation at boundaries, serialization free
+
+    - name: Simple First
+      rule: Simple heuristics over complex solutions
+      rationale: Complexity must earn its place
+
+# =============================================================================
+# Branch Model
+# =============================================================================
+branches:
+  structure: |
+    main (stable)
+      └── {development_branch} (development)
+            └── story/s{N}.{M}/{name}
+
+  flow:
+    - "Stories branch from and merge to {development_branch}"
+    - "{development_branch} merges to main at release"
+    - "Epics are logical containers (directory + tracker), not branches"

raise_cli/rai_base/governance/__init__.py

@@ -0,0 +1 @@
+"""Bundled governance templates for project scaffolding."""

raise_cli/rai_base/governance/architecture/__init__.py

@@ -0,0 +1 @@
+"""Bundled architecture document templates."""

raise_cli/rai_base/governance/architecture/domain-model.md

@@ -0,0 +1,20 @@
+---
+type: architecture_domain_model
+project: "{project_name}"
+status: draft
+bounded_contexts: []
+shared_kernel: {}
+---
+
+# Domain Model: {project_name}
+
+> Bounded contexts and shared kernel
+> Fill with /rai-project-create or /rai-project-onboard
+
+## Bounded Contexts
+
+<!-- Group modules into bounded contexts based on domain boundaries -->
+
+## Shared Kernel
+
+<!-- Modules shared across bounded contexts -->

raise_cli/rai_base/governance/architecture/system-context.md

@@ -0,0 +1,34 @@
+---
+type: architecture_context
+project: "{project_name}"
+status: draft
+tech_stack: {}
+external_dependencies: []
+users: []
+governed_by: []
+---
+
+# System Context: {project_name}
+
+> C4 Level 1 — System Context diagram and description
+> Fill with /rai-project-create or /rai-project-onboard
+
+## Overview
+
+<!-- High-level description: what is this system and who uses it? -->
+
+## Context Diagram
+
+<!-- System context showing external actors and systems -->
+
+```
+┌──────────┐       ┌──────────────┐       ┌──────────┐
+│  Users   │──────►│  {project_name}  │◄──────│ External │
+│          │       │              │       │ Systems  │
+└──────────┘       └──────────────┘       └──────────┘
+```
+
+## External Interfaces
+
+| System | Direction | Protocol | Description |
+|--------|-----------|----------|-------------|

raise_cli/rai_base/governance/architecture/system-design.md

@@ -0,0 +1,24 @@
+---
+type: architecture_design
+project: "{project_name}"
+status: draft
+layers: []
+---
+
+# System Design: {project_name}
+
+> C4 Level 2 — Container/component decomposition
+> Fill with /rai-project-create or /rai-project-onboard
+
+## Architecture Overview
+
+<!-- High-level architecture description -->
+
+## Components
+
+| Component | Responsibility | Technology |
+|-----------|---------------|------------|
+
+## Key Decisions
+
+<!-- Reference ADRs when available: dev/decisions/adr-XXX.md -->

raise_cli/rai_base/governance/backlog.md

@@ -0,0 +1,8 @@
+# Backlog: {project_name}
+
+> **Status**: Draft
+
+## Epics
+
+| ID | Epic | Status | Scope | Priority |
+|----|------|--------|-------|----------|

raise_cli/rai_base/governance/guardrails.md

@@ -0,0 +1,17 @@
+---
+type: guardrails
+version: "1.0.0"
+---
+
+# Guardrails: {project_name}
+
+> Code and architecture guardrails — fill with /rai-project-create or /rai-project-onboard
+
+---
+
+## Guardrails Activos
+
+### Code Quality
+
+| ID | Level | Guardrail | Verification | Derived from |
+|----|-------|-----------|--------------|--------------|

raise_cli/rai_base/governance/prd.md

@@ -0,0 +1,25 @@
+# PRD: {project_name}
+
+> Product Requirements Document — fill with /rai-project-create or /rai-project-onboard
+
+---
+
+## Problem
+
+<!-- Describe the problem this project solves -->
+
+## Goals
+
+<!-- What success looks like -->
+
+---
+
+## Requirements
+
+### RF-01: Core Functionality
+
+<!-- Describe the primary capability this project must provide -->
+
+### RF-02: User Experience
+
+<!-- Describe how users interact with the project -->

raise_cli/rai_base/governance/vision.md

@@ -0,0 +1,16 @@
+# Solution Vision: {project_name}
+
+> Solution vision — fill with /rai-project-create or /rai-project-onboard
+
+## Identity
+
+### Description
+
+<!-- One-paragraph description of what this project is and why it exists -->
+
+## Outcomes
+
+| **Outcome** | **Description** |
+|-------------|-----------------|
+| **Core Value** | <!-- Primary value delivered to users --> |
+| **Quality** | <!-- Quality standards this project meets --> |

raise_cli/rai_base/identity/__init__.py

@@ -0,0 +1,8 @@
+"""Base Rai identity files.
+
+Contains:
+    core.md         Rai's values, boundaries, essence
+    perspective.md  How Rai approaches collaboration
+"""
+
+from __future__ import annotations