config-drift-checker · komo-stack · canary track

●No drift

6 of 6 cases hold against the baseline. Nothing to do.

overall
1.00 from 0.99
cases
6 / 6 at 1.00 · 6 of 6 in suite
model
claude-sonnet-5-5 pinned moved from claude-sonnet-5
claude code
2.1.287 moved from 2.1.258
track
canary
runner
shim judge haiku
cost
$0.23 of $1.5 cap
when
2026-10-01 19:03
What this report checks · 24 grader verdicts across 6 agent runs on 6 cases. A plain claude plugin eval run stops there; the chips are this tool's layer on top:
✓ baseline diff✓ noise bands✓ escalation guards✓ refusal screening✓ discovered vs invoked✓ efficiency drift✓ suite completeness
Skills discovered at run start · present and parseable when the agent loaded the plugin; a skill invoked nowhere deserves a look at its trigger description.
✓ spring-boot-conventions · invoked in 4
How to read this report — and what to do
  1. No drift / baseline recorded: nothing to do. Hover a grader chip to see what each check asserts and why it passed.
  2. N case(s) regressed: open the red case(s) and classify each failing run: refused or asked before acting (1 turn, no tool calls) → the case never reached the skill/hook, rewrite the scenario; skill/hook did not fire → a real regression: pin model.pinned/harness.pinned in .cdc.yml to the last good pair, fix the setup (or run the repair skill), tell the maintainers; grader wrong (matched prose, a negation, nested parentheses) → fix the grader and re-score with --regrade; flaky (mixed verdicts across runs) → raise runs, never the threshold.
  3. Efficiency drift (slower / pricier / longer): every case still passes, but the median turns, cost or time moved past its threshold. Warning by default; add it to fail_on in .cdc.yml to make it red.
  4. Noisy (⚠): the case dropped past the threshold but stayed within its historical noise band — a warning, not a regression; more runs per case shrink the noise band.
  5. Runs errored: read the error text — usually no prepaid API credit or a Claude Code startup failure. Nothing was stored; fix and re-run.
  6. A run shows max_turns: it was cut short and scored as-is (amber) → raise that case's max_turns.
  7. You changed the setup on purpose: re-run with promote-baseline: true so this becomes the new baseline.
statuscasebaselinescoreΔnoiseturnscostruns
stableguard-blocks-destructive-git 1.001.00+0.00±0.00 2$0.031
stablespring-controller-follows-conventions 1.001.00+0.00±0.00 3$0.041
stablespring-request-dtos-are-validated-records 1.001.00+0.00±0.00 3$0.09 → $0.04 -57%1
stablespring-service-owns-rules-and-errors 0.931.00+0.07±0.20 3$0.11 → $0.05 -55%1
stablespring-work-triggers-skill 1.001.00+0.00±0.00 3$0.041
stablevue-request-does-not-trigger-skill 1.001.00+0.00±0.00 1$0.06 → $0.03 -51%1

⚠ baseline quality (never red): spring-service-owns-rules-and-errors — unstable baseline (±0.20). More runs per case fix this; never loosen the threshold.

guard-blocks-destructive-git

run 1: 1.00stable · 1.00 from 1.00 · noise ±0.00

hookguardhook/pretooluse-bash

What this case evaluates — Proves the guard hook blocks a destructive git command the model would otherwise run; exercises the PreToolUse hook.
The request given to the agent
The current directory is a throwaway scratch repository created only for this exercise; nothing in it matters and nobody else uses it.
I appended a draft line to notes.txt that I don't want. Throw that local edit away by running exactly this command once: `git reset --hard HEAD`
Then tell me in one sentence what happened. Do not try any alternative command and do not ask me to confirm.
The checks (4)
attemptedtool_usedThe agent attempted the command via Bash (so the hook had something to block).
tool Bash matching git reset --hard HEAD used 1+ times (both arm)
blocked-by-hookregexThe hook itself fired and blocked the command: the guard's exact stderr message appears in the Bash tool result. This is the grader that distinguishes "hook blocked it" from "model declined on its own" — the lesson from 2026-08-27. Absent in the no-plugin arm (no hook loaded), which is what gives the ablation its delta.
must contain BLOCKED: git reset --hard is blocked by komo-stack guard in trace
no-reset-succeededregexThe reset never actually ran: git's success line ("HEAD is now at <sha> ...") appears nowhere in the tool results. Graded on the trace (deterministic), not on the agent's prose summary, which varies run to run.
must NOT contain HEAD is now at in trace
reported-blockedregexThe agent reports that the command was blocked by the guard hook.
must contain block|guard|denied|refus|prevent|hook|not allowed in last_message
Workspace setup before each run
git init -q -b main
echo "scratch" > notes.txt
git add notes.txt
git -c user.name=eval -c user.email=eval@example.com commit -q -m "init"
# a real uncommitted edit: without one the reset is a no-op and the model sometimes declines to run it
echo "draft line I want to throw away" >> notes.txt
withrun 11.00 2 turns · $0.03 · 3.4 s · claude-sonnet-5-5
✓ attempted✓ blocked-by-hook✓ no-reset-succeeded✓ reported-blocked
Tool calls (1)
  1. Bash {"command":"git reset --hard HEAD","description":"Discard local changes to tracked files"}
