raise-cli 3.1.0a3__tar.gz → 3.1.0b2__tar.gz

raise_cli-3.1.0b2/.gitignore

@@ -0,0 +1,278 @@
+# Node.js
+node_modules/
+
+# IDE / editor directories
+.specstory/
+.cursor/
+.idea/
+.vscode/
+
+# Claude Code local settings (user-specific)
+.claude/settings.local.json
+.claude/worktrees/
+.claude/projects/
+
+# Hermes Agent worktrees (auto-created by hermes -w)
+.worktrees/
+
+# RaiSE worktrees (auto-created by rai-worktree-open — never commit as gitlink)
+.rai-worktrees/
+.worktree/
+
+# Codex/Agents experimental tooling (local only)
+.agents/
+# .codex/ and .codex-plugin/ are tracked — static hook scripts propagate via git
+# Only config.toml is machine-specific (absolute path to rai-mcp-pipeline resolved at init)
+.codex/config.toml
+
+# Hermes MCP config (auto-generated per worktree by rai worktree register
+# --provision — bakes in this worktree's absolute .venv-mcp path, so it can
+# never be shared across worktrees without producing a spurious diff)
+.hermes/config.yaml
+
+# Kimi Code MCP config (auto-generated per checkout by rai init --agent kimi
+# — bakes in this checkout's absolute project path, so it is per-checkout
+# like .mcp.json and .codex/config.toml; not committable) [S15457.3 D5/AC8]
+.kimi-code/mcp.json
+
+# Claude Code legacy files (superseded, prevent re-addition)
+.claude/RAI.md
+.claude/RAI-naming.md
+.claude/rai.archive/
+
+# Daemon config (contains secrets — template committed as .example)
+daemon-team.yaml
+daemon.yaml
+.env.fly
+
+# Conformance analysis data (SQLite, runtime-generated)
+dev/data/*.db
+
+# RaiSE generated/cache files
+.raise/cache/
+.raise/confluence-pages.yaml
+.raise/backlog/
+# .raise/artifacts/ — tracked (story-design YAMLs are versioned artifacts)
+
+# Reliability cadence data (runtime-generated, append-only — pushed to reliability-data branch)
+# These files are committed exclusively to the reliability-data branch via _push_to_data_branch.
+# Gitignore prevents accidental commits to story/main branches.
+.raise/reliability/
+
+# Drift detection pipeline outputs (computed, machine-specific paths, high churn)
+.raise/drift/
+packages/*/.raise/drift/
+packages/*/.raise/pending_sync.json
+packages/*/.raise/rai/personal/sessions/
+packages/*/.raise/rai/personal/telemetry/
+packages/*/.raise/rai/personal/calibration.jsonl
+packages/*/.raise/rai/personal/patterns.jsonl
+packages/*/.raise/rai/personal/active-session
+packages/*/.raise/rai/sessions/
+packages/*/.raise/rai/personal/last-build.json
+
+# Pipeline state (environment-specific, PAT-E-594)
+.rai-state/
+
+# RaiSE adapter configs (declarative, PII-free — identity in env vars)
+# .raise/jira.yaml and .raise/confluence.yaml are tracked (shared config)
+.raise/adapters/*.yaml
+!.raise/adapters/*.yaml.example
+
+# Dossier output (generated, not committed)
+dev/output/
+
+# RaiSE graph index — SQLite is canonical after S22.3; index.json excluded via .raise/.gitignore
+# Rebuild with: rai graph build
+
+# RaiSE personal directory (per-developer, not shared)
+# Note: .raise/rai/personal/memory/ is tracked (S9476.1 CC Memory git sync)
+.raise/rai/personal/sessions/
+.raise/rai/personal/telemetry/
+.raise/rai/personal/calibration.jsonl
+.raise/rai/personal/patterns.jsonl
+.raise/rai/personal/active-session
+
+# RaiSE sync state (per-instance JIRA mappings, not shared)
+.raise/rai/sync/
+
+# RaiSE global SQLite DB (per-machine, not shared)
+.raise/rai/raise.db
+.raise/raise.db
+
+# RaiSE mission migration artifacts
+.raise/rai/missions/*.migrated
+
+# RaiSE sync ephemeral artifacts (backups, dead-letter, migrations, pending ops)
+.raise/sync/backlog-ledger.yaml
+.raise/sync/backlog-ledger.yaml.backup.*
+.raise/sync/backlog-dead-letter.jsonl
+.raise/sync/docs-dead-letter.jsonl
+.raise/sync/backlog-ledger.yaml.migrated
+packages/*/.raise/sync/*-pending-ops.jsonl
+
+# Per-session env context written by Rai skills, read by CC hooks + MCP tool
+# Namespaced by CC session_id (RAISE-1982) — isolates concurrent CC sessions.
+.raise/rai/sessions/
+
+# Temporary files
+req.txt
+*.tmp
+*.bak-*
+*.log
+*.pid
+.DS_Store
+Thumbs.db
+
+# Script generated folders (if testing locally)
+.specify-raise/commands/
+
+# Python build artifacts
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+/lib/
+/lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+
+# Virtual environments
+.venv/
+.venv.dev/
+.venv-mcp/
+venv/
+ENV/
+env/
+
+# Testing
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+.hypothesis/
+.pytest_cache/
+
+# Type checking
+.mypy_cache/
+.dmypy.json
+dmypy.json
+.pyright/
+.rai/memory/graph.json
+.envrc
+
+# Legacy telemetry (should be in personal/, will migrate)
+.raise/rai/telemetry/
+
+# Push tracking markers (per-environment, not shared)
+.raise/rai/learnings/**/.pushed
+
+# MCP server config (contains API tokens)
+.mcp.json
+
+# Secrets & credentials
+.env
+.env.*
+!.env.example
+!.env.production
+*.pem
+*.key
+.pypirc
+credentials.json
+*.sqlite
+.netrc
+.raise/mcp/
+!.raise/mcp/catalog.yaml
+
+# MkDocs build output
+_site/
+.docs-build/
+
+# Security scan outputs (contain findings — not committed)
+work/reports/gl-secret-detection-report*
+
+# Customer and GTM transcripts are owned by raise-gtm/content/sources.
+work/transcripts/
+
+# Issue analysis artifacts (PDFs, images — binary, no git value)
+dev/issues/**/*.pdf
+dev/issues/**/*.png
+dev/issues/**/*.jpg
+dev/issues/**/*.txt
+dev/transcripts/
+
+# Prevent symlink artifacts from being tracked at root
+/es/
+
+# Ephemeral debug artifacts (Playwright MCP snapshots, root-level screenshots)
+.playwright-mcp/
+.claude/scheduled_tasks.lock
+/issue-*.png
+/panel-*.png
+/s7-*.png
+/app-actions-menu.yml
+/issue-layout.yml
+/layout-editor.yml
+/menu-open.yml
+/raise-*.yml
+
+# Per-developer docker compose override (e.g., expose postgres:5432 for e2e).
+# See dev/sops/raise-server-local.md § Running e2e tests locally.
+/docker-compose.override.yaml
+/docker-compose.override.yml
+.worktrees/
+.venv
+.venv
+work/debug/
+
+# Playwright E2E auth state (contains session cookies)
+# Wildcard: any package's .raise/dev/ is per-session Vite/dev-server runtime state (RAISE-11105)
+packages/*/.raise/dev/
+packages/raise-admin/e2e/.auth/
+# Playwright test results
+packages/raise-admin/test-results/
+packages/raise-admin/playwright-report/
+# Vite dev cache (generado por npm run dev, por máquina)
+packages/raise-admin/.vite/
+
+# Forge raise-jira app — generated files
+forge/raise-jira/static/raise-app/package-lock.json
+forge/raise-jira/static/raise-app/pnpm-workspace.yaml
+# Wildcard: any package's .raise/sync dead-letter / .raise/backlog cache (RAISE-11105)
+packages/*/.raise/sync/*-dead-letter.jsonl
+packages/*/.raise/backlog/
+package-lock.json
+.raise/rai/*.db.backup-*
+*.npy
+
+# Generated per-worktree dev stack (rai dev up — compose.py); never commit
+docker-compose.dev.yml
+.hermes/config.yaml
+
+# Distillation verdicts — developer-specific GT data (RAISE-15398)
+.raise/distillation/verdicts/
+
+# Cloudflare Workers/Pages local secrets — never commit (RAISE-15651)
+# These patterns previously lived only in site/.gitignore; hoisted to the root
+# so removing a subdirectory can never silently unprotect a secrets file.
+.dev.vars
+.dev.vars.*
+.env.production
+.astro/
+.scannerwork/

raise_cli-3.1.0b2/PKG-INFO

@@ -0,0 +1,301 @@
+Metadata-Version: 2.4
+Name: raise-cli
+Version: 3.1.0b2
+Summary: RaiSE CLI - Reliable AI Software Engineering governance framework
+Project-URL: Homepage, https://raiseframework.ai
+Project-URL: Documentation, https://docs.raiseframework.ai
+Project-URL: Repository, https://github.com/humansys/raise
+Project-URL: Changelog, https://github.com/humansys/raise/blob/main/CHANGELOG.md
+Author-email: Emilio Osorio <emilio@humansys.ai>
+License: Apache-2.0
+Keywords: ai,cli,governance,methodology,software-engineering
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.12
+Requires-Dist: atlassian-python-api>=3.41.0
+Requires-Dist: httpx<1.0,>=0.27.0
+Requires-Dist: logfire-api>=4.0
+Requires-Dist: markdown>=3.6
+Requires-Dist: mcp<2,>=1.26
+Requires-Dist: networkx>=3.6.1
+Requires-Dist: numpy>=1.26.0
+Requires-Dist: pydantic-settings>=2.2.0
+Requires-Dist: pydantic>=2.6.0
+Requires-Dist: python-dotenv>=1.0.0
+Requires-Dist: pyyaml>=6.0.1
+Requires-Dist: raise-core==3.1.0b2
+Requires-Dist: rich>=13.7.0
+Requires-Dist: tree-sitter-javascript>=0.25.0
+Requires-Dist: tree-sitter-language-pack>=0.13.0
+Requires-Dist: tree-sitter-php>=0.24.1
+Requires-Dist: tree-sitter-svelte>=1.0.2
+Requires-Dist: tree-sitter-typescript>=0.23.2
+Requires-Dist: tree-sitter>=0.25.2
+Requires-Dist: typer>=0.12.0
+Provides-Extra: atlassian
+Provides-Extra: confluence
+Provides-Extra: csharp
+Requires-Dist: tree-sitter-c-sharp>=0.23.1; extra == 'csharp'
+Provides-Extra: eval
+Requires-Dist: ranx<0.4,>=0.3.20; extra == 'eval'
+Requires-Dist: scipy>=1.10; extra == 'eval'
+Provides-Extra: gdrive
+Requires-Dist: google-auth-oauthlib>=1.0; extra == 'gdrive'
+Requires-Dist: google-auth>=2.0; extra == 'gdrive'
+Provides-Extra: go
+Requires-Dist: tree-sitter-go>=0.25.0; extra == 'go'
+Provides-Extra: inference
+Requires-Dist: anthropic>=0.89.0; extra == 'inference'
+Provides-Extra: java
+Requires-Dist: tree-sitter-java>=0.23.5; extra == 'java'
+Provides-Extra: jira
+Provides-Extra: observability
+Requires-Dist: logfire>=4.0; extra == 'observability'
+Requires-Dist: opentelemetry-api>=1.20; extra == 'observability'
+Requires-Dist: opentelemetry-sdk>=1.20; extra == 'observability'
+Description-Content-Type: text/markdown
+
+# RaiSE
+
+[![PyPI](https://img.shields.io/pypi/v/raise-cli)](https://pypi.org/project/raise-cli/)
+[![Python](https://img.shields.io/pypi/pyversions/raise-cli)](https://pypi.org/project/raise-cli/)
+[![License](https://img.shields.io/pypi/l/raise-cli)](https://github.com/humansys/raise/blob/main/LICENSE)
+
+AI coding assistants are fast, but their context resets between sessions, quality checks are opt-in, and decision history is scattered across tool logs. RaiSE persists workflow state, runs your validation commands between phases, and records the artifacts behind each change.
+
+```bash
+uv tool install raise-cli --pre
+cd your-project && rai init --detect
+```
+
+> Works with **Claude Code** · **Cursor** · **Aider** · **Cline** · **Devin** · **Kimi** — CLI works alongside any assistant; full workflow integration varies by tool.
+
+---
+
+## Why This Exists
+
+Most agent workflows rely on prompt instructions like "NEVER skip steps." The LLM skips them anyway — prompt instructions are requests, not constraints. The quality gate that catches this can't be another AI opinion. It has to be code.
+
+CI validates a commit *after* work has been produced. RaiSE runs the same checks *before* the workflow advances, and retains the design and decision artifacts used to produce the change — `scope.md`, `design.md`, `plan.md`, gate results — creating versioned evidence that supports SOC 2, ISO 27001, and EU AI Act traceability requirements.
+
+Within a RaiSE pipeline, a phase cannot advance when a configured gate fails. Not "I checked myself and I'm good" — actual test suites, linters, and type checkers that run as code.
+
+**What's enforced vs. guided:** skills are instructions — an agent can deviate from them, like any prompt. What it can't do is fake a gate result: pipeline state and gate outcomes are produced by real command runs and stored in versioned files under `.raise/`. If work bypassed the pipeline, the artifact trail shows the gap — and CI can require a clean trail before merge, closing the loop with the same enforcement you already trust.
+
+---
+
+## What RaiSE Adds to Your AI Tool
+
+RaiSE is not another coding assistant. It's the governance layer that coordinates what your tools already do.
+
+| Concern | Existing pieces | RaiSE contribution |
+|---|---|---|
+| **Workflow state** | Plans, issues, tool-specific history | A persisted, resumable workflow state machine |
+| **Validation** | CI, pre-commit, tests, lint, types | Runs checks at workflow phase boundaries (design → plan → implement → review), not just at commit or push |
+| **Traceability** | Git, issues, ADRs, logs | Links scope → design → implementation → review → gate results in versioned artifacts |
+| **Context** | Tool memory, AST/LSP indexes | Repo-local persistent memory plus an AST-derived dependency graph |
+| **Portability** | Tool-specific configuration (CLAUDE.md, .cursorrules) | Shared governance artifacts across tools with integration-specific adapters |
+| **Backlog & docs** | Manual Jira updates, Confluence copy-paste | `rai backlog` syncs Jira status; `rai docs publish` pushes artifacts to Confluence |
+
+---
+
+## Quick Start
+
+### Install
+
+```bash
+# Recommended: isolated CLI install
+uv tool install raise-cli --pre
+# or
+pipx install raise-cli --pre
+
+# Alternative: pip
+pip install raise-cli --pre
+
+# macOS / Linux one-liner (inspect first: https://docs.raiseframework.ai/install.sh)
+curl -LsSf https://docs.raiseframework.ai/install.sh | bash
+
+# Windows (PowerShell)
+irm https://docs.raiseframework.ai/install.ps1 | iex
+```
+
+Requires Python 3.12+. Fully functional on its own — sessions, graph, gates, pipelines, backlog adapters — with no server and no account. Project state stays under `.raise/` in your repo; developer config under `~/.rai/`. RaiSE sends no data unless you configure an external adapter.
+
+### Initialize
+
+```bash
+$ rai init --detect                        # illustrative output
+✓ Detected: Python 3.12, pytest, ruff, pyright
+✓ Created .raise/ with project governance
+✓ Registered 4 validation gates (tests, lint, format, types)
+Ready. Run /rai-welcome in your AI coding tool.
+```
+
+Works on existing codebases. `--detect` reads your stack and configures gates from what's already there — no greenfield scaffolding required.
+
+### First Session (Claude Code example)
+
+```
+/rai-welcome              # One-time onboarding — creates your developer profile
+/rai-session-start        # Loads prior context, memory, and proposes focus
+```
+
+Then work using the governed lifecycle:
+
+```
+/rai-story-start          # Branch + scope
+/rai-story-design         # Design the approach (optional for small changes)
+/rai-story-plan           # Break into tasks
+/rai-story-implement      # TDD execution — gates block advancement on failure
+/rai-story-review         # Retrospective, capture patterns
+/rai-story-close          # Merge + cleanup
+/rai-session-close        # Persist learnings for next session
+```
+
+After close, your repo contains `scope.md`, `design.md`, `plan.md`, passing gate results, and captured patterns — every decision traceable for audits or onboarding new contributors.
+
+Need to work on multiple stories at once? `/rai-worktree-open` gives each story its own isolated branch, pipeline state, and memory scope.
+
+> Using Cursor or Aider? The `rai` CLI works standalone: `rai session start`, `rai gate check gate-tests`. Skills are portable markdown — they work in any tool that supports custom instructions.
+
+> **Full guide:** [Getting Started](https://docs.raiseframework.ai/latest/getting-started/) · [Installation](https://docs.raiseframework.ai/latest/installation/) · [First Story](https://docs.raiseframework.ai/latest/guides/first-story/)
+
+---
+
+## How It Works
+
+### Deterministic Pipeline Coordinator
+
+Each phase of your workflow is a **skill** — a structured set of steps. The pipeline coordinator blocks phase transitions when a configured gate fails.
+
+```
+story-start → design → plan → implement → review → close
+                                  │
+                          ┌───────┴────────┐
+                          │  Gate: tests   │  ← deterministic,
+                          │  Gate: lint    │    not AI opinion
+                          │  Gate: types   │
+                          │  Gate: format  │
+                          └────────────────┘
+```
+
+Gates are configurable per project via YAML. Failed gates stop the workflow — no accumulating errors.
+
+### Knowledge Graph
+
+RaiSE builds an AST-derived call and dependency graph of your codebase — not keyword similarity, but actual import chains, call sites, and inheritance relationships.
+
+```bash
+$ rai graph build                          # illustrative output
+✓ Scanned 847 symbols across 12 modules
+✓ Built 2,341 edges (calls, imports, inherits, implements)
+
+$ rai graph query "auth flow"
+→ mod-auth: AuthService.authenticate → TokenStore.issue → AuditLog.record
+  3 cross-module dependencies, 2 governance rules apply
+```
+
+Your agent gets the component that's actually being called — not the one with the closest name.
+
+### Persistent Memory
+
+| What persists | Where it lives | How it helps |
+|---|---|---|
+| **Patterns** | `.raise/rai/memory/` | Learned from your work — recurring failure patterns become suggested guardrails for future stories |
+| **Session history** | `.raise/rai/personal/` | Decisions made, items deferred, context restored |
+| **Knowledge graph** | `.raise/rai/memory/index.json` | Project architecture and dependency relationships |
+| **Calibration** | `.raise/rai/personal/` | Your velocity and working patterns |
+
+Project state stays under `.raise/` in your repo; developer-level config under `~/.rai/`. Memory is portable across AI tools — switch from Claude Code to Cursor and your governance context follows.
+
+### Autonomy Levels
+
+Your level of trust dictates how much the agent does unsupervised:
+
+| Level | Behavior | For |
+|---|---|---|
+| **Supervised** | Pauses at every gate for review | New to RaiSE or high-risk repos |
+| **Delegated** | Autonomous on routine, pauses on novel decisions | Day-to-day development |
+| **Autonomous** | Fully autonomous, pauses only on design decisions or persistent errors | Senior developers, trusted codebases |
+
+---
+
+## Packages
+
+| Package | Description | Install |
+|---|---|---|
+| **raise-cli** | `rai` CLI — sessions, graph, gates, pipelines, backlog | `pip install raise-cli --pre` |
+| **raise-core** | Core library — graph, memory, patterns, discovery | `pip install raise-core --pre` |
+
+Open Core (Apache-2.0). Fully functional on its own — no server, no account. [RaiSE Pro](https://raiseframework.ai) adds team governance, shared services, and hosted runners for organizations that need them.
+
+---
+
+## CLI Reference
+
+```bash
+rai init --detect              # Initialize RaiSE on your project
+rai session start              # Start a working session
+rai session close              # End session, persist learnings
+rai graph build                # Build the knowledge graph
+rai graph query "auth flow"    # Query project architecture
+rai gate check gate-tests      # Run validation gates
+rai skill list                 # List available skills
+rai doctor                     # Diagnostics and health check
+```
+
+> **Full CLI reference:** [docs.raiseframework.ai/latest/cli](https://docs.raiseframework.ai/latest/cli/)
+
+---
+
+## Skills
+
+Skills are structured workflows — portable markdown files that guide AI-assisted development. They work in any tool that supports custom instructions.
+
+| Category | Skills |
+|---|---|
+| **Session** | `rai-welcome` · `rai-session-start` · `rai-session-close` |
+| **Story** | `rai-story-start` · `rai-story-design` · `rai-story-plan` · `rai-story-implement` · `rai-story-review` · `rai-story-close` |
+| **Epic** | `rai-epic-start` · `rai-epic-design` · `rai-epic-plan` · `rai-epic-close` |
+| **Quality** | `rai-quality-review` · `rai-architecture-review` · `rai-debug` |
+| **Research** | `rai-research` · `rai-problem-shape` |
+| **Project** | `rai-project-create` · `rai-project-onboard` · `rai-discover` |
+
+---
+
+## Background
+
+RaiSE has been in development since late 2023, born from a practical problem: a team that lost its developers and had to ship production software using AI assistants — software that had to pass financial regulatory review, CI pipelines, SonarQube, and security audits. RAG wasn't enough. Prompt engineering wasn't enough. What worked was a deterministic governance layer with an AST-derived knowledge graph.
+
+Developed and used in production environments since 2023. Built by [HumanSys](https://humansys.ai).
+
+---
+
+## Documentation
+
+- [Getting Started](https://docs.raiseframework.ai/latest/getting-started/)
+- [Installation Guide](https://docs.raiseframework.ai/latest/installation/)
+- [Concepts Overview](https://docs.raiseframework.ai/latest/concepts/)
+- [CLI Reference](https://docs.raiseframework.ai/latest/cli/)
+- [Pipeline Quickstart](https://docs.raiseframework.ai/latest/guides/pipeline-quickstart/)
+
+---
+
+## Status
+
+Current release: **v3.1.0-beta**. Install with `pip install raise-cli --pre` for the latest.
+
+- **Questions or bugs?** [Open an issue](https://github.com/humansys/raise/issues) (GitHub mirror)
+- **Want to try it?** `pip install raise-cli --pre && rai init --detect`
+
+---
+
+## License
+
+[Apache-2.0](https://github.com/humansys/raise/blob/main/LICENSE)