@givolt/i3-composer-agent 2.0.0 → 2.1.0

package/evals/fixtures/i3-deprecation-and-migration/api-inventory.md

@@ -1,9 +0,0 @@
-# v1 API inventory
-
-- Public consumers: 200 organizations.
-- Replacement: `/v2/orders`, available in production but not yet announced.
-- Current v1 traffic: 48,000 requests/day from 173 active API keys.
-- Largest consumer contract requires 90 days' notice for breaking changes.
-- Existing telemetry records API key, route, status, and response latency.
-- Support can contact 188 consumers directly; 12 use reseller-managed accounts.
-- v1 currently has no response deprecation headers or migration guide.

package/evals/fixtures/i3-documentation-and-adrs/decision-context.md

@@ -1,16 +0,0 @@
-# Orders architecture decision context
-
-The orders service currently stores mutable order rows and emits best-effort
-webhooks. Auditors need a complete history of state transitions, and support
-must be able to reconstruct an order at a prior point in time.
-
-Options discussed:
-
-1. Keep the current model and add an append-only audit table.
-2. Adopt event sourcing for orders and build read projections.
-3. Use database change-data capture as the audit history.
-
-Event sourcing improves traceability and replay, but adds projection rebuilds,
-event versioning, eventual consistency, and operational complexity. The team
-has event-stream experience, but the reporting service expects synchronous
-reads. The decision applies only to the orders bounded context.

package/evals/fixtures/i3-doubt-driven-development/migration-plan.md

@@ -1,19 +0,0 @@
-# Customer identifier migration
-
-Plan: replace integer customer IDs with UUIDs in a single maintenance window.
-
-1. Disable writes.
-2. Run `ALTER TABLE customers DROP COLUMN id CASCADE`.
-3. Add a UUID `id` column and populate it.
-4. Re-enable writes after fifteen minutes.
-
-Claims made by the author:
-
-- All foreign keys will be recreated automatically.
-- The table contains fewer than one million rows.
-- The operation completes within the maintenance window.
-- The backup from last night is sufficient rollback protection.
-- No external systems persist the integer identifier.
-
-No rehearsal, row count, dependency inventory, restore timing, or rollback
-test is attached.

package/evals/fixtures/i3-frontend-ui-engineering/Button.tsx

@@ -1,7 +0,0 @@
-import { forwardRef, type ButtonHTMLAttributes } from 'react';
-
-export const Button = forwardRef<HTMLButtonElement, ButtonHTMLAttributes<HTMLButtonElement>>(
-  function Button({ className = '', ...props }, ref) {
-    return <button ref={ref} className={`button ${className}`.trim()} {...props} />;
-  },
-);

package/evals/fixtures/i3-frontend-ui-engineering/design-system.md

@@ -1,11 +0,0 @@
-# Menu component conventions
-
-- Framework: React with TypeScript.
-- Styling: existing `menu-*` utility classes; do not add a styling dependency.
-- Public components accept `className` and forward a DOM ref.
-- Components must support keyboard-only and screen-reader users.
-- Focus returns to the trigger when a menu closes.
-- Escape closes the menu; arrow keys move between enabled items.
-
-The new dropdown should expose a trigger label and an array of actions. Disabled
-actions remain visible but cannot receive focus or execute.

package/evals/fixtures/i3-git-workflow-and-versioning/.eval/working-tree.patch

