Foundation operation: strip operator content, legacy UI, DO pipeline; port .opencode to CLAUDE.md

.opencode/skills/aztec-types-guide/SKILL.md → .claude/skills/aztec-types-guide/SKILL.md

@@ -2,7 +2,6 @@
 name: aztec-types-guide
 description: Reference for working with Aztec SDK types and the @chicmoz-pkg/types package in Chicmoz. Covers pinned package versions, key type patterns for blocks, transactions, contracts, and notes on viem compatibility.
 license: MIT
-compatibility: opencode
 metadata:
   audience: developers
   workflow: backend
@@ -22,26 +21,10 @@ metadata:
 
 All `@aztec/*` packages are pinned globally via Yarn resolutions in the root `package.json`. **Do not change individual service package.json versions without updating resolutions too.**
 
-### Current pins (as of last update)
-
-| Package                     | Version (main/production) | Version (production-devnet) |
-| --------------------------- | ------------------------- | --------------------------- |
-| `@aztec/aztec.js`           | `4.1.1`                   | `4.0.3`                     |
-| `@aztec/stdlib`             | `4.1.1`                   | `4.0.3`                     |
-| `@aztec/accounts`           | `4.1.1`                   | `4.0.3`                     |
-| `@aztec/bb.js`              | `4.1.1`                   | `4.0.3`                     |
-| `@aztec/bb-prover`          | `4.1.1`                   | `4.0.3`                     |
-| `@aztec/builder`            | `4.1.1`                   | `4.0.3`                     |
-| `@aztec/constants`          | `4.1.1`                   | `4.0.3`                     |
-| `@aztec/entrypoints`        | `4.1.1`                   | `4.0.3`                     |
-| `@aztec/ethereum`           | `4.1.1`                   | `4.0.3`                     |
-| `@aztec/foundation`         | `4.1.1`                   | `4.0.3`                     |
-| `@aztec/l1-artifacts`       | `4.1.1`                   | `4.0.3`                     |
-| `@aztec/noir-contracts.js`  | `4.1.1`                   | `4.0.3`                     |
-| `@aztec/protocol-contracts` | `4.1.1`                   | `4.0.3`                     |
-| `@aztec/pxe`                | `4.1.1`                   | `4.0.3`                     |
-| `@aztec/simulator`          | `4.1.1`                   | `4.0.3`                     |
-| `viem`                      | `2.20.0`                  | `2.20.0`                    |
+### Current pins
+
+Read them from the `resolutions` block in the root `package.json` (all
+`@aztec/*` packages share one version). Devnet is no longer served.
 
 ### Additional non-Aztec dependency
 
@@ -71,13 +54,13 @@ This package (`packages/types/`) is the **source of truth for all cross-service
 - L2 transaction types (pending, mined, dropped)
 - L1 contract types (registered classes, deployed instances)
 - Network configuration types
-- API response shapes (used by both `explorer-api` and `explorer-ui`)
+- API response shapes (used by both `explorer-api` and `explorer-ui-v2`)
 
 ### When to add types here
 
 Add to `@chicmoz-pkg/types` when:
 
-- The type is shared between two or more services (e.g., `explorer-api` produces it, `explorer-ui` consumes it)
+- The type is shared between two or more services (e.g., `explorer-api` produces it, `explorer-ui-v2` consumes it)
 - The type is used in a Kafka message (define it here, import it into `@chicmoz-pkg/message-registry`)
 - The type represents an Aztec domain concept (block, tx, contract) that you want decoupled from the SDK version
 
@@ -185,6 +168,4 @@ When bumping `@aztec/*` versions:
 3. Update `packages/types/` if the Aztec domain model changed (new fields, renamed fields)
 4. Update `services/event-cannon/Dockerfile.compile-contracts` to match: `FROM aztecprotocol/aztec:NEW_VERSION`
 5. Run `yarn build:packages && yarn build && yarn test` to catch type errors early
-6. The devnet branch may be on a different version — apply changes independently per branch
-
-See the `git-release` skill for the full Aztec version bump procedure.
+6. Production is pinned by commit from `AztecProtocol/foundation-iac`; bump `CHICMOZ_REF` there (and the compiler image versions) after merging

.opencode/skills/frontend-design/SKILL.md → .claude/skills/frontend-design/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: frontend-design
 description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
-compatibility: opencode
 license: Complete terms in LICENSE.txt
 metadata:
   audience: developers

.opencode/skills/kafka-message-design/SKILL.md → .claude/skills/kafka-message-design/SKILL.md

@@ -2,7 +2,6 @@
 name: kafka-message-design
 description: Step-by-step guide for designing and registering new Kafka topics and message types in Chicmoz. Covers message-registry structure, topic naming, schema definition, SASL auth context, and wiring producers and consumers.
 license: MIT
-compatibility: opencode
 metadata:
   audience: developers
   workflow: backend

.opencode/skills/react-best-practices/SKILL.md → .claude/skills/react-best-practices/SKILL.md

@@ -1,16 +1,15 @@
 ---
 name: react-best-practices
-description: React best practices for the Chicmoz explorer-ui (React + Vite + TanStack Router/Query + shadcn/ui). Use when writing, reviewing, or refactoring frontend code — components, hooks, data fetching, WebSocket handling, or performance optimisation.
+description: React best practices for the Chicmoz explorer-ui-v2 (React + Vite + TanStack Router/Query + shadcn/ui). Use when writing, reviewing, or refactoring frontend code — components, hooks, data fetching, WebSocket handling, or performance optimisation.
 license: MIT
-compatibility: opencode
 metadata:
   audience: developers
   workflow: frontend
 ---
 
-# React Best Practices — Chicmoz `explorer-ui`
+# React Best Practices — Chicmoz `explorer-ui-v2`
 
-Guidelines for writing and reviewing frontend code in `services/explorer-ui/`. This is a **pure client-side React SPA** (Vite + React 18) — there is no Next.js, no RSC, no SSR, no server actions. All guidance below is scoped to what actually runs in this project.
+Guidelines for writing and reviewing frontend code in `services/explorer-ui-v2/`. This is a **pure client-side React SPA** (Vite + React 18) — there is no Next.js, no RSC, no SSR, no server actions. All guidance below is scoped to what actually runs in this project.
 
 ## Stack at a Glance
 
@@ -353,7 +352,7 @@ Do not use `as any` or `: any`. If a Zod schema covers the data, use `z.infer<ty
 
 ### Domain types come from `@chicmoz-pkg/types`
 
-All L2 block, transaction, contract, and L1 types are defined in the shared workspace package. Do not redefine them locally in `explorer-ui`.
+All L2 block, transaction, contract, and L1 types are defined in the shared workspace package. Do not redefine them locally in `explorer-ui-v2`.
 
 ---