chore: initial public release

Initial public release of ifixai diagnostic, sourced from the
ime_benchmarks working tree. Excludes local-only artefacts
(tests/, RELEASING.md, .gitignore, specs/, caches, env files).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: n-papaioannou

.github/workflows/ci.yml

@@ -0,0 +1,71 @@
+name: CI
+
+on:
+  push:
+  pull_request:
+    branches: [main, "fix/**"]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "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 -e ".[dev]"
+
+      - name: Lint
+        run: ruff check ifixai tests
+
+      - name: Test with coverage
+        run: pytest tests/ ifixai/tests/ --cov=ifixai --cov-report=term-missing --cov-fail-under=60 -q --tb=short -m "not integration"
+
+      - name: Integration tests (disk/fixture-dependent)
+        run: pytest tests/ -q --tb=short -m integration
+
+      - name: Security scan
+        run: bandit -r ifixai -ll
+
+      - name: Docs presence check
+        run: |
+          test -f CHANGELOG.md || { echo "CHANGELOG.md missing"; exit 1; }
+          test -f CONTRIBUTING.md || { echo "CONTRIBUTING.md missing"; exit 1; }
+          test -f SECURITY.md || { echo "SECURITY.md missing"; exit 1; }
+          echo "governance docs present"
+
+  inspect-smoke:
+    runs-on: ubuntu-latest
+    needs: test
+    if: ${{ github.event_name == 'pull_request' }}
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Check OpenAI key presence
+        id: check_key
+        env:
+          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
+        run: |
+          if [ -n "$OPENAI_API_KEY" ]; then
+            echo "present=true" >> "$GITHUB_OUTPUT"
+          else
+            echo "present=false" >> "$GITHUB_OUTPUT"
+          fi
+      - name: Install with inspect extras
+        if: steps.check_key.outputs.present == 'true'
+        run: python -m pip install -e ".[dev,inspect]"
+      - name: Inspect B01 smoke
+        if: steps.check_key.outputs.present == 'true'
+        env:
+          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
+        run: inspect eval ifixai/inspect_integration/tasks.py@ifixai_b01

.pre-commit-config.yaml

@@ -0,0 +1,30 @@
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v5.0.0
+    hooks:
+      - id: check-added-large-files
+      - id: detect-private-key
+      - id: end-of-file-fixer
+      - id: trailing-whitespace
+      - id: check-yaml
+      - id: check-toml
+
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.6.9
+    hooks:
+      - id: ruff
+        args: [--fix, --exit-non-zero-on-fix]
+
+  - repo: https://github.com/gitleaks/gitleaks
+    rev: v8.21.2
+    hooks:
+      - id: gitleaks
+
+  - repo: local
+    hooks:
+      - id: no-env-files
+        name: block .env files from being committed
+        entry: refusing to commit .env files; use .env.example for tracked templates
+        language: fail
+        files: '(^|/)\.env($|\.)'
+        exclude: '\.env\.(example|sample|template)$'

CHANGELOG.md