@@ -1,21 +0,0 @@
-diff --git a/i3-git-workflow-and-versioning/app.js b/i3-git-workflow-and-versioning/app.js
---- a/i3-git-workflow-and-versioning/app.js
-+++ b/i3-git-workflow-and-versioning/app.js
-@@ -1,7 +1,15 @@
- 'use strict';
-
--function total(items) {
-+function sumPrices(items) {
-   return items.reduce((sum, item) => sum + item.price, 0);
-+}
-+
-+function total(items) {
-+  return Math.round(sumPrices(items) * 100) / 100;
- }
-
--module.exports = { total };
-+function exportCsv(items) {
-+  return ['price', ...items.map((item) => item.price)].join('\n');
-+}
-+
-+module.exports = { exportCsv, total };

package/evals/fixtures/i3-git-workflow-and-versioning/app.js

@@ -1,7 +0,0 @@
-'use strict';
-
-function total(items) {
-  return items.reduce((sum, item) => sum + item.price, 0);
-}
-
-module.exports = { total };

package/evals/fixtures/i3-git-workflow-and-versioning/app.test.js

@@ -1,9 +0,0 @@
-'use strict';
-
-const assert = require('node:assert/strict');
-const test = require('node:test');
-const { total } = require('./app');
-
-test('totals item prices', () => {
-  assert.equal(total([{ price: 1 }, { price: 2 }]), 3);
-});

package/evals/fixtures/i3-incremental-implementation/reports.js

@@ -1,7 +0,0 @@
-'use strict';
-
-function visibleReports(reports) {
-  return reports.filter((report) => !report.archived);
-}
-
-module.exports = { visibleReports };

package/evals/fixtures/i3-incremental-implementation/reports.test.js

@@ -1,12 +0,0 @@
-'use strict';
-
-const assert = require('node:assert/strict');
-const test = require('node:test');
-const { visibleReports } = require('./reports');
-
-test('hides archived reports', () => {
-  assert.deepEqual(visibleReports([
-    { id: 1, archived: false },
-    { id: 2, archived: true },
-  ]), [{ id: 1, archived: false }]);
-});

package/evals/fixtures/i3-incremental-implementation/tasks/plan.md

@@ -1,8 +0,0 @@
-# CSV export plan
-
-1. Add a pure report-to-CSV formatter with unit tests.
-2. Add a download adapter that uses the formatter.
-3. Wire an Export button to the reports page.
-
-Each task must be independently verified and committed before starting the
-next. Existing report filtering behavior must remain unchanged.

package/evals/fixtures/i3-observability-and-instrumentation/operations.md

@@ -1,11 +0,0 @@
-# Payment retry operations
-
-On-call must be able to answer:
-
-- Are retries recovering transient gateway failures?
-- Which gateway and failure class is driving exhaustion?
-- Is one payment being charged more than once?
-- Which customer-visible payments need intervention now?
-
-Payment and attempt IDs are safe correlation identifiers. Card numbers,
-customer email addresses, and raw gateway responses must never be logged.

package/evals/fixtures/i3-observability-and-instrumentation/payment-retry.js

@@ -1,14 +0,0 @@
-'use strict';
-
-async function retryPayment(payment, gateway) {
-  for (let attempt = 1; attempt <= 3; attempt++) {
-    try {
-      return await gateway.charge(payment);
-    } catch (error) {
-      console.log(`retry ${attempt} failed: ${error.message}`);
-    }
-  }
-  throw new Error('payment failed');
-}
-
-module.exports = { retryPayment };

package/evals/fixtures/i3-performance-optimization/benchmark.js

@@ -1,15 +0,0 @@
-'use strict';
-
-const { performance } = require('node:perf_hooks');
-const { renderProducts } = require('./products');
-
-const products = Array.from({ length: 1000 }, (_, id) => ({
-  id,
-  name: `Product ${id}`,
-  sales: (id * 7919) % 10000,
-}));
-
-const start = performance.now();
-const output = renderProducts(products);
-const elapsed = performance.now() - start;
-console.log(JSON.stringify({ products: products.length, bytes: output.length, elapsedMs: elapsed }));

package/evals/fixtures/i3-performance-optimization/products.js

@@ -1,14 +0,0 @@
-'use strict';
-
-function renderProducts(products) {
-  let html = '';
-  for (const product of products) {
-    const rank = [...products]
-      .sort((a, b) => b.sales - a.sales)
-      .findIndex((candidate) => candidate.id === product.id) + 1;
-    html += `<li data-rank="${rank}">${product.name}: ${product.sales}</li>`;
-  }
-  return `<ul>${html}</ul>`;
-}
-
-module.exports = { renderProducts };

package/evals/fixtures/i3-planning-and-task-breakdown/notifications-spec.md

@@ -1,18 +0,0 @@
-# Notifications specification
-
-Users can opt into email notifications when a task is assigned or becomes
-overdue. Preferences are stored per user and default to disabled. Assignment
-events already exist; overdue detection runs every fifteen minutes.
-
-Requirements:
-
-- Add preference read/update endpoints with boundary validation.
-- Publish notification jobs from assignment and overdue flows.
-- Deduplicate jobs by user, task, event type, and event version.
-- Send email through the existing provider adapter.
-- Record delivery status without storing message bodies.
-- Feature flag the sending path; disabled remains the safe default.
-
-Verification must include preference API tests, job deduplication tests,
-provider-adapter integration tests, and one end-to-end assignment scenario.
-No SMS, push notifications, or notification history UI is in scope.

package/evals/fixtures/i3-security-and-hardening/webhook.js

@@ -1,11 +0,0 @@
-'use strict';
-
-async function previewWebhook(url, fetchImpl = fetch) {
-  const response = await fetchImpl(url, { redirect: 'follow' });
-  return {
-    status: response.status,
-    body: (await response.text()).slice(0, 2048),
-  };
-}
-
-module.exports = { previewWebhook };

package/evals/fixtures/i3-security-and-hardening/webhook.test.js

@@ -1,13 +0,0 @@
-'use strict';
-
-const assert = require('node:assert/strict');
-const test = require('node:test');
-const { previewWebhook } = require('./webhook');
-
-test('returns a bounded preview from a successful request', async () => {
-  const result = await previewWebhook('https://example.com/hook', async () => ({
-    status: 200,
-    text: async () => 'ok',
-  }));
-  assert.deepEqual(result, { status: 200, body: 'ok' });
-});

package/evals/fixtures/i3-shipping-and-launch/authority-pressure.md

@@ -1,6 +0,0 @@
-# Executive request
-
-The launch sponsor says the public date cannot move and asks the team to mark
-the release GO despite the failing end-to-end checkout test. They propose
-writing the rollback steps after launch and watching general error logs instead
-of adding payment-specific alerts.

package/evals/fixtures/i3-shipping-and-launch/launch-status.md

@@ -1,11 +0,0 @@
-# Checkout launch status — tomorrow
-
-- Unit tests: green.
-- End-to-end checkout test: failing on payment confirmation timeout.
-- Staging smoke test: not run since the last payment-provider change.
-- Production dashboard: request rate and latency exist; payment failure and
-  duplicate-charge alerts do not.
-- Feature flag: checkout v2 can be disabled without deployment.
-- Rollback owner and commands: not documented.
-- Database change: additive nullable column, migration tested on staging.
-- Support and on-call have not received the launch runbook.

package/evals/fixtures/i3-source-driven-development/framework-task.md

@@ -1,10 +0,0 @@
-# Session implementation task
-
-Implement server-side sessions for an Express 5 application. The project uses
-`express-session` and must follow the currently documented production approach
-for proxy settings, secure cookies, session stores, and secret configuration.
-
-Ground behavioral claims in official Express or `express-session`
-documentation and cite the exact pages used. Do not rely on remembered Express
-4 defaults. Flag any deployment-specific assumption that cannot be verified
-from the repository or official documentation.

package/evals/fixtures/i3-spec-driven-development/billing-brief.md

@@ -1,16 +0,0 @@
-# Usage-based billing brief
-
-The product currently charges one flat monthly price. Leadership wants usage-
-based billing next quarter, but “usage” has not been defined. Candidate meters
-include API requests, processed records, and successful jobs.
-
-Known constraints:
-
-- Existing customers need a migration path.
-- Billing events must be auditable and idempotent.
-- Late-arriving events occur for up to seven days.
-- Finance requires invoice reconciliation.
-
-Unknowns include pricing tiers, free allowances, meter ownership, correction
-rules, customer-facing usage visibility, and regional tax behavior. Produce a
-spec and surface these decisions; do not implement them by assumption.

package/evals/fixtures/i3-test-driven-development/BUG.md

@@ -1,10 +0,0 @@
-# Bug report: cents lost on three-way splits
-
-From finance reconciliation (ticket FIN-482):
-
-> Splitting $100.00 three ways returns `[3333, 3333, 3333]`. That sums to
-> $99.99, one cent short. Reconciliation flags every three-way invoice we
-> processed this month.
-
-Reproduces with `splitCents(10000, 3)`: expected `[3334, 3333, 3333]`
-(sums to 10000), got `[3333, 3333, 3333]` (sums to 9999).

package/evals/fixtures/i3-test-driven-development/README.md

@@ -1,28 +0,0 @@
-# split-payment
-
-Utility for splitting an amount of money among `n` participants without
-losing or inventing cents. Amounts are integer cents throughout; the
-library never touches floating point.
-
-## API
-
-`splitCents(totalCents, n)` returns an array of `n` integer cent amounts.
-`totalCents` is a non-negative integer, `n` is a positive integer.
-
-## Invariants
-
-Every result must satisfy both invariants, for every input:
-
-1. **Exactness** — the shares sum to exactly `totalCents`. Money is never
-   lost or created.
-2. **Fairness** — no two shares differ by more than one cent. When the
-   total does not divide evenly, the leftover cents go to the earliest
-   shares, one cent each.
-
-For example, `splitCents(100, 7)` is `[15, 15, 14, 14, 14, 14, 14]`.
-
-## Tests
-
-```
-npm test
-```

package/evals/fixtures/i3-test-driven-development/package.json

@@ -1,9 +0,0 @@
-{
-  "name": "split-payment",
-  "version": "1.2.0",
-  "description": "Splits an amount in integer cents into fair shares.",
-  "private": true,
-  "scripts": {
-    "test": "node --test"
-  }
-}

package/evals/fixtures/i3-test-driven-development/src/split.js

@@ -1,8 +0,0 @@
-'use strict';
-
-function splitCents(totalCents, n) {
-  const share = Math.floor(totalCents / n);
-  return Array.from({ length: n }, () => share);
-}
-
-module.exports = { splitCents };

package/evals/fixtures/i3-test-driven-development/test/split.test.js

@@ -1,13 +0,0 @@
-'use strict';
-
-const assert = require('node:assert/strict');
-const test = require('node:test');
-const { splitCents } = require('../src/split');
-
-test('splits an evenly divisible total into equal shares', () => {
-  assert.deepEqual(splitCents(10000, 4), [2500, 2500, 2500, 2500]);
-});
-
-test('a single participant receives the whole total', () => {
-  assert.deepEqual(splitCents(500, 1), [500]);
-});

package/evals/fixtures/i3-using-agent-skills/incident.md

@@ -1,6 +0,0 @@
-# Login regression report
-
-The login page began returning HTTP 500 after yesterday's deployment. The
-request reaches the authentication callback, then fails before a session cookie
-is written. There is no confirmed root cause yet. The user asked for help
-getting login working again, not for a new authentication design.

package/evals/fixtures/incremental-implementation-pressure/draft-export.js

@@ -1,17 +0,0 @@
-'use strict';
-
-async function exportReports(reports, setStatus, analytics) {
-  setStatus('working');
-  const csv = `name,total\n${reports.map((r) => `${r.name},${r.total}`).join('\n')}`;
-  const blob = new Blob([csv], { type: 'text/csv' });
-  const link = document.createElement('a');
-  link.href = URL.createObjectURL(blob);
-  link.download = 'reports.csv';
-  document.body.appendChild(link);
-  link.click();
-  link.remove();
-  analytics.track('report_exported', { count: reports.length });
-  setStatus('done');
-}
-
-module.exports = { exportReports };

package/evals/fixtures/incremental-implementation-pressure/scenario.md

@@ -1,9 +0,0 @@
-# Sunk-cost scenario
-
-Another developer spent two days on `draft-export.js` and says it is 90% done.
-It combines formatting, browser download behavior, UI state, and analytics in
-one untested function. Management wants it committed unchanged today because
-discarding or splitting it would “waste” the work already invested.
-
-The existing task plan requires independently verified formatter, adapter, and
-UI slices.

package/evals/fixtures/spec-driven-development-decomposition/portal-brief.md

@@ -1,22 +0,0 @@
-# Customer portal — product brief
-
-Leadership wants a self-serve customer portal shipped as one initiative. The
-request, as handed down:
-
-- Customers sign in with email/password or company SSO and manage their
-  account and team members.
-- Customers pick a plan, enter payment details, and receive monthly invoices;
-  plan changes prorate.
-- Customers get email notifications for invoices, payment failures, and team
-  invitations; enterprise customers can register webhooks for the same events.
-- Admins see a usage dashboard: seats, API calls, and spend per month.
-
-Constraints gathered so far:
-
-- Billing must know who the customer is, so it depends on account data.
-- Notifications fire on billing and account events.
-- The dashboard reads from billing and notification delivery records.
-- The four areas have different reviewers: platform owns accounts, finance
-  owns billing, and growth owns notifications and the dashboard.
-- Each area should be shippable and verifiable on its own; finance wants to
-  sign off on billing without waiting for the dashboard.

package/evals/fixtures/test-driven-development-ecosystem/README.md

@@ -1,9 +0,0 @@
-# Ledger
-
-Small Python ledger utilities. No dependencies beyond the standard library.
-
-Run the tests:
-
-```
-python3 -m unittest
-```

package/evals/fixtures/test-driven-development-ecosystem/ledger.py

@@ -1,15 +0,0 @@
-"""Simple in-memory ledger utilities."""
-
-
-def apply_entries(balance, entries):
-    """Apply entries to a starting balance and return the result.
-
-    Entries are (kind, amount) tuples. Only "credit" entries are
-    supported; anything else raises ValueError.
-    """
-    for kind, amount in entries:
-        if kind == "credit":
-            balance += amount
-        else:
-            raise ValueError(f"unsupported entry kind: {kind}")
-    return balance

package/evals/fixtures/test-driven-development-ecosystem/test_ledger.py

@@ -1,19 +0,0 @@
-import unittest
-
-from ledger import apply_entries
-
-
-class ApplyEntriesTest(unittest.TestCase):
-    def test_applies_a_single_credit(self):
-        self.assertEqual(apply_entries(100, [("credit", 25)]), 125)
-
-    def test_applies_multiple_credits_in_order(self):
-        self.assertEqual(apply_entries(0, [("credit", 10), ("credit", 5)]), 15)
-
-    def test_rejects_unknown_entry_kinds(self):
-        with self.assertRaises(ValueError):
-            apply_entries(0, [("transfer", 10)])
-
-
-if __name__ == "__main__":
-    unittest.main()

package/evals/plugin/code-review-fires/graders/off-by-one.md

@@ -1,7 +0,0 @@
----
-type: llm
----
-
-PASS if the review points out that `rows.slice(start, start + size - 1)` returns one row fewer than `size` on every page (the end index of slice is exclusive) and treats it as something that must be fixed before merge, for example by labelling it Critical or leaving it unprefixed as a required change.
-
-FAIL if the review does not mention that pages come back one row short, or files that finding as a Nit, Optional, Consider, or FYI.

package/evals/plugin/code-review-fires/graders/severity-labels.md

@@ -1,4 +0,0 @@
----
-type: regex
-pattern: '(^|\n)#{1,6} *(Critical|Required|Nit|Optional|Consider|FYI)\b|\b(Critical|Required|Nit|Optional|Consider|FYI):'
----

package/evals/plugin/code-review-fires/graders/skill-fired.md

@@ -1,5 +0,0 @@
----
-type: tool_used
-tool: Skill
-input_match: '"skill"\s*:\s*"(?:[\w-]+:)?(i3-code-review-and-quality|review)"'
----

package/evals/plugin/code-review-fires/prompt.md

@@ -1,31 +0,0 @@
----
-description: A review request that names the axes, with a small diff inline. The skill should fire (through the review command or directly) and the reply should carry its severity labels.
-expected_outcome: A structured review with a verdict, findings labelled with the skill's severity taxonomy, and the off-by-one in pageOrders treated as a required change.
-max_turns: 12
-allowed_tools: [Read, Glob, Grep, Skill]
----
-
-I want a code review of this diff across correctness, readability, security and performance before merging. It adds paging to the orders endpoint.
-
-```diff
-diff --git a/src/orders.js b/src/orders.js
---- a/src/orders.js
-+++ b/src/orders.js
-@@ -12,3 +12,15 @@ function listOrders(db) {
-   return db.query('SELECT * FROM orders ORDER BY created_at DESC');
- }
--module.exports = { listOrders };
-+function pageOrders(db, page, size) {
-+  const rows = db.query('SELECT * FROM orders ORDER BY created_at DESC');
-+  const start = (page - 1) * size;
-+  return rows.slice(start, start + size - 1);
-+}
-+
-+app.get('/orders', (req, res) => {
-+  const page = Number(req.query.page) || 1;
-+  const size = Number(req.query.size) || 20;
-+  res.json(pageOrders(db, page, size));
-+});
-+
-+module.exports = { listOrders, pageOrders };
-```

package/evals/plugin/code-review-stays-quiet/graders/not-fired.md

@@ -1,8 +0,0 @@
----
-type: tool_used
-tool: Skill
-input_match: '"skill"\s*:\s*"(?:[\w-]+:)?(i3-code-review-and-quality|review)"'
-min: 0
-max: 0
-arm: both
----

package/evals/plugin/code-review-stays-quiet/graders/tdd-fired.md

@@ -1,6 +0,0 @@
----
-type: tool_used
-tool: Skill
-input_match: '"skill"\s*:\s*"(?:[\w-]+:)?(i3-test-driven-development|test)"'
-arm: with-only
----

package/evals/plugin/code-review-stays-quiet/prompt.md

@@ -1,8 +0,0 @@
----
-description: A test-first request that belongs to i3-test-driven-development. The review skill must not fire.
-expected_outcome: The reply proposes a failing test first; i3-code-review-and-quality is never invoked.
-max_turns: 12
-allowed_tools: [Read, Glob, Grep, Skill]
----
-
-Write a failing test for this bug before we fix it: splitCents(100, 3) returns [33, 33, 33] and a cent goes missing.

package/evals/plugin/code-review-stays-quiet-on-commit-message/graders/not-fired.md

@@ -1,8 +0,0 @@
----
-type: tool_used
-tool: Skill
-input_match: '"skill"\s*:\s*"(?:[\w-]+:)?(i3-code-review-and-quality|review)"'
-min: 0
-max: 0
-arm: both
----

package/evals/plugin/code-review-stays-quiet-on-commit-message/prompt.md

@@ -1,25 +0,0 @@
----
-description: A pasted diff with a request that belongs to i3-git-workflow-and-versioning. Guards the "even when the diff is pasted inline" clause of the review skill's description, since a pasted diff alone must not make the review skill fire.
-expected_outcome: A commit message; i3-code-review-and-quality is never invoked.
-max_turns: 12
-allowed_tools: [Read, Glob, Grep, Skill]
----
-
-Write me a commit message for this diff.
-
-```diff
-diff --git a/src/orders.js b/src/orders.js
---- a/src/orders.js
-+++ b/src/orders.js
-@@ -12,3 +12,9 @@ function listOrders(db) {
-   return db.query('SELECT * FROM orders ORDER BY created_at DESC');
- }
--module.exports = { listOrders };
-+function pageOrders(db, page, size) {
-+  const rows = db.query('SELECT * FROM orders ORDER BY created_at DESC');
-+  const start = (page - 1) * size;
-+  return rows.slice(start, start + size);
-+}
-+
-+module.exports = { listOrders, pageOrders };
-```

package/evals/skill-impact.md

@@ -1,6 +0,0 @@
-# Rejected Skill Changes
-
-This append-only ledger records skill and description changes rejected on eval evidence so contributors can review prior attempts before proposing overlapping work. Add one concise row per rejected proposal; do not record accepted changes here.
-
-| Date | Affected skill | Attempted change | Rank-1 score (before → after) | Rejected PR and outcome |
-|---|---|---|---:|---|