v1.1.0 — CLI, i18n, cost rename, docs overhaul, CI

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,39 @@
+---
+name: Bug Report
+about: Report a bug in Cronalytics
+title: "[Bug] "
+labels: bug
+assignees: ""
+---
+
+## Describe the bug
+
+A clear and concise description of what the bug is.
+
+## To Reproduce
+
+Steps to reproduce the behavior:
+
+1. Run `cronalytics ...`
+2. Open the dashboard and click ...
+3. See error
+
+## Expected behavior
+
+A clear and concise description of what you expected to happen.
+
+## What actually happened
+
+The error message, incorrect behavior, or unexpected output.
+
+## Environment
+
+- **Cronalytics version:** [e.g., 1.1.0]
+- **Hermes Agent version:** [e.g., 0.10.0]
+- **OS:** [e.g., Arch Linux, macOS 14]
+- **Browser (if dashboard issue):** [e.g., Firefox 126, Chrome 125]
+- **Install method:** [e.g., `hermes plugins install`, pip install]
+
+## Additional context
+
+Add any other context: screenshots, `facts.db` excerpts (no secrets!), relevant cron job definitions, or logs from `hermes logs --gateway`.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,27 @@
+---
+name: Feature Request
+about: Suggest an idea for Cronalytics
+title: "[Feature] "
+labels: enhancement
+assignees: ""
+---
+
+## Is your feature request related to a problem?
+
+A clear and concise description of what the problem is. Ex: "I can't see my cron jobs from a non-default profile."
+
+## Describe the solution you'd like
+
+A clear and concise description of what you want to happen.
+
+## Describe alternatives you've considered
+
+A clear and concise description of any alternative solutions or workarounds you've tried.
+
+## How would you use this?
+
+Describe the workflow or use case this feature would enable for you.
+
+## Additional context
+
+Add any other context, references, or screenshots.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,22 @@
+## Description
+
+What does this PR do? Link the issue it fixes (e.g., `Fixes #123`).
+
+## Type of change
+
+- [ ] Bug fix (non-breaking change fixing an issue)
+- [ ] New feature (non-breaking change adding functionality)
+- [ ] Breaking change (fix or feature that would break existing behavior)
+- [ ] Documentation update
+- [ ] Chore (build, CI, tooling, cleanup)
+
+## Checklist
+
+- [ ] I have read [CONTRIBUTING.md](../CONTRIBUTING.md)
+- [ ] Tests pass: `python -m pytest tests/ -v --tb=short`
+- [ ] Lint clean: `ruff check .`
+- [ ] Type check clean: `mypy cronalytics/ dashboard/plugin_api.py`
+- [ ] Dashboard builds: `cd dashboard && node build.js`
+- [ ] Docs updated (if applicable): `docs/` or `dev/` files reflect the change
+- [ ] `CHECKPOINT.md` updated with decisions and verification notes (rebase will drop it)
+- [ ] I am targeting `master` (or `release/X.Y` for hotfixes)

.github/workflows/ci.yml

