0.5.11

.ails/config.yml

@@ -2,8 +2,7 @@ default_agent: claude
 exclude_dirs:
   - fixtures
   - .venv
-  - docs
-  - specs
+  - hub
   - framework
   - .mypy_cache
   - .ruff_cache

.github/workflows/release.yml

@@ -152,32 +152,18 @@ jobs:
         shell: bash
 
   publish:
-    name: Publish release
+    name: Publish to PyPI
     needs: [check-release, verify-wheel]
     runs-on: ubuntu-latest
     permissions:
-      contents: write
       id-token: write
     environment: release
     steps:
-      - uses: actions/checkout@v4
-
       - uses: actions/download-artifact@v4
         with:
           name: dist
           path: dist
 
-      - name: Create tag and GitHub release
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          VERSION="${{ needs.check-release.outputs.version }}"
-          git tag "$VERSION"
-          git push origin "$VERSION"
-          gh release create "$VERSION" \
-            --title "v$VERSION" \
-            --generate-notes
-
       - name: Publish to PyPI
         uses: pypa/gh-action-pypi-publish@release/v1
 
@@ -209,3 +195,23 @@ jobs:
         run: npm publish --access public --provenance
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+
+  tag:
+    name: Tag and GitHub release
+    needs: [check-release, publish, npm]
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Create tag and GitHub release
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          VERSION="${{ needs.check-release.outputs.version }}"
+          git tag "$VERSION"
+          git push origin "$VERSION"
+          gh release create "$VERSION" \
+            --title "v$VERSION" \
+            --generate-notes

.github/workflows/test-action.yml

@@ -34,8 +34,9 @@ jobs:
           echo "score=$SCORE"
           echo "level=$LEVEL"
           echo "violations=$VIOLATIONS"
-          [ -n "$SCORE" ] || { echo "FAIL: no score output"; exit 1; }
+          # score is intentionally empty on an offline run (no server score) — do not require it
           [ -n "$LEVEL" ] || { echo "FAIL: no level output"; exit 1; }
+          [ -n "$VIOLATIONS" ] || { echo "FAIL: no violations output"; exit 1; }
           [ -n "$RESULT" ] || { echo "FAIL: no result output"; exit 1; }
 
   pass-explicit-agent:
@@ -68,22 +69,31 @@ jobs:
 
   # --- Fail scenarios ---
 
-  fail-min-score:
-    name: "Fail: min-score gate rejects low score"
+  skip-min-score-offline:
+    name: "Pass: min-score gate skips on an offline run"
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
       - uses: ./action
-        id: should-fail
+        id: gate
         continue-on-error: true
         with:
           min-score: "11"
           from-source: "true"
-      - name: Verify failure
-        if: steps.should-fail.outcome != 'failure'
+      - name: Verify gate skipped (no server score offline)
+        env:
+          OUTCOME: ${{ steps.gate.outcome }}
+          SCORE: ${{ steps.gate.outputs.score }}
         run: |
-          echo "Expected failure from min-score=11 but got: ${{ steps.should-fail.outcome }}"
-          exit 1
+          echo "outcome=$OUTCOME score=$SCORE"
+          # Offline there is no server score, so the min-score gate logs a warning and
+          # skips rather than failing the build — even an unreachable min-score=11 passes.
+          # The score-rejection path needs a live server score and is covered by unit tests.
+          if [ "$OUTCOME" = "failure" ]; then
+            echo "FAIL: min-score gate failed the build offline (should skip)"
+            exit 1
+          fi
+          [ -z "$SCORE" ] || { echo "FAIL: expected empty score on offline run, got $SCORE"; exit 1; }
 
   fail-strict:
     name: "Fail: strict mode on violations"

.gitignore

@@ -8,8 +8,8 @@ __pycache__
 .pytest_cache
 .ruff_cache
 
-# Internal specs
-specs/
+# Internal coordination surface — private inner repo, never ships in the public CLI
+/hub/
 
 # Claude specific - Dev internals (root only; fixtures under tests/ and framework/ are tracked)
 /.claude/

.ignore