@@ -0,0 +1,9 @@
+# Changelog
+
+All notable changes to `ifixai` will be recorded here. Format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this project uses
+[SemVer](https://semver.org/spec/v2.0.0.html).
+
+## [1.0.0] — 2026-04-27
+
+Initial public release.

CLAUDE.md

@@ -0,0 +1,65 @@
+CLAUDE.md
+Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-specific instructions as needed.
+
+Tradeoff: These guidelines bias toward caution over speed. For trivial tasks, use judgment.
+
+0. Answer Style
+Concise and direct. No long paragraphs.
+
+Prefer bullets for any answer with more than one point.
+Pair explanations with a concrete example (command, snippet, path).
+No throat-clearing ("Great question", "Let me explain", "In summary"). Start with the answer.
+
+1. Think Before Coding
+Don't assume. Don't hide confusion. Surface tradeoffs.
+
+Before implementing:
+
+State your assumptions explicitly. If uncertain, ask.
+If multiple interpretations exist, present them - don't pick silently.
+If a simpler approach exists, say so. Push back when warranted.
+If something is unclear, stop. Name what's confusing. Ask.
+2. Simplicity First
+Minimum code that solves the problem. Nothing speculative.
+
+No features beyond what was asked.
+No abstractions for single-use code.
+No "flexibility" or "configurability" that wasn't requested.
+No error handling for impossible scenarios.
+If you write 200 lines and it could be 50, rewrite it.
+Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
+
+3. Surgical Changes
+Touch only what you must. Clean up only your own mess.
+
+When editing existing code:
+
+Don't "improve" adjacent code, comments, or formatting.
+Don't refactor things that aren't broken.
+Match existing style, even if you'd do it differently.
+If you notice unrelated dead code, mention it - don't delete it.
+When your changes create orphans:
+
+Remove imports/variables/functions that YOUR changes made unused.
+Don't remove pre-existing dead code unless asked.
+The test: Every changed line should trace directly to the user's request.
+
+4. Goal-Driven Execution
+Define success criteria. Loop until verified.
+
+Transform tasks into verifiable goals:
+
+"Add validation" → "Write tests for invalid inputs, then make them pass"
+"Fix the bug" → "Write a test that reproduces it, then make it pass"
+"Refactor X" → "Ensure tests pass before and after"
+For multi-step tasks, state a brief plan:
+
+1. [Step] → verify: [check]
+2. [Step] → verify: [check]
+3. [Step] → verify: [check]
+Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.
+
+<!-- SPECKIT START -->
+Active feature plan: [specs/015-manifest-judge-cleanup/plan.md](specs/015-manifest-judge-cleanup/plan.md)
+Spec: [specs/015-manifest-judge-cleanup/spec.md](specs/015-manifest-judge-cleanup/spec.md)
+<!-- SPECKIT END -->

CONTRIBUTING.md

@@ -0,0 +1,110 @@
+# Contributing to ifixai
+
+Thanks for considering a contribution. This guide covers the mechanics of adding inspections, fixtures, providers, and running the test suite. For the behavioural contract (what the project expects from the code you write), see the root `CLAUDE.md` if it exists plus `.claude/rules/common/*.md` in the repository.
+
+## Environment setup
+
+```bash
+git clone <your-fork-url> ifixai
+cd ifixai
+python -m venv .venv
+source .venv/bin/activate
+pip install -e ".[dev]"
+pre-commit install
+```
+
+The `pre-commit install` step wires up local hooks (`gitleaks`, `ruff`, a `.env` guard, and a sanitizer regex for known-internal identifiers). Run them on demand with `pre-commit run --all-files`.
+
+Verify:
+
+```bash
+ruff check ifixai tests
+python -m pytest --cov=ifixai --cov-report=term
+```
+
+The coverage floor is declared in `.github/workflows/ci.yml`. The policy is simple: the floor is pinned at `floor(current_baseline) - 2` percentage points so a flaky test cannot accidentally erode coverage, and is ratcheted upward when a sustained improvement lands. Drop-below fails CI.
+
+## Adding a test (inspection)
+
+Each inspection is one file under `ifixai/tests/bNN_short_name.py`. The minimum contract:
+
+1. Declare the `SPEC` — a `InspectionSpec` instance with `test_id`, `name`, `category` (one of the five `InspectionCategory` values), `description`, `threshold`, `weight`, `scoring_method`, and optional `is_strategic` / `is_mandatory_minimum` flags.
+2. Implement a subclass of `BaseTest` (from `ifixai.tests.base`). Override `run()` to produce a list of `EvidenceItem`s. Use `self.pipeline.evaluate(...)` to get a pass/fail from the configured judge.
+3. Declare `required_fixture_keys: frozenset[str]` on the subclass listing every fixture key the inspection's templates reference. The fixture loader validates this at load time; inspections that reference keys the fixture doesn't provide fail fast with an actionable error.
+4. Render every prompt through `ifixai.utils.template_renderer.render(template, context)`. Direct `str.format(...)` or f-string interpolation on fixture values is forbidden — it silently leaks `{placeholder}` literals to the model when a key is missing.
+5. Register the inspection in `ifixai/tests/registry.py` (import + add to `ALL_SPECS` + `create_inspection` switch).
+6. Update `ifixai/scoring/category_weights.py` only if the inspection belongs to the strategic set.
+
+### Inspection testing
+
+Every inspection should have a companion test under `tests/test_bNN_*.py` covering at least:
+
+- `test_{inspection}_spec_invariants_unchanged` — asserts immutable fields (id, category, threshold, weight, strategic-ness).
+- Happy-path evidence generation against a fixture.
+- Failure path (provider error, empty response, malformed output).
+
+## Authoring a fixture
+
+Fixtures are YAML files under `ifixai/fixtures/`. Validate against `ifixai/fixtures/schema.json`. A fixture MUST supply every key listed in the union of every registered inspection's `required_fixture_keys`.
+
+The `x-placeholders` section of the schema (lint-only) enumerates the placeholder keys any inspection may reference. Keep it in sync when you add a inspection that references a new key.
+
+Three example fixtures live under `ifixai/fixtures/examples/`. Copy one as a starting point.
+
+## Registering a new provider
+
+Providers implement the `ChatProvider` protocol from `ifixai/providers/base.py`. Steps:
+
+1. Create `ifixai/providers/<your_provider>.py` implementing at minimum `send_message` — other capability methods may raise `NotImplementedError` if the provider does not expose them.
+2. Register the provider string in `ifixai/providers/resolver.py`.
+3. Add an optional dependency extra in `pyproject.toml` under `[project.optional-dependencies]` so users install only what they need.
+4. Do not swallow exceptions silently. If the provider has idiomatic error types, translate them into `ProviderError` (or a subclass).
+5. Add `tests/test_<your_provider>.py` with stub / mock coverage.
+
+## Running tests locally
+
+```bash
+# full suite
+python -m pytest
+
+# one module
+python -m pytest tests/test_your_thing.py
+
+# with coverage
+python -m pytest --cov=ifixai --cov-report=term-missing
+
+# ruff
+ruff check ifixai tests
+
+# type check
+mypy ifixai
+
+# security scan
+bandit -r ifixai -ll
+```
+
+## Commit conventions
+
+Follow the Conventional Commits-style prefixes used by this project:
+
+- `feat:` new user-visible feature
+- `fix:` bug fix
+- `refactor:` behaviour-preserving change
+- `docs:` documentation only
+- `test:` test-only changes
+- `chore:` tooling / housekeeping
+- `perf:` performance improvement
+- `ci:` CI configuration
+
+Keep commits small and atomic. Include a test with every `fix:` or `feat:` that changes observable behaviour.
+
+## Pull requests
+
+- Target branch: `main`.
+- Include a test plan in the PR body.
+- Confirm `ruff`, `pytest`, and `bandit` all pass locally before requesting review. `mypy` is advisory (run it locally if you touched typed surfaces, but it is not a CI gate).
+- For any inspection / fixture / provider change, paste one worked example scorecard snippet (JSON or Markdown) into the PR body. The `ifixai-results/` directory is gitignored and cannot be updated as part of a PR.
+
+## Where to ask
+
+Open a GitHub issue on the repository for questions, bug reports, or feature proposals. For security-sensitive reports see `SECURITY.md`.