amicus 0.2.0__tar.gz → 0.3.0__tar.gz

{amicus-0.2.0 → amicus-0.3.0}/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "amicus",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "One MCP server for every second-opinion model: consult, review, and delegate with the backend as a parameter.",
   "author": { "name": "Brian Connelly", "url": "https://github.com/briandconnelly" },
   "homepage": "https://github.com/briandconnelly/amicus",

{amicus-0.2.0 → amicus-0.3.0}/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "amicus",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "One MCP server for every second-opinion model: consult, review, and delegate with the backend as a parameter.",
   "author": { "name": "Brian Connelly", "url": "https://github.com/briandconnelly" },
   "homepage": "https://github.com/briandconnelly/amicus",

amicus-0.3.0/.github/copilot-instructions.md

@@ -0,0 +1,42 @@
+# Copilot code review instructions
+
+Review guidance for GitHub Copilot code review in this repository.
+`AGENTS.md` holds the rules every contributor and reviewer works under; this file adds what a reviewer needs on top of it and does not restate it.
+Rule numbers below refer to the numbered list under "Rules" in `AGENTS.md`.
+Copilot reads this file from a pull request's head branch, so the pull request that changes it is reviewed under the changed version.
+
+## Rules
+
+1. When a comment enforces a numbered `AGENTS.md` rule, name the rule number.
+   A convention that only the surrounding code establishes needs no citation; describe the pattern the change breaks instead.
+2. Never propose a new or widened contract as a review fix: a tool name, parameter, description claim, error code, value enum or result envelope the pull request did not already change, or a change to the persisted result shape.
+   The surface categories are listed in `FINGERPRINT_COVERS` (`src/amicus/schemas/fingerprint.py`); a change there moves `FINGERPRINT` (rule 10), and a persisted-shape change moves `RESULT_FORMAT` (rule 11); the test that guards each pin states the commit shape it requires.
+   A new contract is a design decision, made in a milestone plan or by the maintainer, so state the concern and say that it needs a decision.
+   Do ask that a contract the pull request changes match its implementation, its plan and its stated intent; that is a correction, and it still moves the version it touches.
+3. Never propose a hand edit to a generated pin: the `*_snapshot.json` and `*_differentials.json` files under `tests/fixtures/`, or `uv.lock`.
+   The test that guards each pin names the command that regenerates it; if a pin looks wrong, say which source of truth it disagrees with.
+   `tests/fixtures/fakebackend/` is source for the wheel-seam test and is edited by hand.
+4. Before flagging a rule-18 violation, read rule 18's exemptions from `AGENTS.md` itself and check the path against them; never flag a use of one of those exemptions, and flag every path rule 18 does not exempt.
+5. For every defect, give a concrete input or sequence that produces the wrong outcome; if you cannot, label the comment a question.
+6. Do not report what a gate command reports on its own: a lint, format, type, import-boundary or test failure, or a Markdown claim that a test pins (see Context).
+7. Put one issue in each comment, and say whether it blocks merging or is optional.
+8. When a test is added or changed, check that its assertion can fail: name the change to the code under test that would turn it red, and flag the test if there is none.
+9. When prose describes code (a tool description, a docstring, a README section, `CHANGELOG.md`, an ADR), check the claim against the source in the same pull request and flag any claim the code does not bear out.
+10. Under `docs/`, flag a prose paragraph that wraps one sentence across several lines (rule 16).
+11. Under `.github/workflows/`, check the change against rules 14, 15 and 22 and name the one it breaks.
+
+## Context
+
+### What the gate already checks
+
+Rule 2 in `AGENTS.md` defines the gate; CI runs it, preceded by the Actions-pinning check (rule 3).
+Some tests pin Markdown surfaces against the code, for example `docs/MIGRATION.md`'s tool and parameter names and the README install pin; a claim one of those tests pins is gate-covered.
+Nothing in the gate checks prose style, so rule 16, stale claims no test pins and unpinned drift between documentation and code are reviewer work.
+
+### Where the risk concentrates
+
+- Rule 18 governs every path a prompt input (`INPUT_FIELDS` in `src/amicus/request.py`) can take.
+  Any new log line, error message, argv construction, fixture or committed capture that can carry one of those values is the highest-value place to look.
+- `src/amicus/jobs/delivery.py` is the chokepoint through which every stored result is delivered; a schema gap there reaches every client.
+- `scripts/check_release_state.py`, `scripts/record_live_gate_evidence.py`, `.github/workflows/publish.yml` and `docs/RELEASING.md` implement rules 19 to 24; check that a change to one keeps the others true.
+- `tests/conftest.py` carries the rule-6 guard and `tests/support/fake_codex.py` stands in for the real CLI, so a test that would only pass with a real `codex`, `kimi` or `claude` on `PATH` is a defect.

{amicus-0.2.0 → amicus-0.3.0}/.github/workflows/publish.yml

@@ -22,7 +22,7 @@ jobs:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
           persist-credentials: false
-      - uses: astral-sh/setup-uv@20cfd1bf945f4377ade1205e4dbc17946fc9a30d # v10.0.1
+      - uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
       - run: uv build
       - run: uv run --with twine twine check dist/*
       - name: The built wheel's console script must start a real MCP server
@@ -70,7 +70,7 @@ jobs:
           persist-credentials: false
           # Full history and tags: the check reads the annotated tag OBJECT, not just the ref.
           fetch-depth: 0
-      - uses: astral-sh/setup-uv@20cfd1bf945f4377ade1205e4dbc17946fc9a30d # v10.0.1
+      - uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
       - name: The tagged tree and the tag must satisfy the release predicate
         # See scripts/check_release_state.py for what a pass does and does not prove. In
         # short: the tree's release-state coherence is proven; the live-gate record carried in

{amicus-0.2.0 → amicus-0.3.0}/.github/workflows/test.yml

@@ -19,7 +19,7 @@ jobs:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
           persist-credentials: false
-      - uses: astral-sh/setup-uv@20cfd1bf945f4377ade1205e4dbc17946fc9a30d # v10.0.1
+      - uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
         with:
           python-version: ${{ matrix.python-version }}
           enable-cache: true

{amicus-0.2.0 → amicus-0.3.0}/.mcp.json

@@ -4,7 +4,7 @@
       "command": "uvx",
       "args": [
         "--from",
-        "git+https://github.com/briandconnelly/amicus.git@v0.1.0",
+        "git+https://github.com/briandconnelly/amicus.git@v0.2.0",
         "amicus-mcp"
       ],
       "env_vars": [