@@ -0,0 +1,36 @@
+name: CI
+
+on:
+  push:
+    branches: [master, feat/*]
+  pull_request:
+    branches: [master]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12"]
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Set up Python ${{ matrix.python-version }}
+      uses: actions/setup-python@v5
+      with:
+        python-version: ${{ matrix.python-version }}
+
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install . ruff mypy pytest httpx pytest-github-actions-annotate-failures
+
+    - name: Lint with ruff
+      run: ruff check .
+
+    - name: Type check with mypy
+      run: mypy cronalytics/
+
+    - name: Test with pytest
+      run: pytest

.gitignore

@@ -1,5 +1,10 @@
 # Python artifacts
 __pycache__/
+*.venv/
+venv/
+ENV/
+.mypy_cache/
+.ruff_cache/
 *.py[cod]
 *$py.class
 *.egg-info/
@@ -25,6 +30,13 @@ scratchpad/
 # Auto-checkpoint state (generated at runtime)
 cronalytics-checkpoint.json
 CHECKPOINT.md
+
+# Internal planning docs — not for public repo
+PLAN.md
+AGENTS.md
+dev/AGENTS.md
+dev/LAUNCH_PLAN.md
+dev/LAUNCH_POSTS.md
 # Test artifacts
 .pytest_cache/
 .coverage
@@ -38,8 +50,6 @@ htmlcov/
 
 # Node artifacts (dashboard build)
 node_modules/
+**/node_modules/
 *.backup*
-*.bak
-facts.db-shm
-facts.db-wal
-CHECKPOINT.md
+*.bak

CHANGELOG.md

@@ -0,0 +1,72 @@
+# Changelog
+
+All notable changes to Cronalytics.
+
+---
+
+## v1.1.0 (2026-05-26)
+
+### Added
+
+- **Terminal CLI** — `cronalytics` command (via `pip install -e`) with 7 subcommands: `summary`, `jobs`, `runs`, `models`, `trends`, `health`, `all`. Full `--json` output on every data command except `all`. `--days`, `--outcome`, `--mode` filters across all commands. Leader Board spotlight in `summary`. Job name resolution from `jobs.json`.
+- **Agent Diagnostic Skill** — Built-in `cronalytics` skill with structured 7-step diagnostic workflow (time window verification → baseline health → job-level drill → per-run investigation → failure pattern → model economics → trend validation). Confidence-graded anomaly detection (HIGH / MEDIUM / LOW) with supporting evidence requirements. "Known Ways to Fool Yourself" guardrails (age-gating, script job awareness, variance checks). Cross-references `jobs.json` for scheduling context and silent failure detection.
+- **Test suite expanded to 149 tests** (83 original + 66 CLI tests) — all passing, `ruff` + `mypy` clean (note: `mypy` excludes `ingester.py`, `scanner.py`, `__init__.py`, and `dashboard/`; `disallow_untyped_defs = false`).
+- **Multilingual/Localization Support (i18n)**: coverage for [en, es, zh-CN, zh-TW]
+
+### Changed
+
+- **Package restructure** — Flat root modules moved into `cronalytics/` namespace package. Enables safe `pip install` without `site-packages` name collisions.
+- **CLI positioning** — CLI is now documented as an optional pip add-on to the dashboard plugin, not a standalone product. Requires the plugin's `facts.db` to function.
+- **Skill install** — No longer auto-linked by plugin; must be installed manually via `hermes skills install`.
+- **Trend Spikes:** Gated arrows behind 1.75x history window to prevent false alarms.
+- **UI Uniformity:** Consistent naming ("Avg Duration") and modernized icon-only refresh.
+
+---
+
+## v1.0.1 (2026-05-13)
+
+### Added
+
+- **Leader Board '% of total'** — spotlight cards show the leader's share of the window total (e.g. "42% of total cost")
+
+### Changed
+
+- **Cost card: suppressed Actual** — partial `actual_cost_usd` coverage creates misleading comparisons. The line now reads `Actual: —` until provider billing data coverage is reliable.
+
+### Fixed
+
+- **Backend fix** — synthetic script-only rows now insert `NULL` for `actual_cost_usd` (was 0.0), eliminating phantom `$0.00` aggregates.
+
+---
+
+## v1.0.0 (2026-05-12)
+
+### Added
+
+- Dashboard: Summary Board, Leader Board, Per-Model Breakdown, Jobs Breakdown table
+- Sortable 8-column jobs table with expandable detail rows
+- Job Detail Modal with full run history, sticky headers, inherited sorting
+- Outcome toggle (All/Success/Failure) with conditional Cost card colors
+- Mode toggle (All/Agent/No agent) with script job visibility
+- Pace, Nominal, and Trend projections with educational modals
+- Reconciliation scanner with watermark-based backfill
+- Bootstrap scanner on plugin load (catches post-restart gaps)
+- 83 pytest tests covering facts, parser, scanner, schedule, ingester, plugin API
+- Lint/type check: `ruff` + `mypy` clean
+- Keyboard-accessible cards and table headers (a11y)
+- Large-font theme resilience
+- API validation layer (JSDoc typedefs + runtime guards)
+
+---
+
+## v0.1.0
+
+### Added
+
+- Initial release: real-time ingestion, fact DB, reconciliation scanner, dashboard API, React frontend with summary cards, jobs table, cost-by-model, sync button.
+
+---
+
+*Plugin path: `~/.hermes/plugins/cronalytics/`*  
+*Fact DB: `~/.hermes/plugins/cronalytics/facts.db`*  
+*API base: `/api/plugins/cronalytics/`*

CODE_OF_CONDUCT.md

@@ -0,0 +1,41 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project maintainers. All complaints will be reviewed and investigated promptly and fairly.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.

CONTRIBUTING.md

@@ -13,12 +13,49 @@
 3. Tag the release (e.g., `v1.0.1`)
 4. Merge or cherry-pick the fix into `master` so it doesn't regress in the next release
 
+## How to Contribute
+
+1. **Fork the repo** and clone your fork.
+2. **Create a branch** — `feature/my-feature` or `fix/bug-description`.
+3. **Make your changes.** Keep commits focused and atomic.
+4. **Run the test suite:** `python -m pytest tests/ -v --tb=short`
+5. **Lint and type check:** `ruff check . && mypy cronalytics/ dashboard/plugin_api.py`
+6. **Build the dashboard:** `cd dashboard && node build.js`
+7. **Open a pull request** against `master` (or `release/X.Y` for hotfixes).
+
 ## Pull Requests
 
 - All changes to `master` and `release/*` branches require PR review.
 - `release/*` branches require at least 1 approving review.
 - Keep commits focused and atomic. Squash fixups before merge if the branch is noisy.
+- Use the [Pull Request Template](.github/PULL_REQUEST_TEMPLATE.md) — it gives reviewers the context they need.
+
+## Reporting Bugs
+
+Please use the [Bug Report](https://github.com/8bit64k/cronalytics/issues/new?template=bug_report.md) template. A good bug report includes:
+
+- What you did (exact steps or commands)
+- What you expected to happen
+- What actually happened (error message, incorrect output)
+- Your environment (Cronalytics version, Hermes version, OS, browser)
+
+The more specific you are, the faster we can reproduce and fix it.
+
+## Feature Requests
+
+Use the [Feature Request](https://github.com/8bit64k/cronalytics/issues/new?template=feature_request.md) template. Tell us the problem you're trying to solve, not just the solution you want. Context helps us find the right fix.
 
 ## Development Environment
 
 See [`dev/DEV_SETUP.md`](dev/DEV_SETUP.md) for build, test, and plugin setup instructions.
+
+## Code Review
+
+Reviewers will check for:
+
+- Tests pass and cover the change
+- Docs reflect new or changed behavior
+- Lint and type checks are clean
+- The change follows existing patterns and conventions in the codebase
+
+If your PR is large, open it as a draft and ask for early feedback. Small, incremental PRs review faster and merge sooner.