@@ -3,3 +3,4 @@
 # .ignore files with .gitignore syntax.
 framework/rules/**/**/tests/**
 tests/fixtures/**
+/archive/

README.md

@@ -1,4 +1,4 @@
-# Reporails CLI (v0.5.10)
+# Reporails CLI (v0.5.11)
 
 > **AI Instruction Diagnostics for coding agents. Validates the entire agentic instruction system against 120+ rules across six rule packs (core + per-agent). Supports Claude, Codex, Copilot, Cursor, and Gemini.**
 > 
@@ -12,36 +12,37 @@ npx @reporails/cli check
 uvx --from reporails-cli ails check
 ```
 
-No install, no account. Actionable findings in seconds - fix them, run again, watch the score improve:
+No install, no account. The headline is a single **Quality** score (the analysis service's verdict on how well-formed your instructions are); fix the findings that move it, run again, watch it climb:
 
 ```
-Reporails - Diagnostics
+Reporails — Diagnostics
 
-  ┌─ Main (4)  61 directive / 9 constraint · 71% prose
+  ┌─ Main (1)  10 directive / 1 constraint · 71% prose
   │ CLAUDE.md  10 dir / 1 con / 1 amb · 71% prose
-  │           Missing tech stack declaration - list languages, frameworks, and runtimes  CORE:C:0034
-  │           Missing MCP documentation - describe MCP server configuration if applicable  CORE:C:0027
-  │     ... and 3 more
-  │     4 brief · 1 orphan
+  │   ✗       Missing tech stack declaration — list languages, frameworks, runtimes  CORE:C:0034
+  │       → Name the languages, frameworks, and runtimes the project targets.
+  │   ⚠       'pytest' should be in backticks (×3)  CORE:E:0003
+  │       → Wrap in backticks: `pytest`
+  │     ◦ +4 lower-priority (won't move your score yet) · -v to list
+  │     ⊕ 6 Pro diagnostics (1 error) — isolated instructions, buried directives
   │
-  └─ 181 findings
-
-  [⋯ Agents (3) · Skills (10) · Rules (13)  +318 findings ⋯]
+  └─ 12 findings
 
   ── Summary ────────────────────────────────────────────────────────
 
-  Score: 7.3 / 10  ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░  (3.9s)
+  Quality   6.4 / 10  ▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░  (4.1s)
+  Findings 3 errors · 38 warnings · 12 info
   Agent: Claude
+  Level: L4 Delegated
 
   Scope:
-    instructions: 277 directive / 448 prose (56%)
-                  75 constraint / 10 ambiguous
+    instructions: 64 directive / 102 prose (61%)
+                  18 constraint / 4 ambiguous
 
-  Main (4):     ▓▓▓▓▓▓▓▓▓▓░░░░░   6.9    Rules (13):   ▓▓▓▓▓▓▓▓▓▓▓▓░░░   7.9
-  Skills (10):  ▓▓▓▓▓▓▓▓▓▓▓░░░░   7.2    Agents (3):   ▓▓▓▓▓▓▓▓▓▓░░░░░   6.9
+  Main (1):    ▓▓▓▓▓▓▓▓▓░░░░░░   6.4  1 err    Rules (2):   ▓▓▓▓▓▓▓▓▓▓▓▓░░░   7.9
+  Skills (3):  ▓▓▓▓▓▓▓▓▓▓▓░░░░   7.2           Agents (1):  ▓▓▓▓▓▓▓▓▓▓░░░░░   6.6
 
-  499 findings · 5 errors · 416 warnings · 70 info
-  2 cross-file conflicts · 7 cross-file repetitions
+  + 41 Pro diagnostics (1 error · 32 warnings) — sign in for line numbers + fix coordinates
 ```
 
 ## Install permanently
@@ -74,7 +75,7 @@ Run on every PR so instruction-quality regressions (contradictions, oversized fi
   with:
     api-key: ${{ secrets.REPORAILS_API_KEY }}   # optional - sign-in for full diagnostic detail
     strict: "true"                              # exit 1 if any rule fires
-    min-score: "7.0"                            # exit 1 if score < 7.0
+    min-score: "7.0"                            # exit 1 if Quality < 7.0
 ```
 
 Capture your API key with `ails auth token` and store it as `REPORAILS_API_KEY` in your CI secret store. See [Configuration → Authentication](https://github.com/reporails/cli/blob/main/docs/configuration.md#authentication).
@@ -86,6 +87,8 @@ Capture your API key with `ails auth token` and store it as `REPORAILS_API_KEY`
 - [Tiers and Limits](https://github.com/reporails/cli/blob/main/docs/tiers.md) - anonymous vs signed in, what each mode includes
 - [Configuration](https://github.com/reporails/cli/blob/main/docs/configuration.md) - disabling rules, project / global config, exclude paths
 - [Score Guide](https://github.com/reporails/cli/blob/main/docs/score-guide.md) - how the score is built and what it tells you
+- [Capability Levels](https://github.com/reporails/cli/blob/main/docs/capability-levels.md) - the L0-L7 ladder and what each level requires
+- [Rules CLI](https://github.com/reporails/cli/blob/main/docs/rules-cli.md) - `ails rules list --capability=skill` and friends — preflight rules before authoring
 - [FAQ](https://github.com/reporails/cli/blob/main/docs/faq.md) - common questions
 
 ## Built and validated for

UNRELEASED.md

@@ -6,6 +6,4 @@
 
 ### Fixed
 
-- [Lint]: Gate user-scope `~/...` rendering in mechanical-check attribution on the classifier's `precedence: user` property (read from agent config patterns) instead of path-prefix heuristics, so Windows tmp paths under the user profile no longer render with a `~/` prefix.
-
 ### Removed

action/action.yml

@@ -123,13 +123,17 @@ runs:
       run: |
         python3 -c "
         import sys
-        score = float('${{ steps.check.outputs.score }}')
+        raw = '${{ steps.check.outputs.score }}'.strip()
+        if not raw:
+            print('::warning::No quality score available (offline run) — skipping min-score gate')
+            sys.exit(0)
+        score = float(raw)
         threshold = float('${{ inputs.min-score }}')
         if score < threshold:
-            print(f'::error::Score {score:.1f} is below minimum threshold {threshold:.1f}')
+            print(f'::error::Quality {score:.1f} is below minimum threshold {threshold:.1f}')
             sys.exit(1)
         else:
-            print(f'Score {score:.1f} meets minimum threshold {threshold:.1f}')
+            print(f'Quality {score:.1f} meets minimum threshold {threshold:.1f}')
         "
 
     - name: Write step summary

action/parse_result.py

@@ -3,6 +3,11 @@
 
 Usage: echo '<json>' | python3 parse_result.py
 Outputs: _SCORE=X.X  _LEVEL=LN  _VIOLATIONS=N  (one per line, eval-safe)
+
+_SCORE is the analysis service's whole-project Quality verdict (the same number
+`ails check` prints), read verbatim from the `quality` key — never recomputed here.
+It is empty when no server score is available (offline run); the min-score gate
+treats an empty score as "skip".
 """
 from __future__ import annotations
 
@@ -15,26 +20,15 @@ def main() -> None:
     files = d.get("files", {})
     stats = d.get("stats", {})
 
-    n_findings = sum(f.get("count", 0) for f in files.values())
-    errors = stats.get("errors", 0)
-    warnings = stats.get("warnings", 0)
-    total = errors + warnings + stats.get("infos", 0)
-
-    if total == 0:
-        score = 10.0
-    else:
-        base = 6.0
-        denom = max(total, 1)
-        ep = min(4.0, errors / denom * 30)
-        wp = min(2.0, warnings / denom * 2)
-        score = max(0.0, min(10.0, base - ep - wp))
+    quality = d.get("quality")  # float, or None when offline / no server score
+    level = d.get("level", "L0")
+    violations = stats.get("total_findings", sum(f.get("count", 0) for f in files.values()))
 
-    score = round(score, 1)
-    level = "L0" if not files else "L1"
+    score_out = "" if quality is None else f"{float(quality):.1f}"
 
-    print(f"_SCORE={score}")
+    print(f"_SCORE={score_out}")
     print(f"_LEVEL={level}")
-    print(f"_VIOLATIONS={n_findings}")
+    print(f"_VIOLATIONS={violations}")
 
 
 if __name__ == "__main__":

docs/agent-support.md

@@ -1,8 +1,8 @@
 ---
 title: "Agent Support"
 description: "Which agents are recognized and what's covered"
-version: "0.5.10"
-last_updated: 2026-05-18
+version: "0.5.11"
+last_updated: 2026-06-06
 ---
 
 # Agent Support

docs/capability-levels.md

@@ -1,8 +1,8 @@
 ---
 title: "Capability Levels"
 description: "The ladder for where AI instructions live and how they act"
-version: "0.5.10"
-last_updated: 2026-05-19
+version: "0.5.11"
+last_updated: 2026-06-06
 ---
 
 # Capability Levels
@@ -61,8 +61,8 @@ Each rung exists because the rung below it fails in a specific way. The trigger
 | L5   | L6 | A constraint must hold 100% of the time, not 95%                                        |
 | L6   | L7 | You keep correcting the same preference across sessions                                 |
 
-Climbing without a symptom adds structure the model has to navigate without solving a problem you had. Under-climbing is more common: *"agent didn't run tests before pushing"* reads like a prompt-engineering problem but is usually a missing L6 hook; *"agent forgot we use Cloudflare Workers"* reads like context drift but is usually a missing L7 memory entry.
+Climbing without a symptom adds structure the model has to navigate without solving a problem you had. Under-climbing is more common: *"agent didn't run tests before pushing"* reads like a prompt-engineering problem but is usually a missing L6 hook; *"agent forgot we use pnpm, not npm"* reads like context drift but is usually a missing L7 memory entry.
 
 ---
 
-[← Score Guide](score-guide.md) · Capability Levels · [FAQ →](faq.md)
+[← Rules CLI](rules-cli.md) · Capability Levels · [FAQ →](faq.md)