@appsforgood/next-supabase-kit 0.1.3 → 0.1.4

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 0.1.4
+
+- Added true multi-agent IDE activation for **Cursor** (`.cursor/agents/*.md`, `.cursor/skills/*/SKILL.md`, scoped rules) and **Codex** (`.codex/agents/*.toml` with model routing effort) via `agent-kit init --activate cursor|codex`.
+- Added shared roster adapter generation (`roster-adapters.ts`) and assistant adapter table parsing so audit and `adapter validate` warn when Active Cursor/Codex rows lack specialist files.
+- Fixed setup wizard IDE activation order so `present` is detected after files are generated and conflicts are returned in the API response.
+- Quoted YAML frontmatter in generated Cursor/Claude subagents and Cursor skills so descriptions with colons or quotes remain valid.
+- Stopped post-copy mutation of existing `.codex/config.toml`; conflict-safe copy behavior now protects customized Codex config.
+- Fixed `cursor-planner.mdc` scoped rule frontmatter and expanded adapter validation, IDE activation, and SSE stream tests.
+
 ## 0.1.3
 
 - Added Antigravity runtime adapter support with `agent-kit init --activate antigravity`, `antigravity/plugin.json`, native `/setup`, `/audit`, `/plan`, `/handoff`, `/frontend`, `/security`, `/copy`, `/ship`, and `/upgrade` command files, and portable `runtime-skills/*/SKILL.md` wrappers.

package/assistant-adapters/codex-agents.md

@@ -18,6 +18,19 @@ Use `AGENTS.md` as the primary project instruction surface.
 - `.agent-kit/council-sessions/`
 - `QUALITY_GATES.md`
 
+## Council Custom Agents
+
+After `agent-kit init --activate codex`, council specialists live in `.codex/agents/*.toml`.
+
+Spawn a dedicated custom agent instead of role-playing the whole council in one thread:
+
+- **Planning / scope:** `.codex/agents/planner.toml`
+- **Security / RLS / secrets:** `.codex/agents/security-reviewer.toml` (high reasoning effort)
+- **Frontend UI:** `.codex/agents/frontend-design-lead.toml`
+- **QA / tests:** `.codex/agents/qa-engineer.toml`
+
+Each file sets `model_reasoning_effort` from `.agent-kit/model-routing.json`. Verify model names in your Codex environment against `MODEL_ROUTING.md`.
+
 ## Operating Rule
 
 When a task is planning-oriented, ambiguous, risky, frontend-facing, security-sensitive, or release-related, start from the roster workflow instead of treating the request as a single generic implementation pass.
@@ -34,3 +47,5 @@ Record in `ASSISTANT_ADAPTERS.md`:
 - The command, session, or screenshot that proves the instructions loaded.
 - The model-selection setting or profile used for the active role.
 - Any known limitations or manual invocation steps.
+
+Run `agent-kit adapter validate codex` after activation.

package/assistant-adapters/cursor-agent-kit.mdc

@@ -20,6 +20,7 @@ Use `AGENTS.md`, `AGENT_ROSTER.md`, `.agent-kit/agent-roster.json`, `MODEL_ROUTI
 - Meaningful work should read project context and active corrections first.
 - Human corrections should be recorded before continuing and promoted to durable project or agent correction rules when they should affect future work.
 - Meaningful multi-agent work should use `agent-kit session checkpoint --file <json>` or individual `agent-kit session ...` commands and render Markdown evidence when available.
+- For council work, delegate to the matching project subagent in `.cursor/agents/` instead of role-playing every role in the main thread.
 
 ## Validation
 

package/assistant-adapters/cursor-frontend.mdc

@@ -0,0 +1,16 @@
+---
+description: Require Frontend Design Lead evidence for significant UI and component work.
+globs:
+  - "src/app/**"
+  - "src/components/**"
+  - "**/*.css"
+alwaysApply: false
+---
+
+# Frontend design gate reminders
+
+Significant UI changes require **Frontend Design Lead** review: brand/content intake, creative-direction rationale, reference-led critique, product-quality scorecard, accessibility, and visual QA evidence.
+
+Delegate to `@frontend-design-lead` in `.cursor/agents/frontend-design-lead.md` for isolated design review context.
+
+Reject generic AI-looking UI that is not specific to the product workflow and content model.

package/assistant-adapters/cursor-planner.mdc

@@ -0,0 +1,14 @@
+---
+description: Route ambiguous, planning, and cross-layer requests through the Planner workflow first.
+globs:
+  - "**/*"
+alwaysApply: false
+---
+
+# Planner routing
+
+When a request is ambiguous, planning-oriented, roadmap-related, or spans multiple layers, start with the **Planner** workflow before implementation.
+
+Delegate to the `@planner` subagent in `.cursor/agents/planner.md` when the task needs isolated planning context.
+
+Read project context, corrections, and `AGENT_ROSTER.md` before choosing a workflow.

package/assistant-adapters/cursor-security.mdc

@@ -0,0 +1,18 @@
+---
+description: Require Security Reviewer for auth, RLS, secrets, API mutations, and external calls.
+globs:
+  - "supabase/**"
+  - "**/auth/**"
+  - "**/api/**"
+  - "**/middleware.ts"
+  - "**/proxy.ts"
+alwaysApply: false
+---
+
+# Security gate reminders
+
+Auth, RLS, data mutation, dependency, secret, external-call, and release-risk changes require **Security Reviewer** review before acceptance.
+
+Delegate to `@security-reviewer` in `.cursor/agents/security-reviewer.md` or Task `security-review` for isolated review context.
+
+Verify OWASP Top 10, IDOR, SSRF, injection, broken auth, and least-privilege boundaries.

package/assistant-adapters/model-selection/codex-config.example.toml

@@ -1,6 +1,9 @@
 # Codex model-selection example for Agent Kit.
 # Copy the relevant comments into ~/.codex/config.toml or a trusted project .codex/config.toml.
 # Verify current model availability in your Codex environment before uncommenting.
+#
+# Custom council agents generated by agent-kit live under .codex/agents/*.toml.
+# Run `agent-kit init --activate codex` to create them from the project roster.
 
 # June 2026 Agent Kit suggested baseline:
 # model = "gpt-5.5"