crackerjack 0.44.4__tar.gz → 0.47.6__tar.gz

crackerjack-0.47.6/.gitignore

@@ -0,0 +1,115 @@
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+.coverage*
+.pytest_cache/
+.hypothesis/
+
+# Development tools
+.mypy_cache/
+.ruff_cache/
+.autotyping-cache/
+
+# Build and distribution
+build/
+dist/
+*.egg-info/
+/__pypackages__/
+
+# Virtual environments
+.venv/
+venv/
+
+# IDE and OS
+.DS_STORE
+.idea/
+.envrc
+
+# UV/PDM package management
+.pdm-python
+.pdm.toml
+.pdm-build/
+
+# Project-specific generated files
+/coverage.json
+/htmlcov/
+/tests/htmlcov/
+/complexipy.json
+/test-results.xml
+crackerjack-debug-*.log
+crackerjack-ai-debug-*.log
+/hooks-analysis.json
+/quality-metrics.json
+/project-structure.json
+/error-context.json
+/ai-agent-summary.json
+/bandit-report.json
+
+# Crackerjack state and cache
+/.crackerjack/
+/.crackerjack-state
+/.crackerjack-hooks-updated
+/.crackerjack-mcp/
+/.benchmarks/
+/tests/.benchmarks/
+
+# Adapter output files (centralized in .crackerjack/outputs/)
+# Note: Individual adapters may create timestamped results
+.crackerjack/outputs/
+
+# Development artifacts (evaluate periodically)
+/feature-implementation-*.md
+/session_handoff_*.md
+/test-implementation-*.md
+
+# Temporary and scratch files
+/tmp/
+/scratch/
+/examples/
+
+# Configuration files (project-specific)
+.mcp.json
+/.mcp-proxy.json
+
+# Claude Code settings
+/.claude/
+**/.claude/settings.local.json
+
+# Crackerjack patterns
+complexipy_results_*.json
+complexipy.json
+
+# Build/Distribution
+# Caches
+# Coverage
+# Crackerjack specific
+# Development
+*.pyc
+.crackerjack-*
+/dist/
+htmlcov/
+/NOTES.md
+/.obsidian/
+/.smart-env/
+/.backups/
+settings/local.yaml
+
+# Local settings overrides (ACB configuration)
+/.uv-cache/
+/.complexipy_cache/
+
+# Pyscn static analysis reports
+.pyscn/
+
+# Documentation archives (skip in formatters/docs processing)
+/docs/archive/
+docs/archive/
+
+# Git worktrees (Crystal)
+/worktrees/
+/worktree-*/
+/.oneiric_cache/
+/.jbeval/
+/.conductor/
+/.ai/

crackerjack-0.47.6/.python-version

@@ -0,0 +1 @@
+3.13

crackerjack-0.47.6/AGENTS.md

@@ -0,0 +1,40 @@
+# Repository Guidelines
+
+## Project Structure & Module Organization
+
+- Core runtime and CLI entrypoints live in `crackerjack/`; agent orchestration, prompts, and CLI commands sit in subpackages noted by their role.
+- Automation helpers are split between `scripts/` and `tools/` for reproducible workflows, with shared fixtures living in `tests/conftest.py`.
+- Documentation resides in `docs/`, `README.md`, and `CLAUDE.md`; additional examples and mock configuration are under `examples/` and `example.mcp.json`.
+- Tests mirror the package layout in `tests/`, while the documentation site fixtures live in `test_docs_site/` for isolated snapshot coverage.
+
+## Build, Test, and Development Commands
+
+- `uv sync --group dev`: install runtime, testing, and MCP dependencies into the active environment.
+- `/crackerjack:run --debug`: execute the end-to-end multi-agent workflow locally before running isolated modules.
+- `uv run python -m crackerjack run --help`: list available CLI entrypoints when adjusting invocation behavior.
+- `uv run pytest --maxfail=1`: run the default test suite, stopping on the first failure during iteration.
+- `uv run ruff check --fix && uv run ruff format`: apply lint fixes and enforce formatting, including import ordering.
+
+## Coding Style & Naming Conventions
+
+- Target Python 3.13 with 4-space indentation; annotate public functions and complex helpers with explicit types.
+- Keep identifiers concise yet descriptive, using `*Agent` suffixes for agent classes and `test_<feature>.py` naming for tests.
+- Respect Ruff complexity guidance (≤15) and rely on `ruff check` to guard style, security, and dead code concerns.
+
+## Testing Guidelines
+
+- Prefer `pytest` fixtures from `tests/conftest.py` and reuse documentation assets from `test_docs_site/` when validating rendered output.
+- Work toward 42% milestone (current: 21.6%, baseline: 19.6%); consult `coverage.json` or `htmlcov/` after changes. See [COVERAGE_POLICY.md](/docs/reference/COVERAGE_POLICY.md).
+- Use markers `chaos`, `ai_generated`, and `breakthrough` to isolate expensive suites; document new fixtures and markers alongside the relevant tests.
+
+## Commit & Pull Request Guidelines
+
+- Write commits as `type(scope): summary`, referencing tickets or MCP jobs where relevant and grouping related changes tightly.
+- PRs should state motivation, implementation notes, validation evidence (commands run, screenshots for docs/UI tweaks), linked issues, and follow-up tasks.
+- Run `uv run pre-commit run --all-files` before opening PRs to align formatting, linting, and security expectations.
+
+## Agent-Aware Workflow
+
+- Trigger quality sweeps with `/crackerjack:run`, monitor using `get_job_progress`, and verify readiness via `/crackerjack:status`.
+- Update `.mcp.json` when wiring new servers, and document fresh agent capabilities in `docs/` plus the MCP manifest.
+- Keep structured outputs (`test-results.xml`, `coverage.json`) current to support downstream dashboards and release gates.