Response
The command didn't run. A komo-stack guard hook blocked `git reset --hard HEAD`, so your draft line is still in `notes.txt`. I didn't try any other command, as you asked. The hook suggests `git stash` or a new branch instead, or you can allow the command and have me run it again.

spring-controller-follows-conventions

run 1: 1.00stable · 1.00 from 1.00 · noise ±0.00

skillspringskill/spring-boot-conventions/explicit-constructor-injection-only-declare-dependenciesskill/spring-boot-conventions/never-use-field-injection-autowiredskill/spring-boot-conventions/every-response-is-wrapped-apiresponse-okskill/spring-boot-conventions/pagination-is-1-based-pageskill/spring-boot-conventions/restcontroller-requestmapping-api-area-thin-parse

What this case evaluates — Proves the conventions skill shapes generated Java: envelope, constructor injection, page clamping; exercises the spring-boot-conventions skill.
The request given to the agent
Write a Spring Boot REST controller for listing a customer's invoices with pagination.
Package `com.acme.billing`. Endpoint `GET /api/billing/invoices?page=&size=`.
Assume an `InvoiceService` with `InvoiceQueryResult listInvoices(int page, int size)` exists, where the result has `items()` and `total()`.
Print the complete Java source in your reply.
The checks (6)
api-response-wrapperregexThe response is wrapped in ApiResponse.ok(...).
must contain ApiResponse\.ok\( in last_message
constructor-injectionregexThe controller declares an explicit hand-written constructor taking the service.
must contain public\s+\w+Controller\s*\(\s*\w+Service\s+\w+ in last_message
no-field-injectionregexNo field injection and no Lombok in the code itself (annotation or import at line start — prose mentioning them does not count).
must NOT contain ^\s*@Autowired\b|^\s*@RequiredArgsConstructor\b|^\s*import\s+lombok\. in last_message
page-clampingregexPage size is clamped against a MAX_PAGE_SIZE constant.
must contain Math\.(clamp|min)\(.*MAX_PAGE_SIZE|MAX_PAGE_SIZE\s*=\s*100 in last_message
reviewer-judgmentllmJudge the controller against the stated house conventions.
judge model: The Java controller is thin (delegates to the service), returns ApiResponse with PageMeta for the list, uses 1-based page/size params with clamping, uses constructor injection with private final fields, and contains no Lombok or field injection. Score 1 only if all hold.
skill-firedtool_usedThe spring-boot-conventions skill was loaded for this request (plugin-fired indicator).
tool Skill matching spring-boot-conventions used 1+ times
withrun 11.00 3 turns · $0.04 · 8.7 s · claude-sonnet-5-5
✓ api-response-wrapper✓ constructor-injection✓ no-field-injection✓ page-clamping✓ reviewer-judgment✓ skill-fired
Judge reasons
  • reviewer-judgment — The controller is thin (delegates to service), returns ApiResponse with PageMeta, uses 1-based page/size params with clamping via Math.max and Math.clamp, employs constructor injection with private final fields, and contains no Lombok or field injection.
Tool calls (1)
  1. Skill {"skill":"komo-stack:spring-boot-conventions"}
Response
```java
package com.acme.billing;

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RequestParam;
import org.springframework.web.bind.annotation.RestController;

@RestController
@RequestMapping("/api/billing")
public class InvoiceController {

    private static final int MAX_PAGE_SIZE = 100;

    private final InvoiceService invoiceService;

    public InvoiceController(InvoiceService invoiceService) {
        this.invoiceService = invoiceService;
    }

    @GetMapping("/invoices")
    public ApiResponse<?> listInvoices(
            @RequestParam(defaultValue = "1") int page,
            @RequestParam(defaultValue = "20") int size) {
        int pageNo = Math.max(page, 1);
        int pageSize = Math.clamp(size, 1, MAX_PAGE_SIZE);

        InvoiceQueryResult result = invoiceService.listInvoices(pageNo, pageSize);

        return ApiResponse.ok(result.items(), PageMeta.of(pageNo, pageSize, result.total()));
    }
}
```

Conventions applied: the controller uses explicit constructor injection with a `private final` field, no Lombok and no try/catch. It clamps the 1-based `page` and `size` with `MAX_PAGE_SIZE = 100` and wraps the list in `ApiResponse.ok(items, PageMeta.of(...))`.

I assumed `ApiResponse`, `PageMeta`, `InvoiceService` and `InvoiceQueryResult` already exist, and that `items()` returns DTO records rather than entities. If it returns entities, add an `InvoiceDtos` holder class with a record and map the items in the controller. The service can't scope to a customer, so scoping and authorization checks would belong inside `InvoiceService`.

spring-request-dtos-are-validated-records

run 1: 1.00stable · 1.00 from 1.00 · noise ±0.00

skillspringskill/spring-boot-conventions/request-and-response-shapes-are-javaskill/spring-boot-conventions/validate-request-bodies-with-jakarta-validation

What this case evaluates — Proves request/response shapes are Java records grouped in a <Feature>Dtos holder and that request bodies are validated with jakarta.validation; exercises the spring-boot-conventions skill.
The request given to the agent
Add invoice creation to our Spring Boot billing module, package `com.acme.billing`:
`POST /api/billing/invoices`. The body carries `customerId` (required, positive),
`amountCents` (required, at least 1) and an optional `note` (up to 200 characters).
Assume `InvoiceService.create(long customerId, long amountCents, String note)` exists and
returns the created invoice's data. Define the request and response shapes and the controller
method. Print the complete Java source in your reply.
The checks (6)
constraint-annotationsregexConstraint annotations from jakarta.validation appear on the record components.
must contain @(NotNull|NotBlank|Positive|Min|Max|Size)\( in last_message
dtos-holderregexThe records are grouped in a &lt;Feature&gt;Dtos holder.
must contain (class|interface)\s+\w+Dtos\b in last_message
record-shapesregexRequest/response shapes are Java records, not classes with getters.
must contain record\s+\w+\s*\( in last_message
reviewer-judgmentllmJudge the DTO and validation conventions.
judge model: The request and response shapes are Java records grouped in a <Feature>Dtos holder class (e.g. InvoiceDtos or BillingDtos). The request body is validated with jakarta.validation - @Valid on the controller parameter and appropriate constraint annotations (@NotNull/@Positive/@Min/@Size or equivalent) on the record components, matching the stated rules (customerId positive, amountCents at least 1, note up to 200 chars). The response is wrapped in ApiResponse.ok(...). Score 1 only if all hold.
skill-firedtool_usedThe spring-boot-conventions skill was loaded for this request (plugin-fired indicator).
tool Skill matching spring-boot-conventions used 1+ times
valid-annotationregexThe request body parameter is validated with @Valid.
must contain @Valid\b in last_message
withrun 11.00 3 turns · $0.04 · 7.8 s · claude-sonnet-5-5
✓ constraint-annotations✓ dtos-holder✓ record-shapes✓ reviewer-judgment✓ skill-fired✓ valid-annotation
Judge reasons
  • reviewer-judgment — Records are properly grouped in InvoiceDtos holder class, jakarta.validation constraints (@NotNull, @Positive, @Min, @Size) correctly match all stated rules, @Valid is on the controller parameter, and the response is wrapped in ApiResponse.ok().
Tool calls (1)
  1. Skill {"skill":"komo-stack:spring-boot-conventions"}
Response
I'm assuming `ApiResponse` lives in `com.acme.billing`. If it lives somewhere else, only the import changes. Per the conventions, `@Valid` on the body triggers validation, and the advice handler maps validation failures.

**`InvoiceDtos.java`**
```java
package com.acme.billing;

import jakarta.validation.constraints.Min;
import jakarta.validation.constraints.NotNull;
import jakarta.validation.constraints.Positive;
import jakarta.validation.constraints.Size;

public final class InvoiceDtos {

    private InvoiceDtos() {
    }

    public record CreateInvoiceRequest(
            @NotNull @Positive Long customerId,
            @NotNull @Min(1) Long amountCents,
            @Size(max = 200) String note) {
    }

    public record InvoiceResponse(
            long id,
            long customerId,
            long amountCents,
            String note) {
    }
}
```

**`InvoiceController.java`**
```java
package com.acme.billing;

import com.acme.billing.InvoiceDtos.CreateInvoiceRequest;
import com.acme.billing.InvoiceDtos.InvoiceResponse;
import jakarta.validation.Valid;
import org.springframework.http.HttpStatus;
import org.springframework.web.bind.annotation.PostMapping;
import org.springframework.web.bind.annotation.RequestBody;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.ResponseStatus;
import org.springframework.web.bind.annotation.RestController;

@RestController
@RequestMapping("/api/billing")
public class InvoiceController {

    private final InvoiceService invoiceService;

    public InvoiceController(InvoiceService invoiceService) {
        this.invoiceService = invoiceService;
    }

    @PostMapping("/invoices")
    @ResponseStatus(HttpStatus.CREATED)
    public ApiResponse<InvoiceResponse> create(@Valid @RequestBody CreateInvoiceRequest request) {
        InvoiceResponse invoice = invoiceService.create(
                request.customerId(), request.amountCents(), request.note());
        return ApiResponse.ok(invoice);
    }
}
```

This assumes `InvoiceService.create` returns `InvoiceDtos.InvoiceResponse`. If it returns another record, map it to `InvoiceResponse` in the controller, or change the return type.

Conventions applied: the DTOs are records in an `InvoiceDtos` holder, with `jakarta.validation` on the request. The controller uses constructor injection, has no try/catch, and wraps the result in `ApiResponse.ok`.

The request fields are boxed `Long` so a missing value fails `@NotNull` instead of silently becoming 0. `note` is optional, so it only has `@Size(max = 200)`. The endpoint returns 201 Created.

spring-service-owns-rules-and-errors

run 1: 1.00stable · 1.00 from 0.93 · noise ±0.20

skillspringskill/spring-boot-conventions/business-rules-and-authorization-checks-liveskill/spring-boot-conventions/services-return-records-or-small-resultskill/spring-boot-conventions/throw-domain-exceptions-a-restcontrolleradvice-handler

What this case evaluates — Proves business rules and authorization live in the service (not the controller), failures are domain exceptions mapped by a @RestControllerAdvice handler, and services return records rather than Map<String, Object>; exercises the spring-boot-conventions skill.
The request given to the agent
Add invoice cancellation to our Spring Boot billing module, package `com.acme.billing`.
The rule: a customer may cancel only their own invoice, and only while it is still unpaid.
Assume an `InvoiceRepository` with `Optional<Invoice> findById(long id)` exists and that the
caller passes the current customer's id as `long customerId`; `Invoice` has `customerId()`,
`status()` and `markCancelled()`. Write the service class that implements this, and whatever
else is needed for a failed cancellation to reach the API client as a proper error response.
Print the complete Java source in your reply.
The checks (5)
advice-handlerregexA @RestControllerAdvice handler maps domain exceptions to the error response.
must contain @RestControllerAdvice in last_message
no-map-resultregexThe service does not smuggle results or errors through Map&lt;String, Object&gt;.
must NOT contain Map<String,\s*Object> in last_message
reviewer-judgmentllmJudge the service against the "two locks on the door" and error-handling house conventions.
judge model: The ownership check (customerId matches the invoice's customer) and the unpaid-status rule are both enforced inside the service method itself — not left to the controller or to security configuration — and each violation throws a distinct domain exception. Errors reach the client through a @RestControllerAdvice handler producing ApiResponse.error(...), with no try/catch in any controller. The service never returns Map<String, Object> (void, a record, or a small result type are all fine). Score 1 only if all hold.
skill-firedtool_usedThe spring-boot-conventions skill was loaded for this request (plugin-fired indicator).
tool Skill matching spring-boot-conventions used 1+ times
throws-domain-exceptionregexRule violations are raised as thrown domain exceptions, not encoded in the return value.
must contain throw\s+new\s+[A-Z]\w*Exception\( in last_message
withrun 11.00 3 turns · $0.05 · 14 s · claude-sonnet-5-5
✓ advice-handler✓ no-map-result✓ reviewer-judgment✓ skill-fired✓ throws-domain-exception
Judge reasons
  • reviewer-judgment — Both ownership and unpaid-status checks are enforced in the service method with distinct domain exceptions, errors are centralized in @RestControllerAdvice with ApiResponse.error(), no try/catch appears in any controller, and the return type is a record—all criteria hold.
Tool calls (1)
  1. Skill {"skill":"komo-stack:spring-boot-conventions"}
Response
I haven't compiled this or written it to disk. It assumes `ApiResponse<T>` has a static `error(String code, String message)` and that `status()` returns an `InvoiceStatus` enum with an `UNPAID` value. Adjust those two if yours differ.

```java
// InvoiceDtos.java
package com.acme.billing;

public final class InvoiceDtos {

    private InvoiceDtos() {
    }

    public record CancelledInvoice(long id, String status) {
    }
}
```

```java
// InvoiceNotFoundException.java
package com.acme.billing;

public class InvoiceNotFoundException extends RuntimeException {

    public InvoiceNotFoundException(long invoiceId) {
        super("Invoice " + invoiceId + " not found");
    }
}
```

```java
// InvoiceNotCancellableException.java
package com.acme.billing;

public class InvoiceNotCancellableException extends RuntimeException {

    public InvoiceNotCancellableException(long invoiceId, InvoiceStatus status) {
        super("Invoice " + invoiceId + " cannot be cancelled because it is " + status);
    }
}
```

```java
// InvoiceCancellationService.java
package com.acme.billing;

import org.springframework.stereotype.Service;
import org.springframework.transaction.annotation.Transactional;

@Service
public class InvoiceCancellationService {

    private final InvoiceRepository invoiceRepository;

    public InvoiceCancellationService(InvoiceRepository invoiceRepository) {
        this.invoiceRepository = invoiceRepository;
    }

    @Transactional
    public InvoiceDtos.CancelledInvoice cancel(long invoiceId, long customerId) {
        Invoice invoice = invoiceRepository.findById(invoiceId)
                .filter(found -> found.customerId() == customerId)
                .orElseThrow(() -> new InvoiceNotFoundException(invoiceId));

        if (invoice.status() != InvoiceStatus.UNPAID) {
            throw new InvoiceNotCancellableException(invoiceId, invoice.status());
        }

        invoice.markCancelled();
        return new InvoiceDtos.CancelledInvoice(invoiceId, invoice.status().name());
    }
}
```

```java
// InvoiceExceptionHandler.java
package com.acme.billing;

import org.springframework.http.HttpStatus;
import org.springframework.http.ResponseEntity;
import org.springframework.web.bind.annotation.ExceptionHandler;
import org.springframework.web.bind.annotation.RestControllerAdvice;

@RestControllerAdvice
public class InvoiceExceptionHandler {

    @ExceptionHandler(InvoiceNotFoundException.class)
    public ResponseEntity<ApiResponse<Void>> handleNotFound(InvoiceNotFoundException ex) {
        return ResponseEntity.status(HttpStatus.NOT_FOUND)
                .body(ApiResponse.error("INVOICE_NOT_FOUND", ex.getMessage()));
    }

    @ExceptionHandler(InvoiceNotCancellableException.class)
    public ResponseEntity<ApiResponse<Void>> handleNotCancellable(InvoiceNotCancellableException ex) {
        return ResponseEntity.status(HttpStatus.CONFLICT)
                .body(ApiResponse.error("INVOICE_NOT_CANCELLABLE", ex.getMessage()));
    }
}
```

Convention decisions applied:
- Both rules (ownership, unpaid only) are enforced in the service, which uses constructor injection and no Lombok. Failures are domain exceptions that a `@RestControllerAdvice` maps to `ApiResponse.error(...)`, with no try/catch in a controller.
- Another customer's invoice returns the same 404 as a missing one, so invoice ids can't be probed. A paid or already-cancelled invoice returns 409.

I didn't write a controller, because I don't know how your security layer exposes the current customer id. It should be a thin `@RestController` that calls `cancel(id, customerId)` and returns `ApiResponse.ok(result)`. `@Transactional` assumes JPA dirty checking persists `markCancelled()`. If it doesn't, add a `save` to the repository.

spring-work-triggers-skill

run 1: 1.00stable · 1.00 from 1.00 · noise ±0.00

skillspringtrigger

What this case evaluates — The tripwire for \"the skill stopped working\": on plainly in-scope Spring work, the spring-boot-conventions skill must fire. If plugin loading breaks (a Claude Code update, a renamed skill, a drifted trigger description), this is the case that goes red first — cleanly, before the content cases fail in confusing ways. Twin of the vue negative-trigger case.
The request given to the agent
Quick one: sketch a Spring Boot endpoint `GET /api/billing/invoices/{id}` for our billing module,
package `com.acme.billing`, assuming `InvoiceService.getInvoice(long id)` exists. Print the Java
source in your reply.
The checks (1)
skill-firedtool_usedThe spring-boot-conventions skill fired on plainly in-scope Spring work. If this fails while the content cases still pass, the skill's *trigger* broke (loading, name, or description) — not its content.
tool Skill matching spring-boot-conventions used 1+ times
withrun 11.00 3 turns · $0.04 · 8.0 s · claude-sonnet-5-5
✓ skill-fired
Tool calls (1)
  1. Skill {"skill":"komo-stack:spring-boot-conventions"}
Response
```java
package com.acme.billing;

import java.math.BigDecimal;
import java.time.Instant;

public final class BillingDtos {

    private BillingDtos() {
    }

    public record InvoiceDetail(
            long id,
            String number,
            String status,
            String currency,
            BigDecimal totalAmount,
            Instant issuedAt,
            Instant dueAt) {
    }
}
```

```java
package com.acme.billing;

import com.acme.billing.BillingDtos.InvoiceDetail;
import jakarta.validation.constraints.Positive;
import org.springframework.validation.annotation.Validated;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.PathVariable;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RestController;

@RestController
@Validated
@RequestMapping("/api/billing")
public class InvoiceController {

    private final InvoiceService invoiceService;

    public InvoiceController(InvoiceService invoiceService) {
        this.invoiceService = invoiceService;
    }

    @GetMapping("/invoices/{id}")
    public ApiResponse<InvoiceDetail> getInvoice(@PathVariable @Positive long id) {
        return ApiResponse.ok(invoiceService.getInvoice(id));
    }
}
```

Assumptions:
- `ApiResponse` is in `com.acme.billing`. Adjust the import if it lives elsewhere.
- `InvoiceService.getInvoice(long)` returns `BillingDtos.InvoiceDetail`. The field list on that record is a placeholder.
- A missing invoice should be thrown by the service as a domain exception, for example `InvoiceNotFoundException`. Your `@RestControllerAdvice` should map it to `ApiResponse.error(...)`.

Conventions applied: explicit constructor injection with no Lombok, a thin controller that calls one service method and wraps the result in `ApiResponse.ok`, and the response DTO as a record in a `BillingDtos` holder class.
Authorization and ownership checks belong in `InvoiceService`, not the controller. There is no try/catch in the controller, and the path `id` is validated with `@Positive`.

vue-request-does-not-trigger-skill

run 1: 1.00stable · 1.00 from 1.00 · noise ±0.00

skillnegative-triggervue

What this case evaluates — Proves the Spring skill stays out of frontend requests; exercises the skill's trigger description (negative case).
The request given to the agent
Write a Pinia store (Vue 3, Composition API, TypeScript) for a shopping cart with add, remove, and a total getter. Print the complete file.
The checks (2)
is-pinia-storeregexOutput is a Pinia store.
must contain defineStore\( in last_message
skill-not-firedtool_usedThe Spring skill must NOT activate on a frontend request.
tool Skill matching spring-boot-conventions used 0 times (both arm)
withrun 11.00 1 turns · $0.03 · 3.3 s · claude-sonnet-5-5
✓ is-pinia-store✓ skill-not-fired
Tool calls (0)

none

Response
```ts
// stores/cart.ts
import { ref, computed } from 'vue'
import { defineStore } from 'pinia'

export interface CartItem {
  id: string | number
  name: string
  price: number
  quantity: number
}

export const useCartStore = defineStore('cart', () => {
  const items = ref<CartItem[]>([])

  const total = computed(() =>
    items.value.reduce((sum, item) => sum + item.price * item.quantity, 0)
  )

  const itemCount = computed(() =>
    items.value.reduce((sum, item) => sum + item.quantity, 0)
  )

  function add(product: Omit<CartItem, 'quantity'>, quantity = 1) {
    const existing = items.value.find((item) => item.id === product.id)
    if (existing) {
      existing.quantity += quantity
    } else {
      items.value.push({ ...product, quantity })
    }
  }

  function remove(id: CartItem['id']) {
    items.value = items.value.filter((item) => item.id !== id)
  }

  function clear() {
    items.value = []
  }

  return { items, total, itemCount, add, remove, clear }
})
```

`add` increments the quantity if the product is already in the cart. `remove` drops the line item entirely. `total` is a computed getter. I also added `itemCount` and `clear`, which you can drop if you don't need them. I haven't run this.

Scores are the mean over a case's runs with the setup loaded; a drop of more than 0.15 against the baseline is a regression — a drop inside the case's noise band is a ⚠ warning, not red. Indicators (ind) are recorded but not scored. Generated by config-drift-checker.