Add github_code/affaan-m__ECC from GitHub - direct commit (part 6)

github_code/affaan-m__ECC/docs/pt-BR/examples/rust-api-CLAUDE.md

@@ -0,0 +1,285 @@
+# Serviço de API Rust — CLAUDE.md de Projeto
+
+> Exemplo real para um serviço de API Rust com Axum, PostgreSQL e Docker.
+> Copie para a raiz do seu projeto e customize para seu serviço.
+
+## Visão Geral do Projeto
+
+**Stack:** Rust 1.78+, Axum (web framework), SQLx (banco assíncrono), PostgreSQL, Tokio (runtime assíncrono), Docker
+
+**Arquitetura:** Arquitetura em camadas com separação handler → service → repository. Axum para HTTP, SQLx para SQL verificado em tempo de compilação, middleware Tower para preocupações transversais.
+
+## Regras Críticas
+
+### Convenções Rust
+
+- Use `thiserror` para erros de library, `anyhow` apenas em crates binários ou testes
+- Sem `.unwrap()` ou `.expect()` em código de produção — propague erros com `?`
+- Prefira `&str` a `String` em parâmetros de função; retorne `String` quando houver transferência de ownership
+- Use `clippy` com `#![deny(clippy::all, clippy::pedantic)]` — corrija todos os warnings
+- Derive `Debug` em todos os tipos públicos; derive `Clone`, `PartialEq` só quando necessário
+- Sem blocos `unsafe` sem justificativa com comentário `// SAFETY:`
+
+### Banco de Dados
+
+- Todas as queries usam macros SQLx `query!` ou `query_as!` — verificadas em compile time contra o schema
+- Migrations em `migrations/` com `sqlx migrate` — nunca alterar banco diretamente
+- Use `sqlx::Pool<Postgres>` como estado compartilhado — nunca criar conexão por requisição
+- Todas as queries usam placeholders parametrizados (`$1`, `$2`) — nunca string formatting
+
+```rust
+// BAD: String interpolation (SQL injection risk)
+let q = format!("SELECT * FROM users WHERE id = '{}'", id);
+
+// GOOD: Parameterized query, compile-time checked
+let user = sqlx::query_as!(User, "SELECT * FROM users WHERE id = $1", id)
+    .fetch_optional(&pool)
+    .await?;
+```
+
+### Tratamento de Erro
+
+- Defina enum de erro de domínio por módulo com `thiserror`
+- Mapeie erros para respostas HTTP via `IntoResponse` — nunca exponha detalhes internos
+- Use `tracing` para logs estruturados — nunca `println!` ou `eprintln!`
+
+```rust
+use thiserror::Error;
+
+#[derive(Debug, Error)]
+pub enum AppError {
+    #[error("Resource not found")]
+    NotFound,
+    #[error("Validation failed: {0}")]
+    Validation(String),
+    #[error("Unauthorized")]
+    Unauthorized,
+    #[error(transparent)]
+    Internal(#[from] anyhow::Error),
+}
+
+impl IntoResponse for AppError {
+    fn into_response(self) -> Response {
+        let (status, message) = match &self {
+            Self::NotFound => (StatusCode::NOT_FOUND, self.to_string()),
+            Self::Validation(msg) => (StatusCode::BAD_REQUEST, msg.clone()),
+            Self::Unauthorized => (StatusCode::UNAUTHORIZED, self.to_string()),
+            Self::Internal(err) => {
+                tracing::error!(?err, "internal error");
+                (StatusCode::INTERNAL_SERVER_ERROR, "Internal error".into())
+            }
+        };
+        (status, Json(json!({ "error": message }))).into_response()
+    }
+}
+```
+
+### Testes
+
+- Testes unitários em módulos `#[cfg(test)]` dentro de cada arquivo fonte
+- Testes de integração no diretório `tests/` usando PostgreSQL real (Testcontainers ou Docker)
+- Use `#[sqlx::test]` para testes de banco com migration e rollback automáticos
+- Faça mock de serviços externos com `mockall` ou `wiremock`
+
+### Estilo de Código
+
+- Tamanho máximo de linha: 100 caracteres (enforced by rustfmt)
+- Agrupe imports: `std`, crates externas, `crate`/`super` — separados por linha em branco
+- Módulos: um arquivo por módulo, `mod.rs` só para re-exports
+- Tipos: PascalCase, funções/variáveis: snake_case, constantes: UPPER_SNAKE_CASE
+
+## Estrutura de Arquivos
+
+```
+src/
+  main.rs              # Entrypoint, server setup, graceful shutdown
+  lib.rs               # Re-exports for integration tests
+  config.rs            # Environment config with envy or figment
+  router.rs            # Axum router with all routes
+  middleware/
+    auth.rs            # JWT extraction and validation
+    logging.rs         # Request/response tracing
+  handlers/
+    mod.rs             # Route handlers (thin — delegate to services)
+    users.rs
+    orders.rs
+  services/
+    mod.rs             # Business logic
+    users.rs
+    orders.rs
+  repositories/
+    mod.rs             # Database access (SQLx queries)
+    users.rs
+    orders.rs
+  domain/
+    mod.rs             # Domain types, error enums
+    user.rs
+    order.rs
+migrations/
+  001_create_users.sql
+  002_create_orders.sql
+tests/
+  common/mod.rs        # Shared test helpers, test server setup
+  api_users.rs         # Integration tests for user endpoints
+  api_orders.rs        # Integration tests for order endpoints
+```
+
+## Padrões-Chave
+
+### Handler (Enxuto)
+
+```rust
+async fn create_user(
+    State(ctx): State<AppState>,
+    Json(payload): Json<CreateUserRequest>,
+) -> Result<(StatusCode, Json<UserResponse>), AppError> {
+    let user = ctx.user_service.create(payload).await?;
+    Ok((StatusCode::CREATED, Json(UserResponse::from(user))))
+}
+```
+
+### Service (Lógica de Negócio)
+
+```rust
+impl UserService {
+    pub async fn create(&self, req: CreateUserRequest) -> Result<User, AppError> {
+        if self.repo.find_by_email(&req.email).await?.is_some() {
+            return Err(AppError::Validation("Email already registered".into()));
+        }
+
+        let password_hash = hash_password(&req.password)?;
+        let user = self.repo.insert(&req.email, &req.name, &password_hash).await?;
+
+        Ok(user)
+    }
+}
+```
+
+### Repository (Acesso a Dados)
+
+```rust
+impl UserRepository {
+    pub async fn find_by_email(&self, email: &str) -> Result<Option<User>, sqlx::Error> {
+        sqlx::query_as!(User, "SELECT * FROM users WHERE email = $1", email)
+            .fetch_optional(&self.pool)
+            .await
+    }
+
+    pub async fn insert(
+        &self,
+        email: &str,
+        name: &str,
+        password_hash: &str,
+    ) -> Result<User, sqlx::Error> {
+        sqlx::query_as!(
+            User,
+            r#"INSERT INTO users (email, name, password_hash)
+               VALUES ($1, $2, $3) RETURNING *"#,
+            email, name, password_hash,
+        )
+        .fetch_one(&self.pool)
+        .await
+    }
+}
+```
+
+### Teste de Integração
+
+```rust
+#[tokio::test]
+async fn test_create_user() {
+    let app = spawn_test_app().await;
+
+    let response = app
+        .client
+        .post(&format!("{}/api/v1/users", app.address))
+        .json(&json!({
+            "email": "alice@example.com",
+            "name": "Alice",
+            "password": "securepassword123"
+        }))
+        .send()
+        .await
+        .expect("Failed to send request");
+
+    assert_eq!(response.status(), StatusCode::CREATED);
+    let body: serde_json::Value = response.json().await.unwrap();
+    assert_eq!(body["email"], "alice@example.com");
+}
+
+#[tokio::test]
+async fn test_create_user_duplicate_email() {
+    let app = spawn_test_app().await;
+    // Create first user
+    create_test_user(&app, "alice@example.com").await;
+    // Attempt duplicate
+    let response = create_user_request(&app, "alice@example.com").await;
+    assert_eq!(response.status(), StatusCode::BAD_REQUEST);
+}
+```
+
+## Variáveis de Ambiente
+
+```bash
+# Server
+HOST=0.0.0.0
+PORT=8080
+RUST_LOG=info,tower_http=debug
+
+# Database
+DATABASE_URL=postgres://user:pass@localhost:5432/myapp
+
+# Auth
+JWT_SECRET=your-secret-key-min-32-chars
+JWT_EXPIRY_HOURS=24
+
+# Optional
+CORS_ALLOWED_ORIGINS=http://localhost:3000
+```
+
+## Estratégia de Teste
+
+```bash
+# Run all tests
+cargo test
+
+# Run with output
+cargo test -- --nocapture
+
+# Run specific test module
+cargo test api_users
+
+# Check coverage (requires cargo-llvm-cov)
+cargo llvm-cov --html
+open target/llvm-cov/html/index.html
+
+# Lint
+cargo clippy -- -D warnings
+
+# Format check
+cargo fmt -- --check
+```
+
+## Workflow ECC
+
+```bash
+# Planning
+/plan "Add order fulfillment with Stripe payment"
+
+# Development with TDD
+/tdd                    # cargo test-based TDD workflow
+
+# Review
+/code-review            # Rust-specific code review
+/security-scan          # Dependency audit + unsafe scan
+
+# Verification
+/verify                 # Build, clippy, test, security scan
+```
+
+## Fluxo Git
+
+- `feat:` novas features, `fix:` correções de bug, `refactor:` mudanças de código
+- Branches de feature a partir da `main`, PRs obrigatórios
+- CI: `cargo fmt --check`, `cargo clippy`, `cargo test`, `cargo audit`
+- Deploy: Docker multi-stage build com base `scratch` ou `distroless`

github_code/affaan-m__ECC/docs/pt-BR/examples/saas-nextjs-CLAUDE.md

@@ -0,0 +1,166 @@
+# Aplicação SaaS — CLAUDE.md de Projeto
+
+> Exemplo real para uma aplicação SaaS com Next.js + Supabase + Stripe.
+> Copie para a raiz do seu projeto e customize para sua stack.
+
+## Visão Geral do Projeto
+
+**Stack:** Next.js 15 (App Router), TypeScript, Supabase (auth + DB), Stripe (billing), Tailwind CSS, Playwright (E2E)
+
+**Arquitetura:** Server Components por padrão. Client Components apenas para interatividade. API routes para webhooks e server actions para mutações.
+
+## Regras Críticas
+
+### Banco de Dados
+
+- Todas as queries usam cliente Supabase com RLS habilitado — nunca bypass de RLS
+- Migrations em `supabase/migrations/` — nunca modificar banco diretamente
+- Use `select()` com lista explícita de colunas, não `select('*')`
+- Todas as queries user-facing devem incluir `.limit()` para evitar resultados sem limite
+
+### Autenticação
+
+- Use `createServerClient()` de `@supabase/ssr` em Server Components
+- Use `createBrowserClient()` de `@supabase/ssr` em Client Components
+- Rotas protegidas checam `getUser()` — nunca confiar só em `getSession()` para auth
+- Middleware em `middleware.ts` renova tokens de auth em toda requisição
+
+### Billing
+
+- Handler de webhook Stripe em `app/api/webhooks/stripe/route.ts`
+- Nunca confiar em preço do cliente — sempre buscar do Stripe server-side
+- Status da assinatura checado via coluna `subscription_status`, sincronizada por webhook
+- Usuários free tier: 3 projetos, 100 chamadas de API/dia
+
+### Estilo de Código
+
+- Sem emojis em código ou comentários
+- Apenas padrões imutáveis — spread operator, nunca mutar
+- Server Components: sem diretiva `'use client'`, sem `useState`/`useEffect`
+- Client Components: `'use client'` no topo, mínimo possível — extraia lógica para hooks
+- Prefira schemas Zod para toda validação de entrada (API routes, formulários, env vars)
+
+## Estrutura de Arquivos
+
+```
+src/
+  app/
+    (auth)/          # Auth pages (login, signup, forgot-password)
+    (dashboard)/     # Protected dashboard pages
+    api/
+      webhooks/      # Stripe, Supabase webhooks
+    layout.tsx       # Root layout with providers
+  components/
+    ui/              # Shadcn/ui components
+    forms/           # Form components with validation
+    dashboard/       # Dashboard-specific components
+  hooks/             # Custom React hooks
+  lib/
+    supabase/        # Supabase client factories
+    stripe/          # Stripe client and helpers
+    utils.ts         # General utilities
+  types/             # Shared TypeScript types
+supabase/
+  migrations/        # Database migrations
+  seed.sql           # Development seed data
+```
+
+## Padrões-Chave
+
+### Formato de Resposta de API
+
+```typescript
+type ApiResponse<T> =
+  | { success: true; data: T }
+  | { success: false; error: string; code?: string }
+```
+
+### Padrão de Server Action
+
+```typescript
+'use server'
+
+import { z } from 'zod'
+import { createServerClient } from '@/lib/supabase/server'
+
+const schema = z.object({
+  name: z.string().min(1).max(100),
+})
+
+export async function createProject(formData: FormData) {
+  const parsed = schema.safeParse({ name: formData.get('name') })
+  if (!parsed.success) {
+    return { success: false, error: parsed.error.flatten() }
+  }
+
+  const supabase = await createServerClient()
+  const { data: { user } } = await supabase.auth.getUser()
+  if (!user) return { success: false, error: 'Unauthorized' }
+
+  const { data, error } = await supabase
+    .from('projects')
+    .insert({ name: parsed.data.name, user_id: user.id })
+    .select('id, name, created_at')
+    .single()
+
+  if (error) return { success: false, error: 'Failed to create project' }
+  return { success: true, data }
+}
+```
+
+## Variáveis de Ambiente
+
+```bash
+# Supabase
+NEXT_PUBLIC_SUPABASE_URL=
+NEXT_PUBLIC_SUPABASE_ANON_KEY=
+SUPABASE_SERVICE_ROLE_KEY=     # Server-only, never expose to client
+
+# Stripe
+STRIPE_SECRET_KEY=
+STRIPE_WEBHOOK_SECRET=
+NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=
+
+# App
+NEXT_PUBLIC_APP_URL=http://localhost:3000
+```
+
+## Estratégia de Teste
+
+```bash
+/tdd                    # Unit + integration tests for new features
+/e2e                    # Playwright tests for auth flow, billing, dashboard
+/test-coverage          # Verify 80%+ coverage
+```
+
+### Fluxos E2E Críticos
+
+1. Sign up → verificação de e-mail → criação do primeiro projeto
+2. Login → dashboard → operações CRUD
+3. Upgrade de plano → Stripe checkout → assinatura ativa
+4. Webhook: assinatura cancelada → downgrade para free tier
+
+## Workflow ECC
+
+```bash
+# Planning a feature
+/plan "Add team invitations with email notifications"
+
+# Developing with TDD
+/tdd
+
+# Before committing
+/code-review
+/security-scan
+
+# Before release
+/e2e
+/test-coverage
+```
+
+## Fluxo Git
+
+- `feat:` novas features, `fix:` correções de bug, `refactor:` mudanças de código
+- Branches de feature a partir da `main`, PRs obrigatórios
+- CI roda: lint, type-check, unit tests, E2E tests
+- Deploy: preview da Vercel em PR, produção no merge para `main`

github_code/affaan-m__ECC/docs/pt-BR/examples/user-CLAUDE.md

@@ -0,0 +1,109 @@
+# Exemplo de CLAUDE.md no Nível de Usuário
+
+Este é um exemplo de arquivo CLAUDE.md no nível de usuário. Coloque em `~/.claude/CLAUDE.md`.
+
+Configurações de nível de usuário se aplicam globalmente em todos os projetos. Use para:
+- Preferências pessoais de código
+- Regras universais que você sempre quer aplicar
+- Links para suas regras modulares
+
+---
+
+## Filosofia Central
+
+Você é Claude Code. Eu uso agentes e skills especializados para tarefas complexas.
+
+**Princípios-Chave:**
+1. **Agent-First**: Delegue trabalho complexo para agentes especializados
+2. **Execução Paralela**: Use ferramenta Task com múltiplos agentes quando possível
+3. **Planejar Antes de Executar**: Use Plan Mode para operações complexas
+4. **Test-Driven**: Escreva testes antes da implementação
+5. **Security-First**: Nunca comprometa segurança
+
+---
+
+## Regras Modulares
+
+Diretrizes detalhadas em `~/.claude/rules/`:
+
+| Rule File | Contents |
+|-----------|----------|
+| security.md | Security checks, secret management |
+| coding-style.md | Immutability, file organization, error handling |
+| testing.md | TDD workflow, 80% coverage requirement |
+| git-workflow.md | Commit format, PR workflow |
+| agents.md | Agent orchestration, when to use which agent |
+| patterns.md | API response, repository patterns |
+| performance.md | Model selection, context management |
+| hooks.md | Hooks System |
+
+---
+
+## Agentes Disponíveis
+
+Localizados em `~/.claude/agents/`:
+
+| Agent | Purpose |
+|-------|---------|
+| planner | Feature implementation planning |
+| architect | System design and architecture |
+| tdd-guide | Test-driven development |
+| code-reviewer | Code review for quality/security |
+| security-reviewer | Security vulnerability analysis |
+| build-error-resolver | Build error resolution |
+| e2e-runner | Playwright E2E testing |
+| refactor-cleaner | Dead code cleanup |
+| doc-updater | Documentation updates |
+
+---
+
+## Preferências Pessoais
+
+### Privacidade
+- Sempre anonimizar logs; nunca colar segredos (API keys/tokens/passwords/JWTs)
+- Revise a saída antes de compartilhar - remova qualquer dado sensível
+
+### Estilo de Código
+- Sem emojis em código, comentários ou documentação
+- Prefira imutabilidade - nunca mutar objetos ou arrays
+- Muitos arquivos pequenos em vez de poucos arquivos grandes
+- 200-400 linhas típico, 800 máximo por arquivo
+
+### Git
+- Conventional commits: `feat:`, `fix:`, `refactor:`, `docs:`, `test:`
+- Sempre testar localmente antes de commitar
+- Commits pequenos e focados
+
+### Testes
+- TDD: escreva testes primeiro
+- Cobertura mínima de 80%
+- Unit + integration + E2E para fluxos críticos
+
+### Captura de Conhecimento
+- Notas pessoais de debug, preferências e contexto temporário → auto memory
+- Conhecimento de time/projeto (decisões de arquitetura, mudanças de API, runbooks de implementação) → seguir estrutura de docs já existente no projeto
+- Se a tarefa atual já produzir docs/comentários/exemplos relevantes, não duplique o mesmo conhecimento em outro lugar
+- Se não houver local óbvio de docs no projeto, pergunte antes de criar um novo doc de topo
+
+---
+
+## Integração com Editor
+
+Eu uso Zed como editor principal:
+- Agent Panel para rastreamento de arquivos
+- CMD+Shift+R para command palette
+- Vim mode habilitado
+
+---
+
+## Métricas de Sucesso
+
+Você tem sucesso quando:
+- Todos os testes passam (80%+ de cobertura)
+- Não há vulnerabilidades de segurança
+- O código é legível e manutenível
+- Os requisitos do usuário são atendidos
+
+---
+
+**Filosofia**: Design agent-first, execução paralela, planejar antes de agir, testar antes de codar, segurança sempre.

github_code/affaan-m__ECC/docs/pt-BR/rules/agents.md

@@ -0,0 +1,50 @@
+# Orquestração de Agentes
+
+## Agentes Disponíveis
+
+Localizados em `~/.claude/agents/`:
+
+| Agente | Propósito | Quando Usar |
+|--------|-----------|-------------|
+| planner | Planejamento de implementação | Recursos complexos, refatoração |
+| architect | Design de sistema | Decisões arquiteturais |
+| tdd-guide | Desenvolvimento orientado a testes | Novos recursos, correção de bugs |
+| code-reviewer | Revisão de código | Após escrever código |
+| security-reviewer | Análise de segurança | Antes de commits |
+| build-error-resolver | Corrigir erros de build | Quando o build falha |
+| e2e-runner | Testes E2E | Fluxos críticos do usuário |
+| refactor-cleaner | Limpeza de código morto | Manutenção de código |
+| doc-updater | Documentação | Atualização de docs |
+| rust-reviewer | Revisão de código Rust | Projetos Rust |
+
+## Uso Imediato de Agentes
+
+Sem necessidade de prompt do usuário:
+1. Solicitações de recursos complexos - Use o agente **planner**
+2. Código acabado de escrever/modificar - Use o agente **code-reviewer**
+3. Correção de bug ou novo recurso - Use o agente **tdd-guide**
+4. Decisão arquitetural - Use o agente **architect**
+
+## Execução Paralela de Tarefas
+
+SEMPRE use execução paralela de Task para operações independentes:
+
+```markdown
+# BOM: Execução paralela
+Iniciar 3 agentes em paralelo:
+1. Agente 1: Análise de segurança do módulo de autenticação
+2. Agente 2: Revisão de desempenho do sistema de cache
+3. Agente 3: Verificação de tipos dos utilitários
+
+# RUIM: Sequencial quando desnecessário
+Primeiro agente 1, depois agente 2, depois agente 3
+```
+
+## Análise Multi-Perspectiva
+
+Para problemas complexos, use subagentes com papéis divididos:
+- Revisor factual
+- Engenheiro sênior
+- Especialista em segurança
+- Revisor de consistência
+- Verificador de redundância

github_code/affaan-m__ECC/docs/pt-BR/rules/coding-style.md

@@ -0,0 +1,48 @@
+# Estilo de Código
+
+## Imutabilidade (CRÍTICO)
+
+SEMPRE crie novos objetos, NUNCA modifique os existentes:
+
+```
+// Pseudocódigo
+ERRADO:  modificar(original, campo, valor) → altera o original in-place
+CORRETO: atualizar(original, campo, valor) → retorna nova cópia com a alteração
+```
+
+Justificativa: Dados imutáveis previnem efeitos colaterais ocultos, facilita a depuração e permite concorrência segura.
+
+## Organização de Arquivos
+
+MUITOS ARQUIVOS PEQUENOS > POUCOS ARQUIVOS GRANDES:
+- Alta coesão, baixo acoplamento
+- 200-400 linhas típico, 800 máximo
+- Extrair utilitários de módulos grandes
+- Organizar por recurso/domínio, não por tipo
+
+## Tratamento de Erros
+
+SEMPRE trate erros de forma abrangente:
+- Trate erros explicitamente em cada nível
+- Forneça mensagens de erro amigáveis no código voltado para UI
+- Registre contexto detalhado de erro no lado do servidor
+- Nunca engula erros silenciosamente
+
+## Validação de Entrada
+
+SEMPRE valide nas fronteiras do sistema:
+- Valide toda entrada do usuário antes de processar
+- Use validação baseada em schema onde disponível
+- Falhe rapidamente com mensagens de erro claras
+- Nunca confie em dados externos (respostas de API, entrada do usuário, conteúdo de arquivo)
+
+## Checklist de Qualidade de Código
+
+Antes de marcar o trabalho como concluído:
+- [ ] O código é legível e bem nomeado
+- [ ] Funções são pequenas (< 50 linhas)
+- [ ] Arquivos são focados (< 800 linhas)
+- [ ] Sem aninhamento profundo (> 4 níveis)
+- [ ] Tratamento adequado de erros
+- [ ] Sem valores hardcoded (use constantes ou config)
+- [ ] Sem mutação (padrões imutáveis usados)

github_code/affaan-m__ECC/docs/pt-BR/rules/git-workflow.md

@@ -0,0 +1,24 @@
+# Fluxo de Trabalho Git
+
+## Formato de Mensagem de Commit
+```
+<tipo>: <descrição>
+
+<corpo opcional>
+```
+
+Tipos: feat, fix, refactor, docs, test, chore, perf, ci
+
+Nota: As instalações gerenciadas pelo ECC definem `"includeCoAuthoredBy": false` em `~/.claude/settings.json`, portanto os commits não incluem `Co-Authored-By` por padrão. Para manter a atribuição do Claude, defina `"includeCoAuthoredBy": true` ou configure `attribution`; o ECC nunca sobrescreve uma escolha explícita.
+
+## Fluxo de Trabalho de Pull Request
+
+Ao criar PRs:
+1. Analisar o histórico completo de commits (não apenas o último commit)
+2. Usar `git diff [branch-base]...HEAD` para ver todas as alterações
+3. Rascunhar resumo abrangente do PR
+4. Incluir plano de teste com TODOs
+5. Fazer push com a flag `-u` se for uma nova branch
+
+> Para o processo de desenvolvimento completo (planejamento, TDD, revisão de código) antes de operações git,
+> veja [development-workflow.md](./development-workflow.md).

github_code/affaan-m__ECC/docs/pt-BR/rules/hooks.md

@@ -0,0 +1,30 @@
+# Sistema de Hooks
+
+## Tipos de Hook
+
+- **PreToolUse**: Antes da execução da ferramenta (validação, modificação de parâmetros)
+- **PostToolUse**: Após a execução da ferramenta (auto-formatação, verificações)
+- **Stop**: Quando a sessão termina (verificação final)
+
+## Permissões de Auto-Aceite
+
+Use com cautela:
+- Habilite para planos confiáveis e bem definidos
+- Desabilite para trabalho exploratório
+- Nunca use a flag dangerously-skip-permissions
+- Configure `allowedTools` em `~/.claude.json` em vez disso
+
+## Melhores Práticas para TodoWrite
+
+Use a ferramenta TodoWrite para:
+- Rastrear progresso em tarefas com múltiplos passos
+- Verificar compreensão das instruções
+- Habilitar direcionamento em tempo real
+- Mostrar etapas de implementação granulares
+
+A lista de tarefas revela:
+- Etapas fora de ordem
+- Itens faltando
+- Itens extras desnecessários
+- Granularidade incorreta
+- Requisitos mal interpretados

github_code/affaan-m__ECC/docs/pt-BR/rules/patterns.md

@@ -0,0 +1,31 @@
+# Padrões Comuns
+
+## Projetos Skeleton
+
+Ao implementar novas funcionalidades:
+1. Buscar projetos skeleton bem testados
+2. Usar agentes paralelos para avaliar opções:
+   - Avaliação de segurança
+   - Análise de extensibilidade
+   - Pontuação de relevância
+   - Planejamento de implementação
+3. Clonar a melhor opção como fundação
+4. Iterar dentro da estrutura comprovada
+
+## Padrões de Design
+
+### Padrão Repository
+
+Encapsular acesso a dados atrás de uma interface consistente:
+- Definir operações padrão: findAll, findById, create, update, delete
+- Implementações concretas lidam com detalhes de armazenamento (banco de dados, API, arquivo, etc.)
+- A lógica de negócios depende da interface abstrata, não do mecanismo de armazenamento
+- Habilita troca fácil de fontes de dados e simplifica testes com mocks
+
+### Formato de Resposta da API
+
+Use um envelope consistente para todas as respostas de API:
+- Incluir indicador de sucesso/status
+- Incluir o payload de dados (nullable em caso de erro)
+- Incluir campo de mensagem de erro (nullable em caso de sucesso)
+- Incluir metadados para respostas paginadas (total, página, limite)

github_code/affaan-m__ECC/docs/pt-BR/rules/performance.md

@@ -0,0 +1,55 @@
+# Otimização de Desempenho
+
+## Estratégia de Seleção de Modelo
+
+**Haiku 4.5** (90% da capacidade do Sonnet, 3x economia de custo):
+- Agentes leves com invocação frequente
+- Programação em par e geração de código
+- Agentes worker em sistemas multi-agente
+
+**Sonnet 5** (Melhor modelo para codificação):
+- Trabalho principal de desenvolvimento
+- Orquestrando fluxos de trabalho multi-agente
+- Tarefas de codificação complexas
+
+**Opus 5** (Raciocínio mais profundo):
+- Decisões arquiteturais complexas
+- Requisitos máximos de raciocínio
+- Pesquisa e análise
+
+## Gerenciamento da Janela de Contexto
+
+Evite os últimos 20% da janela de contexto para:
+- Refatoração em grande escala
+- Implementação de recursos abrangendo múltiplos arquivos
+- Depuração de interações complexas
+
+Tarefas com menor sensibilidade ao contexto:
+- Edições de arquivo único
+- Criação de utilitários independentes
+- Atualizações de documentação
+- Correções de bugs simples
+
+## Pensamento Estendido + Modo de Plano
+
+O pensamento estendido está habilitado por padrão, reservando até 31.999 tokens para raciocínio interno.
+
+Controle o pensamento estendido via:
+- **Toggle**: Option+T (macOS) / Alt+T (Windows/Linux)
+- **Config**: Defina `alwaysThinkingEnabled` em `~/.claude/settings.json`
+- **Limite de orçamento**: `export MAX_THINKING_TOKENS=10000` (bash) ou `$env:MAX_THINKING_TOKENS = "10000"` (PowerShell)
+- **Modo verbose**: Ctrl+O para ver a saída de pensamento
+
+Para tarefas complexas que requerem raciocínio profundo:
+1. Garantir que o pensamento estendido esteja habilitado (habilitado por padrão)
+2. Habilitar **Modo de Plano** para abordagem estruturada
+3. Usar múltiplas rodadas de crítica para análise minuciosa
+4. Usar subagentes com papéis divididos para perspectivas diversas
+
+## Resolução de Problemas de Build
+
+Se o build falhar:
+1. Use o agente **build-error-resolver**
+2. Analise mensagens de erro
+3. Corrija incrementalmente
+4. Verifique após cada correção

github_code/affaan-m__ECC/docs/pt-BR/rules/security.md

@@ -0,0 +1,29 @@
+# Diretrizes de Segurança
+
+## Verificações de Segurança Obrigatórias
+
+Antes de QUALQUER commit:
+- [ ] Sem segredos hardcoded (chaves de API, senhas, tokens)
+- [ ] Todas as entradas do usuário validadas
+- [ ] Prevenção de injeção SQL (queries parametrizadas)
+- [ ] Prevenção de XSS (HTML sanitizado)
+- [ ] Proteção CSRF habilitada
+- [ ] Autenticação/autorização verificada
+- [ ] Rate limiting em todos os endpoints
+- [ ] Mensagens de erro não vazam dados sensíveis
+
+## Gerenciamento de Segredos
+
+- NUNCA hardcode segredos no código-fonte
+- SEMPRE use variáveis de ambiente ou um gerenciador de segredos
+- Valide que os segredos necessários estão presentes na inicialização
+- Rotacione quaisquer segredos que possam ter sido expostos
+
+## Protocolo de Resposta a Segurança
+
+Se um problema de segurança for encontrado:
+1. PARE imediatamente
+2. Use o agente **security-reviewer**
+3. Corrija problemas CRÍTICOS antes de continuar
+4. Rotacione quaisquer segredos expostos
+5. Revise toda a base de código por problemas similares

github_code/affaan-m__ECC/docs/pt-BR/rules/testing.md

@@ -0,0 +1,29 @@
+# Requisitos de Teste
+
+## Cobertura Mínima de Teste: 80%
+
+Tipos de Teste (TODOS obrigatórios):
+1. **Testes Unitários** - Funções individuais, utilitários, componentes
+2. **Testes de Integração** - Endpoints de API, operações de banco de dados
+3. **Testes E2E** - Fluxos críticos do usuário (framework escolhido por linguagem)
+
+## Desenvolvimento Orientado a Testes (TDD)
+
+Fluxo de trabalho OBRIGATÓRIO:
+1. Escreva o teste primeiro (VERMELHO)
+2. Execute o teste - deve FALHAR
+3. Escreva a implementação mínima (VERDE)
+4. Execute o teste - deve PASSAR
+5. Refatore (MELHORE)
+6. Verifique cobertura (80%+)
+
+## Resolução de Falhas de Teste
+
+1. Use o agente **tdd-guide**
+2. Verifique o isolamento de teste
+3. Verifique se os mocks estão corretos
+4. Corrija a implementação, não os testes (a menos que os testes estejam errados)
+
+## Suporte de Agentes
+
+- **tdd-guide** - Use PROATIVAMENTE para novos recursos, aplica escrever-testes-primeiro

github_code/affaan-m__ECC/docs/releases/1.10.0/discussion-announcement.md

@@ -0,0 +1,55 @@
+# ECC v1.10.0 is live
+
+ECC just crossed **140K stars**, and the public release surface had drifted too far from the actual repo.
+
+So v1.10.0 is a hard sync release:
+
+- **38 agents**
+- **156 skills**
+- **72 commands**
+- plugin/install metadata corrected
+- top-line docs and release surfaces brought back in line
+
+This release also folds in the operator/media lane that has been growing around the core harness system:
+
+- `brand-voice`
+- `social-graph-ranker`
+- `connections-optimizer`
+- `customer-billing-ops`
+- `google-workspace-ops`
+- `project-flow-ops`
+- `workspace-surface-audit`
+- `manim-video`
+- `remotion-video-creation`
+
+And on the 2.0 side:
+
+ECC 2.0 is now **real as an alpha control-plane surface** in-tree under `ecc2/`.
+
+It builds today and exposes:
+
+- `dashboard`
+- `start`
+- `sessions`
+- `status`
+- `stop`
+- `resume`
+- `daemon`
+
+That does **not** mean the full ECC 2.0 roadmap is done.
+
+It means the control-plane alpha is here, usable, and moving out of the “just a vision” category.
+
+The shortest honest framing right now:
+
+- ECC 1.x is the battle-tested harness/workflow layer shipping broadly today
+- ECC 2.0 is the alpha control-plane growing on top of it
+
+If you have been waiting for:
+
+- cleaner install surfaces
+- stronger cross-harness parity
+- operator workflows instead of just coding primitives
+- a real control-plane direction instead of scattered notes
+
+this is the release that makes the repo feel coherent again.

github_code/affaan-m__ECC/docs/releases/1.10.0/release-notes.md

@@ -0,0 +1,70 @@
+# ECC v1.10.0 Release Notes
+
+## Positioning
+
+ECC v1.10.0 is a surface-sync and operator-lane release.
+
+The goal was to make the public repo, plugin metadata, install paths, and ecosystem story reflect the actual live state of the project again, while continuing to ship the operator workflows and media tooling that grew around the core harness layer.
+
+## What Changed
+
+- Synced the live OSS surface to **38 agents, 156 skills, and 72 commands**.
+- Updated the Claude plugin, Codex plugin, OpenCode package metadata, and release-facing docs to **1.10.0**.
+- Refreshed top-line repo metrics to match the live public repo (**140K+ stars**, **21K+ forks**, **170+ contributors**).
+- Expanded the operator/workflow lane with:
+  - `brand-voice`
+  - `social-graph-ranker`
+  - `connections-optimizer`
+  - `customer-billing-ops`
+  - `google-workspace-ops`
+  - `project-flow-ops`
+  - `workspace-surface-audit`
+- Expanded the media lane with:
+  - `manim-video`
+  - `remotion-video-creation`
+- Added and stabilized more framework/domain coverage, including `nestjs-patterns`.
+
+## ECC 2.0 Status
+
+ECC 2.0 is **real and usable as an alpha**, but it is **not general-availability complete**.
+
+What exists today:
+
+- `ecc2/` Rust control-plane codebase in the main repo
+- `cargo build --manifest-path ecc2/Cargo.toml` passes
+- `ecc-tui` commands currently available:
+  - `dashboard`
+  - `start`
+  - `sessions`
+  - `status`
+  - `stop`
+  - `resume`
+  - `daemon`
+
+What this means:
+
+- You can experiment with the control-plane surface now.
+- You should not describe the full ECC 2.0 roadmap as finished.
+- The right framing today is **ECC 2.0 alpha / control-plane preview**, not GA.
+
+## Install Guidance
+
+Current install surfaces:
+
+- Claude Code plugin
+- `ecc-universal` on npm
+- Codex plugin manifest
+- OpenCode package/plugin surface
+- AgentShield CLI + npm + GitHub Marketplace action
+
+Important nuance:
+
+- The Claude plugin remains constrained by platform-level `rules` distribution limits.
+- The selective install / OSS path is still the most reliable full install for teams that want the complete ECC surface.
+
+## Recommended Upgrade Path
+
+1. Refresh to the latest plugin/install metadata.
+2. Prefer the selective install / OSS path when you need full rules coverage.
+3. Use AgentShield for guardrails and repo scanning.
+4. Treat ECC 2.0 as an alpha control-plane surface until the open P0/P1 roadmap is materially burned down.

github_code/affaan-m__ECC/docs/releases/1.10.0/x-thread.md

@@ -0,0 +1,45 @@
+# X Thread Draft — ECC v1.10.0
+
+ECC crossed 140K stars and the public surface had drifted too far from the actual repo.
+
+so v1.10.0 is the sync release.
+
+38 agents
+156 skills
+72 commands
+
+plugin metadata fixed
+install surfaces corrected
+docs and release story brought back in line with the live repo
+
+also shipped the operator / media lane that grew out of real usage:
+
+- brand-voice
+- social-graph-ranker
+- connections-optimizer
+- customer-billing-ops
+- google-workspace-ops
+- project-flow-ops
+- workspace-surface-audit
+- manim-video
+- remotion-video-creation
+
+and most importantly:
+
+ECC 2.0 is no longer just roadmap talk.
+
+the `ecc2/` control-plane alpha is in-tree, builds today, and already exposes:
+
+- dashboard
+- start
+- sessions
+- status
+- stop
+- resume
+- daemon
+
+not calling it GA yet.
+
+calling it what it is:
+
+an actual alpha control plane sitting on top of the harness/workflow layer we’ve been building in public.

github_code/affaan-m__ECC/docs/releases/1.8.0/linkedin-post.md

@@ -0,0 +1,13 @@
+# LinkedIn Draft - ECC v1.8.0
+
+ECC v1.8.0 is now focused on harness performance at the system level.
+
+This release improves:
+- hook reliability and lifecycle behavior
+- eval-driven engineering workflows
+- operator tooling for autonomous loops
+- cross-platform support for Claude Code, Cursor, OpenCode, and Codex
+
+We also shipped NanoClaw v2 with stronger session operations for real workflow usage.
+
+If your AI coding workflow feels inconsistent, start by treating the harness as a first-class engineering system.

github_code/affaan-m__ECC/docs/releases/1.8.0/reference-attribution.md

@@ -0,0 +1,16 @@
+# Reference Attribution and Licensing Notes
+
+ECC v1.8.0 references research and workflow inspiration from:
+
+- `plankton`
+- `ralphinho`
+- `infinite-agentic-loop`
+- `continuous-claude`
+- public profiles: [zarazhangrui](https://github.com/zarazhangrui), [humanplane](https://github.com/humanplane)
+
+## Policy
+
+1. No direct code copying from unlicensed or incompatible sources.
+2. ECC implementations are re-authored for this repository’s architecture and licensing model.
+3. Referenced material is used for ideas, patterns, and conceptual framing only unless licensing explicitly permits reuse.
+4. Any future direct reuse requires explicit license verification and source attribution in-file and in release notes.

github_code/affaan-m__ECC/docs/releases/1.8.0/release-notes.md

@@ -0,0 +1,20 @@
+# ECC v1.8.0 Release Notes
+
+## Positioning
+
+ECC v1.8.0 positions the project as an agent harness performance system, not just a config bundle.
+
+## Key Improvements
+
+- Stabilized hooks and lifecycle behavior.
+- Expanded eval and loop operations surface.
+- Upgraded NanoClaw for operational use.
+- Improved cross-harness parity (Claude Code, Cursor, OpenCode, Codex).
+
+## Upgrade Focus
+
+1. Validate hook profile defaults in your environment.
+2. Run `/harness-audit` to baseline your project.
+3. Use `/quality-gate` and updated eval workflows to enforce consistency.
+4. Review attribution and licensing notes for referenced ecosystems: [reference-attribution.md](./reference-attribution.md).
+5. For partner/sponsor optics, use live distribution metrics and talking points: [../business/metrics-and-sponsorship.md](../../business/metrics-and-sponsorship.md).

github_code/affaan-m__ECC/docs/releases/1.8.0/x-quote-eval-skills.md

@@ -0,0 +1,5 @@
+# X Quote Draft - Eval Skills Post
+
+Strong eval skills are now built deeper into ECC.
+
+v1.8.0 expands eval-harness patterns, pass@k guidance, and release-level verification loops so teams can measure reliability, not guess it.

github_code/affaan-m__ECC/docs/releases/1.8.0/x-quote-plankton-deslop.md

@@ -0,0 +1,5 @@
+# X Quote Draft - Plankton / De-slop Workflow
+
+The quality gate model matters.
+
+In v1.8.0 we pushed harder on write-time quality enforcement, deterministic checks, and cleaner loop recovery so agents converge faster with less noise.

github_code/affaan-m__ECC/docs/releases/1.8.0/x-thread.md

@@ -0,0 +1,11 @@
+# X Thread Draft - ECC v1.8.0
+
+1/ ECC v1.8.0 is live. This release is about one thing: better agent harness performance.
+
+2/ We shipped hook reliability fixes, loop operations commands, and stronger eval workflows.
+
+3/ NanoClaw v2 now supports model routing, skill hot-load, branching, search, compaction, export, and metrics.
+
+4/ If your agents are underperforming, start with `/harness-audit` and tighten quality gates.
+
+5/ Cross-harness parity remains a priority: Claude Code, Cursor, OpenCode, Codex.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/article-outline.md

@@ -0,0 +1,78 @@
+# Article Outline - ECC v2.0.0-rc.1
+
+## Working Title
+
+Turning ECC Into a Cross-Harness Operating System
+
+## Core Argument
+
+Most agentic work breaks down because the tools stay isolated.
+
+The leverage comes from treating the harness, reusable workflow layer, and operator shell as one system:
+
+- skills for repeatable work
+- hooks and tests for enforcement
+- MCPs for tool access
+- memory and handoffs for continuity
+- one operator shell that can route daily execution
+
+## Structure
+
+### 1. The Problem
+
+- too many chat windows
+- too many tool-specific workflows
+- too much context living in personal habit instead of reusable system shape
+
+### 2. What ECC Already Solved
+
+- reusable skill format
+- cross-harness install surfaces
+- hooks and verification discipline
+- security and review patterns
+- operator workflow skills around content, research, and business ops
+- queue, discussion, Linear, legacy, and release-evidence checks that make the
+  operating state inspectable
+- supply-chain IOC scanning and no-lifecycle install hardening after the
+  Mini Shai-Hulud/TanStack campaign
+
+### 3. Why Hermes Is the Operator Layer
+
+- chat, CLI, TUI, cron, and handoffs can sit above the reusable ECC layer
+- business and content work can run next to engineering work
+- the daily loop becomes easier to inspect and improve
+
+### 4. What Ships in rc.1
+
+- sanitized Hermes setup guide
+- release and distribution collateral
+- cross-harness architecture doc
+- Hermes import guidance
+- clearer 2.0 positioning in the repo
+- preview-pack smoke gate
+- launch drafts for GitHub release copy, X, LinkedIn, article, Telegram/Hermes
+  handoff, and demo prompts
+
+### 5. What Changed Since v1.10.0
+
+- Claude Code remains the core target, but ECC now treats Codex, OpenCode,
+  Cursor, Gemini, Zed, and terminal-only workflows as shared execution surfaces.
+- The release process now has repeatable platform, discussion, observability,
+  supply-chain, Linear progress, and preview-pack checks.
+- AgentShield and ECC Tools work is mirrored into the roadmap so enterprise
+  security, hosted review, policy promotion, and billing-readiness lanes do not
+  drift away from the main release.
+
+### 6. What Stays Local
+
+- secrets and auth
+- raw workspace exports
+- personal datasets
+- operator-specific automations that have not been sanitized
+- deeper CRM, finance, and Google Workspace playbooks
+
+### 7. Closing Point
+
+The goal is not to copy one exact stack.
+
+The goal is to build an operating system around the agent that turns repeated work into reusable, measurable surfaces.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/demo-prompts.md

@@ -0,0 +1,42 @@
+# Hermes x ECC Demo Prompts
+
+## Prompt 1: ECC Builds ECC
+
+Use the current ECC repo and the public release pack at `docs/releases/2.0.0-rc.1/`.
+
+Do 4 things in order:
+
+1. Inspect git status and the current repo diff, then give me a concise ECC v2.0.0-rc.1 PR or release summary that proves ECC is being used to build ECC itself.
+2. Finalize one strong X thread.
+3. Finalize one strong LinkedIn post.
+4. Tell me the exact 3 recordings I should do next plus what Hermes can generate automatically after I record.
+
+Keep it decisive and practical.
+
+## Prompt 2: Turn Recording Into Assets
+
+Assume I just recorded:
+
+- one face-camera hook
+- one screen capture of Hermes using ECC to ship ECC v2.0.0-rc.1
+- one setup walkthrough of the Hermes x ECC workspace
+
+Give me:
+
+1. a short-form edit plan for X, LinkedIn, TikTok, and YouTube Shorts
+2. a voiceover script if I want to re-record clean audio
+3. the exact repo-relative filenames and folders I should use for raw footage
+4. the assets Hermes can generate automatically after I drop the files in place
+
+Keep it operational.
+
+## Prompt 3: Public Launch Push
+
+Using the ECC v2.0.0-rc.1 release pack, give me:
+
+1. one release tweet
+2. one follow-up tweet
+3. one LinkedIn comment I can paste under the post
+4. one short Telegram handoff I can send to Hermes later to keep distributing this launch across channels
+
+Make it sound like an operator shipping real work, not a launch thread cliche.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/ito-prediction-market-skill-pack.md

@@ -0,0 +1,78 @@
+# Itô Prediction-Market Skill Pack
+
+This rc.1 note records a public teaser skill pack that connects ECC's skill
+distribution loop with Itô prediction-market workflows while keeping the two
+businesses separate.
+
+ECC remains the open agent-harness substrate and ECC Tools remains the hosted
+GitHub App / Pro surface. Itô remains a separate prediction-market basket
+business. The link is distribution: ECC can ship reusable skills that make
+agents better at researching, comparing, explaining, and planning around
+prediction-market baskets. Live Itô API access stays gated.
+
+## Included Skills
+
+| Skill | Use |
+| --- | --- |
+| `ito-market-intelligence` | Source-grounded event, underlier, venue, liquidity, and news context |
+| `ito-basket-compare` | Compare baskets against a knowledge base, portfolio notes, financial context, or thesis |
+| `ito-trade-planner` | Build a manual, non-advisory worksheet for market and venue review |
+| `ito-data-atlas-agent` | Design background research/drafting agents with human edit points |
+| `prediction-market-oracle-research` | Treat prediction markets as data/oracle inputs for agents and decision intelligence |
+| `prediction-market-risk-review` | Review advice, venue, security, privacy, and execution boundaries |
+
+## Access Model
+
+The public skills work without Itô credentials for research and planning. Any
+Itô-backed call requires explicit gated access:
+
+```bash
+export ITO_API_KEY=...
+```
+
+Do not include live keys, account data, positions, private strategy, or venue
+credentials in public docs, prompts, commits, slide decks, or support tickets.
+
+Suggested public CTA:
+
+> The Itô skill pack works as public research/planning workflows today. DM or
+> request access for the Itô API key if you want live basket data.
+
+## Non-Advisory Boundary
+
+These skills do not provide investment, legal, tax, or trading advice. They do
+not place trades. They can help a user:
+
+- inspect markets and underliers;
+- compare a basket against their own notes or constraints;
+- understand resolution and venue mechanics;
+- use prediction-market signals as one input to a broader research process;
+- draft a manual worksheet the user can review themselves.
+
+## Growth Loop
+
+For the general product-integration contract, see
+[`docs/architecture/platform-value-loop.md`](../../architecture/platform-value-loop.md).
+
+The loop is intentionally simple:
+
+1. ECC users discover useful public prediction-market skills.
+2. Builders run the skills with public sources and see the Itô-shaped workflow.
+3. Serious users request gated API access for live Itô basket data.
+4. Itô usage creates more operator patterns.
+5. Sanitized patterns can become new ECC skills.
+
+This sends agent/tooling traffic toward Itô without making ECC Tools look like
+an Itô product or mixing subscription ownership between businesses.
+
+## Useful Chain
+
+For a full workflow, chain:
+
+`deep-research` -> `x-api` or `exa-search` -> `ito-market-intelligence` ->
+`ito-basket-compare` -> `prediction-market-risk-review` ->
+`ito-trade-planner`
+
+For corporate or industry use cases, replace trade planning with
+`prediction-market-oracle-research` and route the output into a dashboard,
+decision memo, or agent memory record.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/launch-checklist.md

@@ -0,0 +1,68 @@
+# ECC v2.0.0-rc.1 Launch Checklist
+
+## Repo
+
+- verify local `main` is synced to `origin/main`
+- verify `docs/ECC-2.0-GA-ROADMAP.md` reflects the current Linear milestone
+  plan and the latest `ECC Platform Roadmap` project snapshot under the Ito
+  Markets workspace
+- verify `docs/HERMES-SETUP.md` is present
+- verify `docs/architecture/cross-harness.md` is present
+- verify this release directory is committed
+- verify `preview-pack-manifest.md` lists the public release, Hermes, adapter,
+  observability, publication, and announcement artifacts before running final
+  publish checks
+- verify `release-name-plugin-publication-checklist-2026-05-18.md` still
+  matches current GitHub, npm, Claude, Codex, OpenCode, and billing surfaces
+- keep private tokens, personal docs, and raw workspace exports out of the repo
+
+## Release Surface
+
+- verify package, plugin, marketplace, OpenCode, and agent metadata stays at `2.0.0-rc.1`
+- verify `ecc2/Cargo.toml` stays at `0.1.0` for rc.1; `ecc2/` remains an alpha control-plane scaffold
+- complete `publication-readiness.md` with fresh evidence before any GitHub release, npm publish, plugin submission, or announcement post
+- run `npm run release:approval-gate -- --format json` after owner approvals
+  and live URL readbacks are recorded; it must return ready true before any
+  publish, upload, social, or outbound action
+- rerun the release name/plugin publication checklist before creating a
+  GitHub prerelease, publishing npm, pushing Claude plugin tags, recording the
+  Codex marketplace path, or posting public copy
+- include `publication-evidence-2026-05-17.md` and
+  `operator-readiness-dashboard-2026-05-17.md` in the final evidence review,
+  then rerun publish-facing checks from the exact release commit
+- update release metadata in one dedicated release-version PR
+- run the root test suite
+- run `cd ecc2 && cargo test`
+
+## Content
+
+- publish the X thread from `x-thread.md`
+- publish the LinkedIn draft from `linkedin-post.md`
+- use `article-outline.md` for the longer writeup
+- route sponsor, partner, consulting, conference, podcast, and GitHub
+  Discussion copy through `partner-sponsor-talks-pack.md`
+- record one 30-60 second proof-of-work clip
+- validate the release video suite with `npm run release:video-suite -- --format json`
+  after setting `ECC_VIDEO_SOURCE_ROOT` and `ECC_VIDEO_RELEASE_SUITE_ROOT`
+- keep `video-suite-production.md` aligned with the actual primary launch
+  render, timeline, captions, and self-eval gate
+
+## Demo Asset Suggestions
+
+- Hermes plus ECC side by side
+- release docs being generated or reviewed from the repo
+- a workflow moving from brief to post to checklist
+- `ecc2/` dashboard or session surface with alpha framing
+
+## Messaging
+
+Use language like:
+
+- "release candidate"
+- "sanitized operator stack"
+- "cross-harness operating system for agentic work"
+- "ECC is the reusable substrate; Hermes is the operator shell"
+- "private/local integrations land after sanitization"
+
+Do not send sponsor, partner, consulting, conference, or podcast outreach
+without explicit human approval.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/linkedin-post.md

@@ -0,0 +1,52 @@
+# LinkedIn Draft - ECC v2.0.0-rc.1
+
+ECC v2.0.0-rc.1 is ready for final release review as the first release-candidate pass at the 2.0 direction.
+
+The practical shift is simple: ECC is no longer framed as only a Claude Code plugin or config bundle.
+
+It is becoming a meta-harness for agentic work: the portable layer above the
+individual AI coding clients.
+
+- reusable skills instead of one-off prompts
+- hooks and tests instead of manual discipline
+- MCP-backed access to docs, code, browser automation, and research
+- Codex, OpenCode, Cursor, Gemini, Zed, and Claude Code surfaces that share the same core workflow layer
+- Hermes as the operator shell for chat, cron, handoffs, and daily work routing
+
+For this release-candidate surface, I kept the repo honest.
+
+I did not publish private workspace state. I shipped the reusable layer:
+
+- sanitized Hermes setup documentation
+- release notes and launch collateral
+- cross-harness architecture notes
+- Hermes import guidance for turning local operator patterns into public ECC skills
+- release-readiness gates for PRs, issues, discussions, Linear progress, legacy tails, observability, and supply-chain checks
+- a deterministic preview-pack smoke test so the public pack can be verified before a release action
+- a gated Itô prediction-market skill pack for research, comparison, planning,
+  and risk review, with Itô API access kept separate from ECC Tools and
+  approval-based
+
+The leverage is not just better prompting.
+
+It is reducing the number of isolated surfaces, turning repeated workflows into
+reusable skills, and making the operating system around the agent measurable.
+
+That is the reason I like the phrase meta-harness. The goal is not to replace
+the harness. The goal is to make the workflow layer above the harness portable,
+auditable, and useful across teams.
+
+The supply-chain work became part of the release story too. After the Mini
+Shai-Hulud/TanStack campaign, rc.1 now includes IOC scanning, no-lifecycle CI
+installs, advisory-source refresh, npm audit/signature checks, and AI-tool
+persistence coverage.
+
+There is still more to harden before GA, especially around packaging, installers, and the `ecc2/` control plane. But rc.1 is enough to show the shape clearly.
+
+The GitHub prerelease and npm `next` package are live now. Public publication
+still stays approval-gated for the plugin path, video URLs, final outbound URLs,
+and any billing/native-payments claim that has not been freshly rechecked.
+
+The release URL ledger now separates links that already resolve from links that
+must wait for the remaining approval-gated plugin, video, billing, and outbound
+checks.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/naming-and-publication-matrix.md

@@ -0,0 +1,158 @@
+# ECC v2.0.0-rc.1 Naming And Publication Matrix
+
+Snapshot date: 2026-05-19. Publication state refreshed 2026-05-26 after the
+GitHub prerelease and npm `next` readbacks succeeded.
+
+This matrix records the rc.1 identity after the public repository rename to
+`affaan-m/ECC`. It is evidence for planning, not a publication action.
+
+## Decision
+
+For `v2.0.0-rc.1`, ship the public identity as **ECC**.
+
+Use `affaan-m/ECC` as the canonical GitHub repo and `ECC` as the product name
+in copy, plugin slugs, status surfaces, diagrams, and release collateral. Keep
+the npm package and package entry points as `ecc-universal` until a separate
+post-rc migration plan exists.
+
+Reason:
+
+- the current install surface already works as `ecc-universal` plus the `ecc`
+  plugin slug;
+- the exact npm package name `ecc` is already occupied by an unrelated elliptic
+  curve cryptography package;
+- `affaan-m/ECC` is the live public GitHub repo;
+- Claude and Codex plugin surfaces are already short enough as `ecc`;
+- rc.1 should prove the release, plugin, and publication pipeline before any
+  npm/package rename.
+
+## Current Values
+
+| Surface | Current value | Evidence command | Current result | Release decision |
+| --- | --- | --- | --- | --- |
+| Product display name | `ECC` | `rg -n "^# ECC\|displayName.*ECC\|affaan-m/ECC" README.md .codex-plugin/plugin.json docs/releases/2.0.0-rc.1` | Present across README, plugin manifests, release copy, and URL ledger | Keep for rc.1 and GA |
+| GitHub repo | `affaan-m/ECC` | `git remote get-url origin` | `https://github.com/affaan-m/ECC.git` | Keep for rc.1 and GA |
+| npm package | `ecc-universal` | `node -p "require('./package.json').name"` | `ecc-universal` | Keep for rc.1 |
+| npm package version | `2.0.0-rc.1` local, `1.10.0` registry latest, `2.0.0-rc.1` registry next | `node -p "require('./package.json').version"` and `npm view ecc-universal name version dist-tags --json` | Local rc.1 is ready; registry latest remains `1.10.0`; `next` points to `2.0.0-rc.1` | Keep rc on `next`, not `latest` |
+| Exact npm short name | `ecc` | `npm view ecc name version description repository.url --json` | Occupied by `ecc@0.0.2`, "Elliptic curve cryptography functions." | Do not use |
+| Scoped npm short name | `@affaan-m/ecc` | `npm view @affaan-m/ecc name version --json` | Registry 404 | Possible future scoped package if npm scope policy permits |
+| Former package name | `everything-claude-code` | `npm view everything-claude-code name version dist-tags --json` | Registry reports unpublished on 2026-02-07 | Do not revive for rc.1 |
+| Claude plugin slug | `ecc` | `node -p "require('./.claude-plugin/plugin.json').name"` | `ecc` | Keep |
+| Claude plugin version | `2.0.0-rc.1` | `claude plugin validate .claude-plugin/plugin.json`; `claude plugin tag .claude-plugin --dry-run` | Validation passed on Claude Code `2.1.143`; dry run would create `ecc--v2.0.0-rc.1` | Ready for release-tag gate |
+| Claude marketplace entry | `ecc` | `.claude-plugin/marketplace.json`; `claude plugin marketplace add --help`; Anthropic plugin marketplace docs | Version and repo point at current rc.1 surface; GitHub, git URL, remote marketplace JSON, and local path marketplace sources are supported | Keep |
+| Codex plugin slug | `ecc` | `node -p "require('./.codex-plugin/plugin.json').name"` | `ecc` | Keep |
+| Codex plugin version | `2.0.0-rc.1` | `node tests/plugin-manifest.test.js`; `node tests/docs/ecc2-release-surface.test.js` | Plugin manifest passed 54/54; release surface passed 21/21 on Codex CLI `0.131.0` | Ready for Codex marketplace/manual marketplace gate |
+| Codex repo marketplace | `ecc` | `.agents/plugins/marketplace.json`; `codex plugin marketplace add --help`; OpenAI Codex plugin docs | Repo marketplace add supports GitHub shorthand, Git URLs, SSH URLs, local roots, `--ref`, and `--sparse`; local and GitHub-ref temp-home add smokes passed | Use as rc.1 Codex distribution path |
+| OpenCode package | `ecc-universal` | `node -p "require('./.opencode/package.json').name"` | `ecc-universal` | Keep |
+| OpenCode build | Generated package output | `npm run build:opencode` | Passed | Ready for package dry-run gate |
+| npm pack surface | Reduced runtime package | `NPM_CONFIG_USERCONFIG=/dev/null npm pack --dry-run --json` | Produced `ecc-universal-2.0.0-rc.1.tgz`, 2228 entries, 4,348,504 bytes packed, 13,024,929 bytes unpacked | Needs final release-commit rerun |
+
+## Publication Paths
+
+| Path | Current evidence | Required next action | Blocker |
+| --- | --- | --- | --- |
+| GitHub release | `v2.0.0-rc.1` prerelease is live at <https://github.com/affaan-m/ECC/releases/tag/v2.0.0-rc.1> | Keep release notes aligned with the URL ledger; rerun evidence before any follow-up release edit | Remaining plugin, video, billing, and outbound URLs still gated |
+| npm | `ecc-universal@2.0.0-rc.1` is live on `next`; registry latest remains `1.10.0` | Keep rc on `next`; do not move `latest` before GA approval | Remaining plugin, video, billing, and outbound URLs still gated |
+| Claude plugin | `claude plugin validate .claude-plugin/plugin.json` passed; `claude plugin tag --help` confirms the release tag flow creates `{name}--v{version}` tags and can push them | Run `claude plugin tag .claude-plugin --dry-run` from the clean release commit, then tag/push only after release approval | No plugin release tag created in this pass |
+| Claude marketplace | `.claude-plugin/marketplace.json` points at `ecc` and the public repo | Verify marketplace update/install path after tag exists | External marketplace propagation not verified |
+| Codex plugin | `codex plugin marketplace` supports local and Git marketplace sources; `.codex-plugin/plugin.json` is present; `.agents/plugins/marketplace.json` exposes `ecc` from the repo root; temp-home local and GitHub-ref marketplace adds passed | Publish rc.1 docs with the repo-marketplace command, then monitor OpenAI's official Plugin Directory path | Do not claim official Plugin Directory listing before OpenAI submission evidence |
+| OpenCode package | `.opencode/package.json` builds from source and ships inside npm package | Re-run `npm run build:opencode` and package dry-run from release commit | OpenCode CLI 1.2.21 does not expose a separate plugin publication command in this pass |
+| ECC Tools billing claim | README and launch copy mention ECC Tools / marketplace context | ECC-Tools #89/#90/#91 add selected-target billing readback, selected-target announcement gating, and ignored `--env-file` support; #92 adds the non-breaking operator bearer path; #93 records the live selected-target gate pass | Billing evidence ready; repeat the live selected-target gate before any payment announcement |
+| Social and longform copy | X thread, LinkedIn copy, article outline, GitHub release copy exist | Replace stale URLs and publish only after the remaining plugin/video/billing/outbound gates are approved | GitHub prerelease and npm URLs are live; plugin, video, billing, and outbound URLs are not final |
+
+## ITO-46 Blocker Register
+
+| Channel | Current status | Required metadata/evidence | Owner | Blocker or follow-up |
+| --- | --- | --- | --- | --- |
+| GitHub release | Live prerelease at <https://github.com/affaan-m/ECC/releases/tag/v2.0.0-rc.1> | Tag, release URL, prerelease flag, final release notes, URL ledger | Release owner | Keep release edits behind final evidence and owner approval |
+| npm | `ecc-universal@2.0.0-rc.1` is published on `next`; registry latest is `1.10.0` | Pack summary, publish readback, `next` dist-tag readback, registry signature evidence | Package owner | Do not move rc.1 to `latest` before GA approval |
+| Short npm name | `ecc` is occupied; `@affaan-m/ecc` returns 404 | Name availability outputs and migration plan | Release owner | Keep `ecc-universal` for rc.1; scoped rename is post-rc only |
+| Claude plugin | `ecc@2.0.0-rc.1` validates; tag dry run would create `ecc--v2.0.0-rc.1` | `claude plugin validate .`, `claude plugin tag .claude-plugin --dry-run`, marketplace install/update smoke | Plugin owner | Real tag push and marketplace propagation require release approval |
+| Claude marketplace | Docs and CLI support GitHub, git URL, remote marketplace JSON, and local path sources | Public repo marketplace JSON, support/contact metadata, post-tag install smoke | Plugin owner | No external official listing has been submitted in this pass |
+| Codex repo marketplace | Local and GitHub-ref temp-home marketplace add smokes passed on Codex CLI `0.131.0` | `.codex-plugin/plugin.json`, `.agents/plugins/marketplace.json`, repo/personal marketplace evidence | Plugin owner | Official Plugin Directory listing requires OpenAI submission/listing evidence |
+| Codex official Plugin Directory | OpenAI docs describe the curated official directory; ECC has not submitted or received listing evidence | Directory submission link or OpenAI approval path once available | Plugin owner | Track as an ITO-56/ITO-46 follow-up; do not claim an official listing |
+| OpenCode package | `npm run build:opencode` passed | Built `.opencode` package metadata inside npm tarball | Package owner | No separate public plugin channel identified; follows npm |
+| Billing/native payments | Marketplace Pro target readback, selected-target announcement preflight, env-file operator path, non-breaking operator bearer, and live selected-target gate have passed | 2026-05-20 selected-target readback, webhook provenance, selected-target announcement gate, ECC-Tools #91 `--env-file` support, ECC-Tools #92 operator bearer, ECC-Tools #93 live gate evidence | ECC Tools owner | Repeat the live gate immediately before rc.1 announcement; final copy still waits on release/plugin/live URL approvals |
+| Social/longform copy | Drafts exist; GitHub and npm links are live | Final live GitHub, npm, Claude, Codex, video, and billing URLs | Release owner | Publish only after remaining plugin/video/billing/outbound approvals exist |
+
+## Package Rename After rc.1
+
+If the package layer moves from `ecc-universal` toward a shorter npm surface
+after rc.1, do it as a staged migration:
+
+1. Keep `ecc-universal` as the npm package until a replacement package has a
+   verified owner, deprecation plan, and install migration.
+2. Keep `affaan-m/ECC` as the canonical repo for public docs, release notes,
+   plugin marketplace entries, npm metadata, and external links.
+3. Reserve or create any new npm/package surfaces before announcing the
+   package rename.
+4. Ship a compatibility guide that maps old commands, package names, plugin
+   slugs, and docs URLs to the new names.
+
+## Evidence Captured In This Pass
+
+```text
+git rev-parse HEAD
+67e63e63f9bfd074bd6a21bf6bac71f3dfefa58b
+
+node -p "require('./package.json').name + '@' + require('./package.json').version"
+ecc-universal@2.0.0-rc.1
+
+node -p "require('./.claude-plugin/plugin.json').name + '@' + require('./.claude-plugin/plugin.json').version"
+ecc@2.0.0-rc.1
+
+node -p "require('./.codex-plugin/plugin.json').name + '@' + require('./.codex-plugin/plugin.json').version"
+ecc@2.0.0-rc.1
+
+node -p "require('./.opencode/package.json').name + '@' + require('./.opencode/package.json').version"
+ecc-universal@2.0.0-rc.1
+
+npm view ecc name version description repository.url --json
+ecc@0.0.2 is occupied by an unrelated elliptic curve cryptography package.
+
+npm view ecc-universal name version dist-tags --json
+registry latest is 1.10.0; next is 2.0.0-rc.1.
+
+npm view ecc-universal@2.0.0-rc.1 name version dist.tarball dist.integrity time --json
+registry returned version 2.0.0-rc.1, the rc tarball URL, and published time
+2026-05-26T00:36:22.940Z.
+
+claude plugin validate .claude-plugin/plugin.json
+Validation passed on Claude Code 2.1.143.
+
+claude plugin validate .
+Validation passed with one warning: root CLAUDE.md is not loaded as plugin
+context; ship plugin context through skills instead.
+
+claude plugin tag .claude-plugin --dry-run
+Would create and push tag ecc--v2.0.0-rc.1.
+
+node tests/docs/ecc2-release-surface.test.js
+21 release-surface checks passed.
+
+node tests/plugin-manifest.test.js
+54 plugin-manifest checks passed.
+
+npm run build:opencode
+Passed.
+
+npm pack --dry-run --json
+Produced ecc-universal-2.0.0-rc.1.tgz, 2228 entries, 4,348,504 bytes
+packed, and 13,024,929 bytes unpacked.
+
+npm publish --tag next --dry-run
+Dry run would publish ecc-universal@2.0.0-rc.1 to npm with tag next.
+
+codex plugin marketplace add --help
+Supports GitHub shorthand, HTTP(S) Git URLs, SSH URLs, local marketplace roots,
+--ref, and Git-only --sparse.
+
+HOME="$(mktemp -d)" codex plugin marketplace add <local-checkout>
+Added marketplace ecc and recorded the installed marketplace root as
+<local-checkout> without touching the real Codex config.
+
+HOME="$(mktemp -d)" codex plugin marketplace add affaan-m/ECC --ref "$(git rev-parse HEAD)"
+Added marketplace ecc from the GitHub repo pinned to
+67e63e63f9bfd074bd6a21bf6bac71f3dfefa58b without touching the real Codex
+config.
+```

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-15.md

@@ -0,0 +1,55 @@
+# ECC Operator Readiness Dashboard
+
+This dashboard is generated by `npm run operator:dashboard`. It is an operator snapshot, not release approval.
+
+Generated: 2026-05-17T05:08:31.916Z
+Commit: 6d130cfcd5d06b42c7eb30be8e109cfa87fde197
+Status: work remaining
+
+## Current Status
+
+| Area | Status | Evidence |
+| --- | --- | --- |
+| PR queue | Current | 6 open PRs across tracked repos |
+| Issue queue | Current | 3 open issues across tracked repos |
+| Discussions | Current | 0 need maintainer touch; 0 missing accepted answer |
+| Local worktree | Needs work | 7 blocking dirty files; 1 ignored dirty entries |
+| Dashboard generation | Current | platform audit ready: true; GitHub skipped: false |
+| Publication | Not complete | release, npm, plugin, billing, and announcement gates are tracked below |
+
+## Prompt-To-Artifact Checklist
+
+| Objective requirement | Artifact or gate | Status | Evidence | Gap |
+| --- | --- | --- | --- | --- |
+| Keep public PRs below 20 | scripts/platform-audit.js live GitHub sweep | current | 6 open PRs across 5 tracked repos | repeat before release |
+| Keep public issues below 20 | scripts/platform-audit.js live GitHub sweep | current | 3 open issues across 5 tracked repos | repeat before release |
+| Respond and manage repository discussions | scripts/platform-audit.js discussion summary | current | 0 need maintainer touch; 0 answerable discussions missing accepted answer | repeat before release |
+| Build ITO-44 completion dashboard into a repeatable command | npm run operator:dashboard | complete | operator:dashboard package script exists | keep generated dashboard attached to publication evidence |
+| ECC 2.0 preview pack ready | docs/releases/2.0.0-rc.1/preview-pack-manifest.md | in_progress | preview pack manifest is in-tree | final clean-checkout release approval and publish evidence still pending |
+| Include Hermes specialized skills safely | docs/HERMES-SETUP.md and skills/hermes-imports/SKILL.md | in_progress | Hermes setup and import skill are present | final preview-pack smoke and release review pending |
+| Prepare name-change, Claude plugin, and Codex plugin paths | naming-and-publication-matrix plus publication-readiness | in_progress | naming matrix and plugin readiness gates exist | real tag/push, marketplace submission, and final channel choice remain approval-gated |
+| Prepare release notes, articles, tweets, and push notifications | docs/releases/2.0.0-rc.1 social and release-copy files | in_progress | release notes, X thread, and LinkedIn draft are present | URL-backed refresh and publish approval still pending |
+| Advance AgentShield enterprise iteration | AgentShield PR evidence plus enterprise roadmap | in_progress | AgentShield enterprise PR evidence is mirrored in the GA roadmap | workflow automation around protected rollout and richer runtime review UX pending after policy promotion shipped |
+| Advance ECC Tools native payments and AI-native harness-agnostic app | ECC Tools PR evidence, billing gate, hosted analysis lanes | in_progress | billing announcement gate, hosted analysis lanes, AgentShield fleet-summary consumption, hosted finding evidence paths, and harness-route policy linking are mirrored in the GA roadmap | live Marketplace test-account readback, hosted promotion telemetry, and richer operator review UX pending |
+| Audit, prune, or attach legacy work | docs/stale-pr-salvage-ledger.md and legacy inventory | in_progress | legacy salvage ledger and ITO-55 tracking are present | final translation/manual-review tail remains |
+| Keep Linear roadmap detailed and progress tracking synchronized | Linear project mirror plus progress-sync contract | in_progress | repo mirror and progress-sync contract are present | recurring Linear status sync and productized realtime sync remain pending |
+| Provide ECC 2.0 observability for self-use | observability readiness gate | complete | observability:ready command and readiness doc exist | runtime/dashboard implementation can continue after release gates |
+| Keep Mini Shai-Hulud/TanStack protection loop current | supply-chain watch plus runbook | current | scheduled supply-chain watch now emits IOC and advisory-source refresh artifacts | Linear status synchronization remains ITO-57 follow-up after each significant merge batch |
+
+## Top Actions
+
+- `ecc-preview-pack`: final clean-checkout release approval and publish evidence still pending
+- `hermes-specialized-skills`: final preview-pack smoke and release review pending
+- `naming-and-plugin-publication`: real tag/push, marketplace submission, and final channel choice remain approval-gated
+- `release-notes-and-notifications`: URL-backed refresh and publish approval still pending
+- `agentshield-enterprise-iteration`: workflow automation around protected rollout and richer runtime review UX pending after policy promotion shipped
+- `ecc-tools-next-level`: live Marketplace test-account readback, hosted promotion telemetry, and richer operator review UX pending
+- `legacy-salvage`: final translation/manual-review tail remains
+- `linear-roadmap-and-progress`: recurring Linear status sync and productized realtime sync remain pending
+
+## Next Work Order
+
+1. Regenerate this dashboard from the final release commit before publication evidence is recorded.
+2. Continue ITO-57 with Linear status synchronization for the scheduled supply-chain watch advisory-source report.
+3. Advance ECC Tools live Marketplace test-account readback before publishing native-payments announcement copy.
+4. Resume ITO-45, ITO-46, and ITO-56 only after the generated dashboard and final release gates are refreshed.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-17.md

@@ -0,0 +1,51 @@
+# ECC Operator Readiness Dashboard
+
+This dashboard is generated by `npm run operator:dashboard`. It is an operator snapshot, not release approval.
+
+Generated: 2026-05-18T01:50:19.099Z
+Commit: 000df72d6b9c5b11feb11deef609911943b48424
+Status: work remaining
+
+## Current Status
+
+| Area | Status | Evidence |
+| --- | --- | --- |
+| PR queue | Current | 0 open PRs across tracked repos |
+| Issue queue | Current | 0 open issues across tracked repos |
+| Discussions | Current | 0 need maintainer touch; 0 missing accepted answer |
+| Local worktree | Current | 0 blocking dirty files; 1 ignored dirty entries |
+| Dashboard generation | Current | platform audit ready: true; GitHub skipped: false |
+| Publication | Not complete | release, npm, plugin, billing, and announcement gates are tracked below |
+
+## Prompt-To-Artifact Checklist
+
+| Objective requirement | Artifact or gate | Status | Evidence | Gap |
+| --- | --- | --- | --- | --- |
+| Keep public PRs below 20 | scripts/platform-audit.js live GitHub sweep | current | 0 open PRs across 5 tracked repos | repeat before release |
+| Keep public issues below 20 | scripts/platform-audit.js live GitHub sweep | current | 0 open issues across 5 tracked repos | repeat before release |
+| Respond and manage repository discussions | scripts/platform-audit.js discussion summary | current | 0 need maintainer touch; 0 answerable discussions missing accepted answer | repeat before release |
+| Build ITO-44 completion dashboard into a repeatable command | npm run operator:dashboard | complete | operator:dashboard package script exists | keep generated dashboard attached to publication evidence |
+| ECC 2.0 preview pack ready | docs/releases/2.0.0-rc.1/preview-pack-manifest.md | current | preview pack manifest and deterministic smoke gate are in-tree | repeat clean-checkout preview-pack smoke before publication |
+| Include Hermes specialized skills safely | docs/HERMES-SETUP.md and skills/hermes-imports/SKILL.md | current | Hermes setup/import artifacts are covered by preview-pack smoke | repeat preview-pack smoke before release review |
+| Prepare name-change, Claude plugin, and Codex plugin paths | naming-and-publication-matrix plus publication-readiness | in_progress | naming matrix and plugin readiness gates exist | real tag/push, marketplace submission, and final channel choice remain approval-gated |
+| Prepare release notes, articles, tweets, and push notifications | docs/releases/2.0.0-rc.1 social and release-copy files | in_progress | release notes, X thread, and LinkedIn draft are present | URL-backed refresh and publish approval still pending |
+| Advance AgentShield enterprise iteration | AgentShield PR evidence plus enterprise roadmap | in_progress | AgentShield policy promotion `reviewItems` landed in `87aec47`; package-manager hardening drift detection landed in `28d08c7`; workflow action runtime pins were refreshed in `659f569`; npm age-gate guidance was corrected in `ee585cd`; package-manager hardening Action outputs landed in `1124535`; policy-promotion Action outputs and runtime-smoke job-summary evidence landed in `1593925`; ECC-Tools consumes those outputs in `8658951`, surfaces operator-readable status/pack/count/digest telemetry in `16c537f`, and renders hosted promotion judge audit traces in `05d4e82`; all are mirrored in the GA roadmap | deepen live operator approval/readback after Marketplace/payment gates |
+| Advance ECC Tools native payments and AI-native harness-agnostic app | ECC Tools PR evidence, billing gate, hosted analysis lanes | in_progress | billing announcement gate, hosted analysis lanes, AgentShield fleet-summary consumption, hosted finding evidence paths, harness-route policy linking, policy-promotion Action-output telemetry, operator-visible promotion output details, hosted promotion judge audit traces, billing announcement preflight, and production KV readback state are mirrored in the GA roadmap | complete Marketplace purchase/webhook readback, then run the live announcement gate |
+| Audit, prune, or attach legacy work | docs/stale-pr-salvage-ledger.md and legacy inventory | current | legacy salvage ledger and inventory are current; all localization tails are attached to Linear ITO-55 for manual language-owner review | repeat legacy scan before release |
+| Keep Linear roadmap detailed and progress tracking synchronized | Linear project mirror plus progress-sync contract | current | Linear live sync and project progress snapshot are current; progress-sync contract defines the file-backed work-items/status path | repeat Linear/project status update and local work-items sync after each significant merge batch |
+| Provide ECC 2.0 observability for self-use | observability readiness gate | complete | observability:ready command and readiness doc exist | runtime/dashboard implementation can continue after release gates |
+| Keep Mini Shai-Hulud/TanStack protection loop current | supply-chain watch plus runbook plus AgentShield package-manager hardening | current | scheduled supply-chain watch emits IOC/advisory-source refresh artifacts; ECC scanner covers gh-token-monitor token-store persistence; AgentShield now detects known AI-tool persistence IOCs, npm lifecycle/token drift, unsupported npm age-key drift, and pnpm/Yarn cooldown drift; ITO-57 has May 17 Linear evidence updates | repeat advisory/source refresh and Linear sync after each significant supply-chain batch |
+
+## Top Actions
+
+- `naming-and-plugin-publication`: real tag/push, marketplace submission, and final channel choice remain approval-gated
+- `release-notes-and-notifications`: URL-backed refresh and publish approval still pending
+- `agentshield-enterprise-iteration`: deepen live operator approval/readback after Marketplace/payment gates
+- `ecc-tools-next-level`: complete Marketplace purchase/webhook readback, then run the live announcement gate
+
+## Next Work Order
+
+1. Regenerate this dashboard from the final release commit before publication evidence is recorded.
+2. Repeat ITO-57 Linear/project status sync after the next significant merge batch or advisory-source refresh.
+3. Complete ECC Tools Marketplace purchase/webhook readback, then run preflight and the live announcement gate before publishing native-payments copy.
+4. Resume ITO-45, ITO-46, and ITO-56 only after the generated dashboard and final release gates are refreshed.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-18.md

@@ -0,0 +1,51 @@
+# ECC Operator Readiness Dashboard
+
+This dashboard is generated by `npm run operator:dashboard`. It is an operator snapshot, not release approval.
+
+Generated: 2026-05-18T20:25:22.649Z
+Commit: 4470e2e6702f17099d6feb137ba03ff00582c202
+Status: work remaining
+
+## Current Status
+
+| Area | Status | Evidence |
+| --- | --- | --- |
+| PR queue | Current | 0 open PRs across tracked repos |
+| Issue queue | Current | 0 open issues across tracked repos |
+| Discussions | Current | 0 need maintainer touch; 0 missing accepted answer |
+| Local worktree | Current | 0 blocking dirty files; 0 ignored dirty entries |
+| Dashboard generation | Current | platform audit ready: true; GitHub skipped: false |
+| Publication | Not complete | release, npm, plugin, billing, and announcement gates are tracked below |
+
+## Prompt-To-Artifact Checklist
+
+| Objective requirement | Artifact or gate | Status | Evidence | Gap |
+| --- | --- | --- | --- | --- |
+| Keep public PRs below 20 | scripts/platform-audit.js live GitHub sweep plus owner-wide queue cleanup ledger | current | 0 open PRs across 5 tracked repos; 0 owner-wide open PRs after cleanup | repeat platform:audit and owner-wide gh search before release |
+| Keep public issues below 20 | scripts/platform-audit.js live GitHub sweep plus owner-wide queue cleanup ledger | current | 0 open issues across 5 tracked repos; 0 owner-wide open issues after cleanup | repeat platform:audit and owner-wide gh search before release |
+| Respond and manage repository discussions | scripts/platform-audit.js discussion summary | current | 0 need maintainer touch; 0 answerable discussions missing accepted answer | repeat before release |
+| Build ITO-44 completion dashboard into a repeatable command | npm run operator:dashboard | complete | operator:dashboard package script exists | keep generated dashboard attached to publication evidence |
+| ECC 2.0 preview pack ready | docs/releases/2.0.0-rc.1/preview-pack-manifest.md | current | preview pack manifest and deterministic smoke gate are in-tree | repeat clean-checkout preview-pack smoke before publication |
+| Include Hermes specialized skills safely | docs/HERMES-SETUP.md and skills/hermes-imports/SKILL.md | current | Hermes setup/import artifacts are covered by preview-pack smoke | repeat preview-pack smoke before release review |
+| Prepare name-change, Claude plugin, and Codex plugin paths | naming-and-publication-matrix plus release-name-plugin-publication checklist plus publication-readiness | in_progress | naming matrix, release publication checklist, and plugin readiness gates exist | real tag/push, marketplace submission, and final channel choice remain approval-gated |
+| Prepare release notes, articles, tweets, and push notifications | docs/releases/2.0.0-rc.1 social and release-copy files | in_progress | release notes, X thread, LinkedIn draft, and URL ledger are present | final live release/npm/plugin/billing URLs and publish approval still pending |
+| Advance AgentShield enterprise iteration | AgentShield PR evidence plus enterprise roadmap | in_progress | AgentShield policy promotion `reviewItems` landed in `87aec47`; package-manager hardening drift detection landed in `28d08c7`; workflow action runtime pins were refreshed in `659f569`; npm age-gate guidance was corrected in `ee585cd`; package-manager hardening Action outputs landed in `1124535`; policy-promotion Action outputs and runtime-smoke job-summary evidence landed in `1593925`; fleet review ticket payloads and current Mini Shai-Hulud IOC breadcrumbs landed in `840952a`; ECC-Tools consumes those outputs in `8658951`, surfaces operator-readable status/pack/count/digest telemetry in `16c537f`, and renders hosted promotion judge audit traces in `05d4e82`; all are mirrored in the GA roadmap | deepen live operator approval/readback after Marketplace/payment gates |
+| Advance ECC Tools native payments and AI-native harness-agnostic app | ECC Tools PR evidence, billing gate, hosted analysis lanes | in_progress | billing announcement gate, hosted analysis lanes, AgentShield fleet-summary consumption, hosted finding evidence paths, harness-route policy linking, policy-promotion Action-output telemetry, operator-visible promotion output details, hosted promotion judge audit traces, billing announcement preflight, aggregate production billing KV readback, Wrangler OAuth readback, target-account billing readback, provenance-aware Marketplace billing-state gates, sanitized Marketplace plan/action provenance counts, hosted team-learning feedback controls, and ECC-Tools Dependabot alert remediation are mirrored in the GA roadmap | create or verify Marketplace-managed Pro target billing-state with webhook provenance, configure the target account and INTERNAL_API_SECRET, then rerun target readback and the live announcement gate |
+| Audit, prune, or attach legacy work | docs/stale-pr-salvage-ledger.md and legacy inventory | current | legacy salvage ledger and inventory are current; all localization tails are attached to Linear ITO-55 for manual language-owner review | repeat legacy scan before release |
+| Keep Linear roadmap detailed and progress tracking synchronized | Linear project mirror plus progress-sync contract | current | Linear live sync and project progress surface are current; progress-sync contract defines the file-backed work-items/status path | repeat Linear/project status update and local work-items sync after each significant merge batch |
+| Provide ECC 2.0 observability for self-use | observability readiness gate | complete | observability:ready command and readiness doc exist | runtime/dashboard implementation can continue after release gates |
+| Keep Mini Shai-Hulud/TanStack protection loop current | supply-chain watch plus runbook plus AgentShield package-manager hardening | current | scheduled supply-chain watch emits IOC/advisory-source refresh artifacts; ECC scanner covers gh-token-monitor token-store persistence; AgentShield now detects known AI-tool persistence IOCs, npm lifecycle/token drift, unsupported npm age-key drift, and pnpm/Yarn cooldown drift; current-head watch evidence and ITO-57 May 18 Linear evidence updates are current | repeat advisory/source refresh and Linear sync after each significant supply-chain batch |
+
+## Top Actions
+
+- `naming-and-plugin-publication`: real tag/push, marketplace submission, and final channel choice remain approval-gated
+- `release-notes-and-notifications`: final live release/npm/plugin/billing URLs and publish approval still pending
+- `agentshield-enterprise-iteration`: deepen live operator approval/readback after Marketplace/payment gates
+- `ecc-tools-next-level`: create or verify Marketplace-managed Pro target billing-state with webhook provenance, configure the target account and INTERNAL_API_SECRET, then rerun target readback and the live announcement gate
+
+## Next Work Order
+
+1. Regenerate this dashboard from the final release commit before publication evidence is recorded.
+2. Repeat ITO-57 Linear/project status sync after the next significant merge batch or advisory-source refresh.
+3. Create or verify Marketplace-managed Pro target billing-state with webhook provenance, configure the target account and INTERNAL_API_SECRET, then rerun target readback and the live announcement gate before publishing native-payments copy.
+4. Resume ITO-45, ITO-46, and ITO-56 only after the generated dashboard and final release gates are refreshed.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-19.md

@@ -0,0 +1,66 @@
+# ECC Operator Readiness Dashboard
+
+This dashboard is generated by `npm run operator:dashboard`. It is an operator snapshot, not release approval.
+
+Generated: 2026-05-20T01:28:52.541Z
+Commit: a2bbc45504ff55f09e9e06be0e253d72f3c54f90
+Status: work remaining
+
+## Current Status
+
+| Area | Status | Evidence |
+| --- | --- | --- |
+| PR queue | Current | 0 open PRs across tracked repos |
+| Issue queue | Current | 0 open issues across tracked repos |
+| Discussions | Current | 0 need maintainer touch; 0 missing accepted answer |
+| Local worktree | Current | 0 blocking dirty files; 0 ignored dirty entries |
+| Dashboard generation | Current | platform audit ready: true; GitHub skipped: false |
+| Publication | Not complete | release, npm, plugin, billing, and announcement gates are tracked below |
+
+## Growth Baseline
+
+| Metric | Current | Target | Gap |
+| --- | ---: | ---: | ---: |
+| MRR | $1,728/mo | $10,000/mo | $8,272/mo |
+
+Growth lanes: GitHub Sponsors and OSS partner sponsors; ECC Tools Pro subscriptions; consulting and implementation contracts; talks, podcasts, conference demos, and partner webinars.
+
+## Prompt-To-Artifact Checklist
+
+| Objective requirement | Artifact or gate | Status | Evidence | Gap |
+| --- | --- | --- | --- | --- |
+| Keep public PRs below 20 | scripts/platform-audit.js live GitHub sweep plus owner-wide queue cleanup ledger | current | 0 open PRs across 5 tracked repos; 0 owner-wide open PRs after cleanup | repeat platform:audit and owner-wide gh search before release |
+| Keep public issues below 20 | scripts/platform-audit.js live GitHub sweep plus owner-wide queue cleanup ledger | current | 0 open issues across 5 tracked repos; 0 owner-wide open issues after cleanup | repeat platform:audit and owner-wide gh search before release |
+| Respond and manage repository discussions | scripts/platform-audit.js discussion summary | current | 0 need maintainer touch; 0 answerable discussions missing accepted answer | repeat before release |
+| Build ITO-44 completion dashboard into a repeatable command | npm run operator:dashboard | complete | operator:dashboard package script exists | keep generated dashboard attached to publication evidence |
+| ECC 2.0 preview pack ready | docs/releases/2.0.0-rc.1/preview-pack-manifest.md | current | preview pack manifest and deterministic smoke gate are in-tree | repeat clean-checkout preview-pack smoke before publication |
+| Include Hermes specialized skills safely | docs/HERMES-SETUP.md and skills/hermes-imports/SKILL.md | current | Hermes setup/import artifacts are covered by preview-pack smoke | repeat preview-pack smoke before release review |
+| Prepare name-change, Claude plugin, and Codex plugin paths | naming-and-publication-matrix plus release-name-plugin-publication checklist plus publication-readiness | in_progress | naming matrix, release publication checklist, and plugin readiness gates exist | real tag/push, marketplace submission, and final channel choice remain approval-gated |
+| Prepare release notes, articles, tweets, and push notifications | docs/releases/2.0.0-rc.1 social and release-copy files | in_progress | release notes, X thread, LinkedIn draft, and URL ledger are present | final live release/npm/plugin/billing URLs and publish approval still pending |
+| Prepare final owner approval packet | docs/releases/2.0.0-rc.1/owner-approval-packet-2026-05-19.md | current | owner approval packet covers release, package, plugin, video, billing, social, and outbound decisions | review owner approvals from the final release commit before any publication or outbound action |
+| Create a second-phase hypergrowth release command center | docs/releases/2.0.0/ecc-2-hypergrowth-release-command-center.md plus May 19 evidence | current | current MRR, target MRR, gap, release claim, video lane, distribution plan, and approval boundaries are in-tree | refresh after every MRR, channel, or approval-state change before public launch |
+| Produce the ECC 2.0 release video suite | docs/releases/2.0.0-rc.1/video-suite-production.md and npm run release:video-suite | current | video-suite gate is ready with 15/15 source assets, 13/13 suite artifacts, 12/12 publish candidates, primary self-eval, and zero detected black-frame segments recorded in May 19 evidence | final owner approval, upload, and public video URLs remain approval-gated |
+| Prepare sponsor, partner, consulting, podcast, talk, and Discussion copy | docs/releases/2.0.0-rc.1/partner-sponsor-talks-pack.md | in_progress | sponsor outbound, platform partner DM, consulting intro, talk/podcast pitch, GitHub Discussion announcement, CTA hooks, and do-not-send gate are drafted | replace final URLs after publication gates, then get explicit approval before outbound or personal-account posts |
+| Advance AgentShield enterprise iteration | AgentShield PR evidence plus enterprise roadmap | in_progress | AgentShield policy promotion `reviewItems` landed in `87aec47`; package-manager hardening drift detection landed in `28d08c7`; workflow action runtime pins were refreshed in `659f569`; npm age-gate guidance was corrected in `ee585cd`; package-manager hardening Action outputs landed in `1124535`; policy-promotion Action outputs and runtime-smoke job-summary evidence landed in `1593925`; fleet review ticket payloads and current Mini Shai-Hulud IOC breadcrumbs landed in `840952a`; ECC-Tools consumes those outputs in `8658951`, surfaces operator-readable status/pack/count/digest telemetry in `16c537f`, and renders hosted promotion judge audit traces in `05d4e82`; all are mirrored in the GA roadmap | deepen live operator approval/readback after Marketplace/payment gates |
+| Advance ECC Tools native payments and AI-native harness-agnostic app | ECC Tools PR evidence, billing gate, hosted analysis lanes | in_progress | billing announcement gate, hosted analysis lanes, AgentShield fleet-summary consumption, hosted finding evidence paths, harness-route policy linking, policy-promotion Action-output telemetry, operator-visible promotion output details, hosted promotion judge audit traces, billing announcement preflight, aggregate production billing KV readback, Wrangler OAuth readback, target-account billing readback, provenance-aware Marketplace billing-state gates, sanitized Marketplace plan/action provenance counts, ready Marketplace Pro target selection, hosted team-learning feedback controls, and ECC-Tools Dependabot alert remediation are mirrored in the GA roadmap | obtain or rotate the local/internal INTERNAL_API_SECRET bearer-token path, then run the live billing announcement gate for the selected Marketplace Pro target before publishing native-payments copy |
+| Audit, prune, or attach legacy work | docs/stale-pr-salvage-ledger.md and legacy inventory | current | legacy salvage ledger and inventory are current; all localization tails are attached to Linear ITO-55 for manual language-owner review | repeat legacy scan before release |
+| Keep Linear roadmap detailed and progress tracking synchronized | Linear project mirror plus progress-sync contract | current | Linear live sync is current with the May 19 post-PR #2002 sync document, project comment, and active issue-lane updates; progress-sync contract defines the file-backed work-items/status path | repeat Linear/project status update and local work-items sync after each significant merge batch |
+| Provide ECC 2.0 observability for self-use | observability readiness gate | complete | observability:ready command and readiness doc exist | runtime/dashboard implementation can continue after release gates |
+| Keep Mini Shai-Hulud/TanStack protection loop current | supply-chain watch plus runbook plus AgentShield package-manager hardening | current | scheduled supply-chain watch emits IOC/advisory-source refresh artifacts; ECC scanner covers gh-token-monitor token-store persistence; AgentShield now detects known AI-tool persistence IOCs, npm lifecycle/token drift, unsupported npm age-key drift, and pnpm/Yarn cooldown drift; current-head watch evidence and ITO-57 May 18 Linear evidence updates are current | repeat advisory/source refresh and Linear sync after each significant supply-chain batch |
+
+## Top Actions
+
+- `naming-and-plugin-publication`: real tag/push, marketplace submission, and final channel choice remain approval-gated
+- `release-notes-and-notifications`: final live release/npm/plugin/billing URLs and publish approval still pending
+- `partner-sponsor-talks-pack`: replace final URLs after publication gates, then get explicit approval before outbound or personal-account posts
+- `agentshield-enterprise-iteration`: deepen live operator approval/readback after Marketplace/payment gates
+- `ecc-tools-next-level`: obtain or rotate the local/internal INTERNAL_API_SECRET bearer-token path, then run the live billing announcement gate for the selected Marketplace Pro target before publishing native-payments copy
+
+## Next Work Order
+
+1. Regenerate this dashboard from the final release commit before publication evidence is recorded.
+2. Review the owner approval packet from the final release commit and approve, defer, or block each publication and outbound lane.
+3. Review the owner-approved primary launch video candidates, choose the final cuts, upload after approval, and attach public video URLs to the release pack.
+4. Replace final release, npm, plugin, billing, and video URLs in the partner/sponsor/talk pack, then get explicit approval before outbound.
+5. Repeat ITO-57 Linear/project status sync after the next significant merge batch or advisory-source refresh.
+6. Obtain or rotate the local/internal INTERNAL_API_SECRET bearer-token path, then run the live billing announcement gate for the selected Marketplace Pro target before publishing native-payments copy.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-20.md

@@ -0,0 +1,66 @@
+# ECC Operator Readiness Dashboard
+
+This dashboard is generated by `npm run operator:dashboard`. It is an operator snapshot, not release approval.
+
+Generated: 2026-05-20T03:14:39.338Z
+Commit: 66733b511b70cf1cb501e8a3298b1cbd9968a9a0
+Status: work remaining
+
+## Current Status
+
+| Area | Status | Evidence |
+| --- | --- | --- |
+| PR queue | Current | 0 open PRs across tracked repos |
+| Issue queue | Current | 0 open issues across tracked repos |
+| Discussions | Current | 0 need maintainer touch; 0 missing accepted answer |
+| Local worktree | Current | 0 blocking dirty files; 0 ignored dirty entries |
+| Dashboard generation | Current | platform audit ready: true; GitHub skipped: false |
+| Publication | Not complete | release, npm, plugin, billing, and announcement gates are tracked below |
+
+## Growth Baseline
+
+| Metric | Current | Target | Gap |
+| --- | ---: | ---: | ---: |
+| MRR | $1,728/mo | $10,000/mo | $8,272/mo |
+
+Growth lanes: GitHub Sponsors and OSS partner sponsors; ECC Tools Pro subscriptions; consulting and implementation contracts; talks, podcasts, conference demos, and partner webinars.
+
+## Prompt-To-Artifact Checklist
+
+| Objective requirement | Artifact or gate | Status | Evidence | Gap |
+| --- | --- | --- | --- | --- |
+| Keep public PRs below 20 | scripts/platform-audit.js live GitHub sweep plus owner-wide queue cleanup ledger | current | 0 open PRs across 5 tracked repos; 0 owner-wide open PRs after cleanup | repeat platform:audit and owner-wide gh search before release |
+| Keep public issues below 20 | scripts/platform-audit.js live GitHub sweep plus owner-wide queue cleanup ledger | current | 0 open issues across 5 tracked repos; 0 owner-wide open issues after cleanup | repeat platform:audit and owner-wide gh search before release |
+| Respond and manage repository discussions | scripts/platform-audit.js discussion summary | current | 0 need maintainer touch; 0 answerable discussions missing accepted answer | repeat before release |
+| Build ITO-44 completion dashboard into a repeatable command | npm run operator:dashboard | complete | operator:dashboard package script exists | keep generated dashboard attached to publication evidence |
+| ECC 2.0 preview pack ready | docs/releases/2.0.0-rc.1/preview-pack-manifest.md | current | preview pack manifest and deterministic smoke gate are in-tree | repeat clean-checkout preview-pack smoke before publication |
+| Include Hermes specialized skills safely | docs/HERMES-SETUP.md and skills/hermes-imports/SKILL.md | current | Hermes setup/import artifacts are covered by preview-pack smoke | repeat preview-pack smoke before release review |
+| Prepare name-change, Claude plugin, and Codex plugin paths | naming-and-publication-matrix plus release-name-plugin-publication checklist plus publication-readiness | in_progress | naming matrix, release publication checklist, and plugin readiness gates exist | real tag/push, marketplace submission, and final channel choice remain approval-gated |
+| Prepare release notes, articles, tweets, and push notifications | docs/releases/2.0.0-rc.1 social and release-copy files | in_progress | release notes, X thread, LinkedIn draft, and URL ledger are present | final live release/npm/plugin/billing URLs and publish approval still pending |
+| Prepare final owner approval packet | docs/releases/2.0.0-rc.1/owner-approval-packet-2026-05-19.md | current | owner approval packet covers release, package, plugin, video, billing, social, and outbound decisions | review owner approvals from the final release commit before any publication or outbound action |
+| Create a second-phase hypergrowth release command center | docs/releases/2.0.0/ecc-2-hypergrowth-release-command-center.md plus May 19 evidence | current | current MRR, target MRR, gap, release claim, video lane, distribution plan, and approval boundaries are in-tree | refresh after every MRR, channel, or approval-state change before public launch |
+| Produce the ECC 2.0 release video suite | docs/releases/2.0.0-rc.1/video-suite-production.md and npm run release:video-suite | current | video-suite gate is ready with 15/15 source assets, 13/13 suite artifacts, 12/12 publish candidates, primary self-eval, and zero detected black-frame segments recorded in May 19 evidence | final owner approval, upload, and public video URLs remain approval-gated |
+| Prepare sponsor, partner, consulting, podcast, talk, and Discussion copy | docs/releases/2.0.0-rc.1/partner-sponsor-talks-pack.md | in_progress | sponsor outbound, platform partner DM, consulting intro, talk/podcast pitch, GitHub Discussion announcement, CTA hooks, and do-not-send gate are drafted | replace final URLs after publication gates, then get explicit approval before outbound or personal-account posts |
+| Advance AgentShield enterprise iteration | AgentShield PR evidence plus enterprise roadmap | in_progress | AgentShield policy promotion `reviewItems` landed in `87aec47`; package-manager hardening drift detection landed in `28d08c7`; workflow action runtime pins were refreshed in `659f569`; npm age-gate guidance was corrected in `ee585cd`; package-manager hardening Action outputs landed in `1124535`; policy-promotion Action outputs and runtime-smoke job-summary evidence landed in `1593925`; fleet review ticket payloads and current Mini Shai-Hulud IOC breadcrumbs landed in `840952a`; ECC-Tools consumes those outputs in `8658951`, surfaces operator-readable status/pack/count/digest telemetry in `16c537f`, and renders hosted promotion judge audit traces in `05d4e82`; all are mirrored in the GA roadmap | deepen live operator approval/readback after Marketplace/payment gates |
+| Advance ECC Tools native payments and AI-native harness-agnostic app | ECC Tools PR evidence, billing gate, hosted analysis lanes | in_progress | billing announcement gate, selected-target announcement gate, billing gate env-file operator path, non-breaking operator bearer path, hosted analysis lanes, AgentShield fleet-summary consumption, hosted finding evidence paths, harness-route policy linking, policy-promotion Action-output telemetry, operator-visible promotion output details, hosted promotion judge audit traces, billing announcement preflight, aggregate production billing KV readback, Wrangler selected-target readback, target-account billing readback, provenance-aware Marketplace billing-state gates, sanitized Marketplace plan/action provenance counts, ready Marketplace Pro target selection, hosted team-learning feedback controls, and ECC-Tools Dependabot alert remediation are mirrored in the GA roadmap | repeat KV readback and selected-target announcement gate immediately before launch; keep native-payments copy behind the final release, plugin, URL, and owner-approval gates |
+| Audit, prune, or attach legacy work | docs/stale-pr-salvage-ledger.md and legacy inventory | current | legacy salvage ledger and inventory are current; all localization tails are attached to Linear ITO-55 for manual language-owner review | repeat legacy scan before release |
+| Keep Linear roadmap detailed and progress tracking synchronized | Linear project mirror plus progress-sync contract | current | Linear live sync is current with the May 20 Marketplace Pro release-gate comments on ITO-61 and the ECC platform roadmap; progress-sync contract defines the file-backed work-items/status path | repeat Linear/project status update and local work-items sync after each significant merge batch |
+| Provide ECC 2.0 observability for self-use | observability readiness gate | complete | observability:ready command and readiness doc exist | runtime/dashboard implementation can continue after release gates |
+| Keep Mini Shai-Hulud/TanStack protection loop current | supply-chain watch plus runbook plus AgentShield package-manager hardening | current | scheduled supply-chain watch emits IOC/advisory-source refresh artifacts; ECC scanner covers gh-token-monitor token-store persistence; AgentShield now detects known AI-tool persistence IOCs, npm lifecycle/token drift, unsupported npm age-key drift, and pnpm/Yarn cooldown drift; current-head watch evidence and ITO-57 May 18 Linear evidence updates are current | repeat advisory/source refresh and Linear sync after each significant supply-chain batch |
+
+## Top Actions
+
+- `naming-and-plugin-publication`: real tag/push, marketplace submission, and final channel choice remain approval-gated
+- `release-notes-and-notifications`: final live release/npm/plugin/billing URLs and publish approval still pending
+- `partner-sponsor-talks-pack`: replace final URLs after publication gates, then get explicit approval before outbound or personal-account posts
+- `agentshield-enterprise-iteration`: deepen live operator approval/readback after Marketplace/payment gates
+- `ecc-tools-next-level`: repeat KV readback and selected-target announcement gate immediately before launch; keep native-payments copy behind the final release, plugin, URL, and owner-approval gates
+
+## Next Work Order
+
+1. Regenerate this dashboard from the final release commit before publication evidence is recorded.
+2. Review the owner approval packet from the final release commit and approve, defer, or block each publication and outbound lane.
+3. Review the owner-approved primary launch video candidates, choose the final cuts, upload after approval, and attach public video URLs to the release pack.
+4. Replace final release, npm, plugin, billing, and video URLs in the partner/sponsor/talk pack, then get explicit approval before outbound.
+5. Repeat ITO-57 Linear/project status sync after the next significant merge batch or advisory-source refresh.
+6. Repeat KV readback and the selected-target billing announcement gate immediately before launch; keep native-payments copy behind the final release, plugin, URL, and owner-approval gates.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/owner-approval-packet-2026-05-19.md

@@ -0,0 +1,100 @@
+# ECC v2.0.0-rc.1 Owner Approval Packet
+
+Snapshot date: 2026-05-19.
+
+This packet is the final human decision sheet for the rc.1 public launch. It
+does not publish anything by itself. Use it to approve, defer, or block each
+release action after the final evidence commands are rerun from the intended
+release commit.
+
+Source commit for the clean evidence baseline this packet extends:
+`9819626459a662773be7d0b1c18d82c1316b8c36`.
+
+## Current Evidence
+
+| Evidence | Current recorded state | Repeat before approval |
+| --- | --- | --- |
+| Platform audit | ready true, 0 open PRs, 0 open issues, 0 discussion gaps, 0 dirty files | yes |
+| Preview pack smoke | ready true, digest `531328aaaa53`, 5/5 checks | yes |
+| Release approval gate | ready false, digest `ef8f49f727b7`, 4/6 checks pass; owner decisions and live URL readbacks pending | yes |
+| GitHub prerelease | live at <https://github.com/affaan-m/ECC/releases/tag/v2.0.0-rc.1>; prerelease true, draft false, published `2026-05-25T18:29:31Z` | yes |
+| npm `next` publish | live at <https://www.npmjs.com/package/ecc-universal/v/2.0.0-rc.1>; `next` points to `2.0.0-rc.1`, `latest` remains `1.10.0` | yes |
+| Video suite | ready true, 15/15 source assets, 13/13 suite artifacts, 12/12 publish candidates | yes |
+| Release surface tests | 28/28 passed after the May 26 URL/package refresh | yes |
+| Full local suite | 2568/2568 passed before PR #2013 merged; focused GateGuard regression passed 91/91 again before PR #2011 merged | yes |
+| GitHub CI | PR #1998, PR #1999, PR #2000, PR #2001, PR #2002, PR #2004, PR #2008, post-PR #2006 `main`, PR #2009, post-PR #2009 `main`, post-PR #2011 `main`, and post-PR #2013 `main` all merged or advanced after green required checks | verify current head |
+
+## Decision Register
+
+| Decision | Approve / defer / block | Evidence required first | Notes |
+| --- | --- | --- | --- |
+| GitHub prerelease | approve | live prerelease readback | Live at <https://github.com/affaan-m/ECC/releases/tag/v2.0.0-rc.1>. Remaining plugin/video/billing URLs stay approval-gated. |
+| npm `next` publish | approve | `npm pack --dry-run`, `npm publish --tag next`, registry dist-tag readback | `ecc-universal@2.0.0-rc.1` is published on `next`; `latest` remains `1.10.0` during rc.1. |
+| Claude plugin tag | defer | `claude plugin validate .claude-plugin/plugin.json`, `claude plugin tag .claude-plugin --dry-run` | Create and push the real tag only after release approval. |
+| Codex repo marketplace | defer | temp-home marketplace add smoke and current official Plugin Directory status | Claim repo-marketplace distribution only; do not claim official Plugin Directory listing without listing evidence. |
+| ECC Tools billing language | defer | live readiness readback for the target account and billing/product state | Do not announce native payments or Marketplace-managed Pro until the gate is live. |
+| Video upload | defer | owner selects primary launch cut plus short clips, self-eval stays clean | Upload only approved cuts; keep editable timeline/project output preserved. |
+| X, LinkedIn, GitHub Discussion, longform | defer | live release, npm, plugin, video, and billing URL ledger updates | Personal-account posts and outbound copy need explicit approval. |
+| Sponsor, partner, consulting, conference, podcast outreach | defer | final public URLs plus owner-approved outbound copy | Do not send drafts until the owner approves the exact batch. |
+
+## Final URL Fill-In
+
+Update these surfaces after the approved publication actions finish:
+
+| Surface | Final value source | Update targets |
+| --- | --- | --- |
+| GitHub prerelease URL | `gh release view v2.0.0-rc.1 --repo affaan-m/ECC --json url` | release notes, URL ledger, social copy |
+| npm rc package URL | `npm view ecc-universal@2.0.0-rc.1 name version dist.tarball dist.integrity time --json` | URL ledger, quickstart, release notes |
+| Claude plugin tag URL | pushed `ecc--v2.0.0-rc.1` tag or marketplace readback | URL ledger, plugin docs, release notes |
+| Codex repo-marketplace evidence | temp-home `codex plugin marketplace add <local-checkout>` readback | URL ledger, publication readiness |
+| Primary launch video URL | uploaded owner-approved primary launch video | GitHub release, X, LinkedIn, longform |
+| Short clip URLs | uploaded approved clips | X thread, LinkedIn, partner/sponsor/talk pack |
+| ECC Tools billing/readiness URL | live readiness readback or explicit blocked status | sponsor copy, Pro copy, release notes |
+
+## Final Evidence Commands
+
+Run these from the exact release commit before approving publication:
+
+```bash
+git status --short --branch
+node scripts/platform-audit.js --json
+npm run preview-pack:smoke -- --format json
+npm run release:approval-gate -- --format json
+npm run release:video-suite -- --format json
+npm run harness:adapters -- --check
+npm run harness:audit -- --format json
+npm run observability:ready
+npm run security:ioc-scan
+npm audit --audit-level=moderate
+npm audit signatures
+node tests/docs/ecc2-release-surface.test.js
+node tests/hooks/gateguard-fact-force.test.js
+node tests/run-all.js
+cd ecc2 && cargo test
+```
+
+## Approval Text
+
+Use short, explicit approvals. Example:
+
+```text
+Approved for rc.1 GitHub prerelease, npm next publish, Claude plugin tag, and
+release announcement after the final evidence commands pass from commit <sha>.
+Video uploads approved for <primary-video> and <shorts-list>.
+Outbound sponsor, partner, consulting, conference, and podcast messages remain
+blocked until I approve the exact batch.
+```
+
+## Do Not Approve If
+
+- The final branch is dirty or no longer matches the intended release commit.
+- Any required evidence command fails or is skipped without a written deferral.
+- The release copy claims live billing, plugin marketplace propagation, npm
+  `next`, or official Codex Plugin Directory listing before readback exists.
+- Announcement copy contains stale URLs, private paths, or unresolved live-link
+  decisions.
+- The selected video cut has black frames, missing audio, stale URLs, weak
+  product proof, or unreviewed captions.
+- The outbound batch has not been reviewed exactly as it will be sent.
+
+No outbound email, personal-account post, package publish, plugin tag, or billing announcement is authorized by this packet alone.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/owner-queue-cleanup-2026-05-18.md

@@ -0,0 +1,65 @@
+# Owner-Wide Queue Cleanup - 2026-05-18
+
+This note records the live GitHub queue cleanup outside the five ECC release
+repos tracked by `scripts/platform-audit.js`.
+
+## Commands
+
+```bash
+gh search prs --owner affaan-m --state open --json repository,number,title,url,author,updatedAt --limit 100
+gh search issues --owner affaan-m --state open --json repository,number,title,url,updatedAt --limit 100
+```
+
+## Result
+
+- Owner-wide open PRs after cleanup: 0.
+- Owner-wide open issues after cleanup: 0.
+- Stale dependency-bot PRs closed: 24.
+- Stale legacy payments/0EM roadmap issues closed: 72.
+- Final stale/generated/manual-review PRs closed: 9.
+- Final legacy/outreach/placeholder issues closed: 5.
+- Archived repos temporarily unarchived for stale dependency PR closure and
+  restored to archived state:
+  `affaan-m/stoictradingAI`, `affaan-m/dprc-autotrader-v2`,
+  `affaan-m/polycule-secure`, and `affaan-m/pragmAItism_defAInce`.
+- The final archived-repo sweep temporarily unarchived and restored
+  `affaan-m/dprc-autotrader-v2` and `affaan-m/stoictradingAI`.
+
+## Final PR Disposition
+
+- `affaan-m/dprc-autotrader-v2#5`: closed stale generated ECC bundle with
+  failing checks and dependency-update base.
+- `affaan-m/x-algorithm-score#2`: closed stale/conflicting external feature
+  PR with accidental local AI-tool directories noted in the PR body.
+- `affaan-m/dexploy#28`: closed stale generated ECC skill PR with requested
+  changes.
+- `affaan-m/zenith#5`: closed stale generated ECC skill PR.
+- `affaan-m/zenith#4`: closed test/noise PR whose diff only added a
+  non-actionable script comment.
+- `affaan-m/affaan-m#1`: closed stale/conflicting third-party README-card PR.
+- `affaan-m/affaanmustafa.com#1`: closed stale Cloudflare Worker-name PR with
+  requested changes.
+- `affaan-m/0em-payments-dashboard#11`: closed stale/conflicting Cloudflare
+  Worker-name PR.
+- `affaan-m/0em-payments-dashboard#3`: closed stale/conflicting Cloudflare
+  Worker-name PR.
+
+## Final Issue Disposition
+
+- `affaan-m/dprc-autotrader-v2#3`: closed public integration pitch as not
+  planned for the archived repo.
+- `affaan-m/stoictradingAI#20`: closed public outreach question as not planned
+  for the archived repo.
+- `affaan-m/dexploy#27`: closed stale internal skill-creator test issue.
+- `affaan-m/dexploy#25`: preserved useful deployment/localStorage and
+  Cloudflare findings in Linear `ITO-62`, then closed the stale GitHub issue.
+- `affaan-m/telegram-mcp-ts#1`: closed stale empty placeholder issue.
+
+## Disposition
+
+The closed dependency PRs were stale generated version bumps and should be
+regenerated from current bases if still needed. The closed generated ECC bundle
+PRs should be regenerated from the current ECC Tools flow if those repositories
+become active again. The closed legacy payments/0EM issues were old planning
+items superseded by the ECC Tools native-payments, hosted analysis,
+billing-readback, and Linear/project roadmap lanes.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/partner-sponsor-talks-pack.md

@@ -0,0 +1,217 @@
+# ECC v2.0.0-rc.1 Partner, Sponsor, and Talks Pack
+
+This pack turns the rc.1 release surface into outbound-ready copy for sponsors,
+partners, consulting conversations, conference talks, podcast bookings, and
+community announcements.
+
+It is not a publish action. Use it after the release URL ledger, video suite,
+and publication gates are current.
+
+## Current Business Baseline
+
+| Metric | Current | Target | Gap |
+| --- | ---: | ---: | ---: |
+| MRR | `$1,728/mo` | `$10,000/mo` | `$8,272/mo` |
+| Core revenue lanes | Sponsors, ECC Tools Pro, consulting, talks | Repeatable growth loop | Approval-gated outbound |
+| Launch proof | rc.1 preview pack, video suite, queue-zero audit | Public release package | Final URLs and human approval |
+
+## Positioning Line
+
+ECC 2.0 is the harness-native operator system for agentic work.
+
+Use this short version in partner and sponsor messages:
+
+```text
+ECC gives teams one reusable layer for skills, hooks, rules, MCP conventions,
+release gates, and operator workflows across Claude Code, Codex, OpenCode,
+Cursor, Gemini, Zed, GitHub Copilot, and terminal-only workflows.
+```
+
+## Offer Ladder
+
+| Motion | Best fit | Starting point | Primary ask |
+| --- | --- | ---: | --- |
+| Pilot sponsor | OSS-friendly team that wants early signal | `$200/mo` | GitHub Sponsors |
+| Business sponsor | Tooling or AI infra company that wants logo and case-study surface | `$500/mo` | GitHub Sponsors or direct invoice |
+| Strategic partner | Platform, marketplace, security, or developer-tool company | `$1,000+/mo` | Sponsor plus launch or integration plan |
+| Consulting sprint | Team adopting agent harnesses internally | Scoped quote | Harness audit, rollout plan, and operating loop |
+| Talk or podcast | Devtools, AI engineering, security, OSS, or founder audience | No fee required for high-leverage reach | Recording slot, demo slot, or conference proposal |
+
+## Partner Targets
+
+Prioritize partners that already benefit from a harness-agnostic operating
+layer:
+
+- AI coding platforms and IDEs;
+- hosted agent and workflow orchestration tools;
+- code review, security, and supply-chain vendors;
+- model and inference providers;
+- developer education, podcast, and conference organizers;
+- teams adopting multiple harnesses at once.
+
+## Sponsor Outbound
+
+Subject:
+
+```text
+ECC 2.0 sponsor slot for cross-harness agent workflows
+```
+
+Body:
+
+```text
+Hey [name],
+
+I am getting ECC v2.0.0-rc.1 ready for release review.
+
+The project is now positioned around one reusable operator layer for agentic
+work across Claude Code, Codex, OpenCode, Cursor, Gemini, Zed, GitHub Copilot,
+and terminal workflows.
+
+The sponsor fit is pretty direct: ECC reaches the exact builders who are
+standardizing their AI coding stack, security posture, and workflow automation.
+
+The current public sponsor ladder is:
+
+- Pilot Partner: $200/mo
+- Business Sponsor: $500/mo
+- Strategic Partner: $1,000+/mo
+
+Business sponsors get logo placement and release visibility. Strategic partners
+can turn it into a deeper integration or launch motion.
+
+Repo: https://github.com/affaan-m/ECC
+Sponsor: https://github.com/sponsors/affaan-m
+Release notes: https://github.com/affaan-m/ECC/blob/main/docs/releases/2.0.0-rc.1/release-notes.md
+
+If useful, I can send the short sponsor packet and a proposed first 30-day plan.
+
+Affaan
+```
+
+## Platform Partner DM
+
+```text
+ECC 2.0 is getting close to rc.1.
+
+The release is centered on cross-harness agent workflows: reusable skills,
+hooks, rules, MCP conventions, release gates, and an optional Hermes operator
+shell.
+
+The partner angle is not "another prompt pack." It is a tested operating layer
+for teams using more than one AI coding harness.
+
+I think there is a real integration or co-launch angle here if your team wants
+better setup, policy, security, or workflow portability for agent users.
+
+Repo: https://github.com/affaan-m/ECC
+```
+
+## Consulting Intro
+
+```text
+I am open to a small number of ECC 2.0 implementation sprints for teams that
+are standardizing AI coding workflows.
+
+The useful scope is usually:
+
+1. audit the current harness setup;
+2. turn repeated workflows into ECC skills, hooks, and rules;
+3. add release, security, and CI gates;
+4. create a team operating loop that works across Claude Code, Codex, OpenCode,
+   Cursor, Gemini, Zed, GitHub Copilot, and terminal workflows.
+
+This is not generic AI consulting. The output is a working harness operating
+system your team can keep using.
+```
+
+## Talk And Podcast Pitch
+
+Title options:
+
+- Building a Cross-Harness Operating System for AI Coding
+- From Prompt Packs to Operator Systems
+- What Breaks When Teams Adopt Too Many AI Coding Harnesses
+- Security and Release Discipline for Agentic Coding Workflows
+
+Short pitch:
+
+```text
+ECC started as an open-source workflow layer for Claude Code and is now moving
+toward a cross-harness operating system for agentic work.
+
+The talk is about the practical problems teams hit after the first AI coding
+honeymoon: scattered prompts, duplicated setup, weak release gates, fragile
+security posture, and no clear operating loop across tools.
+
+I can show how ECC uses reusable skills, hooks, MCP conventions, release gates,
+AgentShield-style security checks, and an optional Hermes operator shell to make
+agentic work more measurable and portable.
+```
+
+## GitHub Discussion Announcement
+
+```text
+ECC v2.0.0-rc.1 preview pack is ready for final release review.
+
+The main point: ECC 2.0 is a meta-harness for agentic work.
+
+It is the portable layer that keeps skills, hooks, MCP conventions, release
+gates, security checks, and team workflows reusable across the AI coding tools
+people actually use.
+
+It now has a reviewed public surface for:
+
+- reusable skills, hooks, rules, and MCP conventions;
+- Claude Code, Codex, OpenCode, Cursor, Gemini, Zed, GitHub Copilot, and
+  terminal workflows;
+- Hermes as the optional operator shell;
+- release, security, queue, discussion, Linear, observability, and video-suite
+  gates.
+- a gated Itô prediction-market skill pack for research, comparison, planning,
+  and risk review, with Itô API access kept separate and approval-based.
+
+The GitHub prerelease and npm `next` package are live now. The release remains
+approval-gated for plugin paths, video URLs, final outbound URLs, and billing
+claims that have not been freshly rechecked.
+
+Feedback wanted: install friction, cross-harness gaps, partner integrations,
+sponsor fit, prediction-market research use cases, and examples of teams using
+multiple AI coding harnesses.
+```
+
+## Video CTA Hooks
+
+Use these with the release video suite:
+
+- "If your AI coding setup only works in one harness, it is not an operating
+  system yet."
+- "ECC 2.0 is the shared layer: skills, hooks, MCPs, release gates, and team
+  workflows across the tools people actually use."
+- "OSS stays free. Sponsors, Pro, and implementation work fund the public
+  layer."
+- "Start with one workflow lane: engineering, research, content, or outreach."
+
+## Do Not Send Or Publish If
+
+- The release URL ledger still has stale or placeholder links.
+- `npm run release:video-suite -- --format json` is not green against the
+  intended video roots.
+- The GitHub prerelease or npm package readback is contradicted, or a plugin
+  path, video URL, billing claim, or official directory listing is described as
+  live without evidence.
+- The message claims native payments are ready before ECC Tools billing readback
+  passes.
+- The recipient needs a custom promise that is not covered by `SPONSORS.md`,
+  `SPONSORING.md`, or a separate consulting scope.
+- The user has not approved outbound sponsor, partner, consulting, or media
+  messages.
+
+## Routing Links
+
+- Repo: <https://github.com/affaan-m/ECC>
+- Release notes: <https://github.com/affaan-m/ECC/blob/main/docs/releases/2.0.0-rc.1/release-notes.md>
+- Quickstart: <https://github.com/affaan-m/ECC/blob/main/docs/releases/2.0.0-rc.1/quickstart.md>
+- Sponsor: <https://github.com/sponsors/affaan-m>
+- Sponsor tiers: <https://github.com/affaan-m/ECC/blob/main/SPONSORS.md>
+- Sponsoring guide: <https://github.com/affaan-m/ECC/blob/main/SPONSORING.md>

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/preview-pack-manifest.md

@@ -0,0 +1,149 @@
+# ECC v2.0.0-rc.1 Preview Pack Manifest
+
+This manifest defines the reviewed preview pack for `2.0.0-rc.1`. It is not a
+release action by itself. Use it to verify that the public launch surface stays
+assembled after the GitHub prerelease and npm `next` publish, and before
+tagging plugin surfaces, uploading video, or posting announcements.
+
+## Pack Contents
+
+| Artifact | Role | Gate |
+| --- | --- | --- |
+| `README.md` | Public onramp and install surface | Links Hermes setup, rc.1 notes, plugin install, manual install, reset, and uninstall guidance |
+| `docs/HERMES-SETUP.md` | Public Hermes operator topology | No raw workspace export, credentials, private account names, or local-only operator state |
+| `skills/hermes-imports/SKILL.md` | Sanitized Hermes-to-ECC import workflow | Includes import rules, sanitization checklist, conversion pattern, and output contract |
+| `docs/architecture/cross-harness.md` | Shared substrate model for Claude Code, Codex, OpenCode, Cursor, Gemini, Hermes, and terminal-only use | Names portability boundaries and does not claim unsupported native parity |
+| `docs/architecture/harness-adapter-compliance.md` | Adapter matrix and scorecard | Verified by `npm run harness:adapters -- --check` |
+| `docs/architecture/platform-value-loop.md` | Product integration and full-stack platform thesis | Keeps external product skill packs, gated APIs, case studies, sponsorship, Pro, and consulting loops separate from unsupported GA/control-pane claims |
+| `docs/architecture/observability-readiness.md` | Local operator-readiness gate | Verified by `npm run observability:ready` |
+| `docs/architecture/progress-sync-contract.md` | GitHub, Linear, handoff, roadmap, and work-item sync boundary | Checked by `node scripts/platform-audit.js --json` |
+| `scripts/preview-pack-smoke.js` | Deterministic preview-pack smoke gate | Verified by `npm run preview-pack:smoke` |
+| `scripts/release-approval-gate.js` | Final owner-decision, live-URL, and launch-copy gate | Must return ready true before any additional release/package action, plugin tag, video upload, announcement, or outbound batch |
+| `docs/releases/2.0.0-rc.1/release-notes.md` | GitHub release copy source | Must stay aligned with live GitHub/npm URLs and remaining plugin/video/billing gates before publication |
+| `docs/releases/2.0.0-rc.1/quickstart.md` | Clone-to-first-workflow path | Covers clone, install, verify, first skill, and harness switch |
+| `docs/releases/2.0.0-rc.1/launch-checklist.md` | Operator launch checklist | Must remain approval-gated for plugin, video, billing, and announcement actions |
+| `docs/releases/2.0.0-rc.1/publication-readiness.md` | Release gate | Requires fresh evidence from the exact release commit |
+| `docs/releases/2.0.0-rc.1/publication-evidence-2026-05-15.md` | Current May 15 queue, roadmap, security, supply-chain watch, no-lifecycle CI install hardening, AgentShield #86 evidence-pack provenance, ECC Tools billing-gate, Actions cache purge, and `ecc2` test evidence through PR #1941 | Must be superseded by a final clean-checkout evidence file before real publication |
+| `docs/releases/2.0.0-rc.1/publication-evidence-2026-05-16.md` | Current May 16/17 queue cleanup, recsys skill merge, GateGuard triage, PR #1947 supply-chain protection, AgentShield #87 plugin-cache confidence evidence, AgentShield #88 evidence-pack inspect/readback, AgentShield #89 evidence-pack fleet routing, AgentShield #90 fleet review items, AgentShield #91 policy export, AgentShield #92 policy promotion, ECC-Tools #76 fleet-summary consumption, ECC-Tools #77 hosted finding evidence paths, ECC-Tools #78 harness policy-route linking, dashboard refresh, and combined Node/Rust/release-surface gate evidence through the May 16 mirror | Must still be repeated from a strict clean checkout before real publication |
+| `docs/releases/2.0.0-rc.1/publication-evidence-2026-05-17.md` | May 17 queue-zero state, Japanese localization merge, Dependabot TypeScript and Node type merges, post-merge ja-JP lint repair, Mini Shai-Hulud/TanStack protection recheck, npm audit/signature checks, legacy and Linear progress routing, deterministic preview-pack smoke, operator dashboard refresh, Linear sync, and GitHub CI evidence for `27dc2918` | Superseded by the May 18 evidence snapshot; repeat from a strict clean checkout before real publication |
+| `docs/releases/2.0.0-rc.1/publication-evidence-2026-05-18.md` | May 18 queue-zero state, #1970/#1971/#1972 merge batch, #1978 review/closure, supply-chain recheck, AgentShield evidence mirror, Linear sync, current-head CI/security scan success for `4470e2e6`, and ITO-46 naming/plugin publication closure | Superseded by the May 19 ECC identity, video, and growth evidence snapshot |
+| `docs/releases/2.0.0-rc.1/publication-evidence-2026-05-19.md` | Current May 19/20 evidence for canonical ECC identity, release video suite, partner/sponsor/talk outreach pack, owner approval packet, release approval gate, May 20 operator dashboard, preview-pack smoke digest `eebb8a66c33e`, 2568-test local suite, PR #1998 visual QA CI success, PR #1999 dashboard evidence CI success, PR #2000 suite-count evidence success, PR #2001 owner approval packet CI success, PR #2002 owner-approval dashboard gate CI success, PR #2004 Linear readiness evidence sync CI success, PR #2008 supply-chain evidence gate CI success, post-PR #2006 main CI success, PR #2009 project-registry hygiene CI success, post-PR #2009 main CI success, post-PR #2011 GateGuard CI success, post-PR #2013 release-approval-gate CI success, PR #2017/#2018 AgentShield evidence sync, ECC-Tools #79 billing-announcement redaction hardening, ECC-Tools #80-#93 runtime-receipt, AgentShield approval-ID, Linear sync, remediation sync, hosted observability event/status/depth-plan/API readback, Marketplace Pro selected-target readback, selected-target announcement gate, env-file billing operator path, non-breaking operator bearer path, live `announcementGateReady: true`, AgentShield #94 Zed/VS Code adapter coverage, AgentShield #95 Dependabot alert closure, JARVIS #15/#16 queue/deploy repair, ECC #2019/#2020 Marketplace Pro gate sync, and the May 19/20 Linear sync comments | Current strongest readiness snapshot; must still be repeated from a strict clean checkout before real publication |
+| `docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-17.md` | Previous prompt-to-artifact operator dashboard | Superseded by the May 18 generated dashboard |
+| `docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-18.md` | Previous prompt-to-artifact operator dashboard | Superseded by the May 19 generated dashboard |
+| `docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-19.md` | Previous prompt-to-artifact operator dashboard | Superseded by the May 20 generated dashboard |
+| `docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-20.md` | Current prompt-to-artifact operator dashboard | Shows PR/issue/discussion/platform/supply-chain gates current and adds the current `$1,728/mo` to `$10,000/mo` hypergrowth, video owner-approval, Linear release-gate sync, selected-target billing gate, operator bearer path, live billing gate pass, and outbound-pack operating lanes |
+| `docs/releases/2.0.0-rc.1/owner-approval-packet-2026-05-19.md` | Final human decision sheet for release, package, plugin, video, billing, social, and outbound approvals | Must be reviewed by the owner before any publication or outbound action |
+| `docs/releases/2.0.0-rc.1/release-url-ledger-2026-05-19.md` | Live URL and approval-gated URL ledger for release copy | Must be regenerated from the final release commit before public announcements |
+| `docs/releases/2.0.0-rc.1/video-suite-production.md` | Release video production manifest | Gates local media inventory, rough primary render, captions, timeline, self-eval, and no-private-path publication rules |
+| `docs/releases/2.0.0-rc.1/partner-sponsor-talks-pack.md` | Partner, sponsor, consulting, conference, podcast, and discussion copy | Must stay approval-gated and avoid live billing, release, package, or plugin claims without evidence |
+| `docs/releases/2.0.0-rc.1/naming-and-publication-matrix.md` | Naming, slug, and publication-path decision record | Keeps `ECC`, npm `ecc-universal`, and plugin slug `ecc` for rc.1 |
+| `docs/releases/2.0.0-rc.1/release-name-plugin-publication-checklist-2026-05-18.md` | Release name, package, Claude plugin, Codex plugin, and publication-order checklist | Freezes rc.1 identity and requires final commit evidence before plugin, billing, or announcement actions |
+| `docs/releases/2.0.0-rc.1/x-thread.md` | X launch draft | Must use live GitHub/npm URLs and keep remaining plugin/video/billing URLs gated |
+| `docs/releases/2.0.0-rc.1/linkedin-post.md` | LinkedIn launch draft | Must use live GitHub/npm URLs and keep remaining plugin/video/billing URLs gated |
+| `docs/releases/2.0.0-rc.1/article-outline.md` | Longform launch outline | Must stay release-candidate framed until GA evidence exists |
+| `docs/releases/2.0.0-rc.1/telegram-handoff.md` | Internal/shareable handoff copy | Must not include private workspace or credential details |
+| `docs/releases/2.0.0-rc.1/demo-prompts.md` | Demo prompts and proof-of-work prompts | Must keep private Hermes workflows abstracted into public examples |
+| `docs/releases/2.0.0-rc.1/ito-prediction-market-skill-pack.md` | Public Itô skill-pack distribution note | Keeps Itô API access gated, non-advisory, and separate from ECC Tools billing |
+
+## Itô Skill Pack Boundary
+
+The general product-integration contract is recorded in
+`docs/architecture/platform-value-loop.md`. The Itô pack is the first worked
+example: useful public workflows, separate gated API access, and sanitized
+operator patterns feeding back into ECC without merging business ownership.
+
+The preview pack includes six public teaser skills for prediction-market and
+Itô-adjacent workflows:
+
+- `skills/ito-market-intelligence/SKILL.md`
+- `skills/ito-basket-compare/SKILL.md`
+- `skills/ito-trade-planner/SKILL.md`
+- `skills/ito-data-atlas-agent/SKILL.md`
+- `skills/prediction-market-oracle-research/SKILL.md`
+- `skills/prediction-market-risk-review/SKILL.md`
+
+They are research, comparison, planning, and risk-review skills. They do not
+place trades, do not provide investment advice, and do not merge ECC Tools with
+Itô. Any Itô-backed data call requires explicit gated API access through
+`ITO_API_KEY`.
+
+## Hermes Skill Boundary
+
+The preview pack includes one public Hermes-specialized skill:
+
+- `skills/hermes-imports/SKILL.md`
+
+That is intentional for rc.1. The skill is a sanitization and conversion
+workflow, not a dump of private Hermes automations. Additional Hermes-generated
+skills should enter ECC only after they pass the same rules:
+
+- no raw workspace exports;
+- no live account names, client data, finance data, CRM data, health data, or
+  private contact graph;
+- provider requirements described by capability, not by secret value;
+- repo-relative examples instead of local absolute paths;
+- tests or docs proving the workflow is useful without private state.
+
+## Reference-Inspired Adapter Direction
+
+The preview pack uses outside systems as design pressure, not as copy targets:
+
+| Reference pressure | ECC preview-pack interpretation |
+| --- | --- |
+| Claude Code | Native plugin, skills, commands, hooks, MCP conventions, and statusline-oriented workflows |
+| Codex | Instruction-backed plugin metadata, shared skills, MCP reference config, and explicit hook-parity caveats |
+| OpenCode | Adapter-backed package/plugin surface with shared hook logic at the edge |
+| Zed-adjacent tools | Instruction-backed portability until a verified native adapter exists |
+| dmux | Session/runtime orchestration signals and handoff exports, not a replacement for repo validation |
+| Orca, Superset, Ghast | Reference-only pressure for worktree lifecycle, session grouping, notifications, and workspace presets |
+| Hermes Agent, meta-harness, autocontext-style systems | Evaluation, memory, and context-routing pressure routed through public artifacts, verifier outputs, and the evaluator/RAG prototype |
+
+## Final Verification Commands
+
+Run these from the exact release commit before publication:
+
+```bash
+git status --short --branch
+node scripts/platform-audit.js --json
+npm run preview-pack:smoke
+npm run release:approval-gate -- --format json
+npm run release:video-suite -- --format json
+npm run harness:adapters -- --check
+npm run harness:audit -- --format json
+npm run observability:ready
+npm run security:ioc-scan
+npm audit --audit-level=moderate
+npm audit signatures
+node tests/docs/ecc2-release-surface.test.js
+node tests/run-all.js
+cd ecc2 && cargo test
+```
+
+## Publication Blockers
+
+The preview pack is assembled, and the first release/package surfaces are now
+live. Full publication is still blocked until these live surfaces and decisions
+are recorded in a final evidence file:
+
+- final release URL ledger regenerated from the intended release commit;
+- `npm run release:approval-gate -- --format json` returning ready true after
+  owner approvals and live URL readbacks are recorded;
+- final release name/plugin publication checklist rerun from the intended
+  release commit;
+- GitHub prerelease `v2.0.0-rc.1` live readback;
+- npm `ecc-universal@2.0.0-rc.1` on the `next` dist-tag live readback;
+- Claude plugin tag / marketplace propagation for `ecc@ecc`;
+- Codex repo-marketplace distribution evidence plus official Plugin Directory
+  availability status;
+- final announcement URLs in X, LinkedIn, GitHub release, and longform copy;
+- ECC Tools billing/product readiness evidence remains fresh: the May 20
+  selected-target KV readback and live announcement gate passed through the
+  operator bearer path. Repeat the billing readback and gate immediately before
+  any native-payments announcement copy is published.
+
+## Result
+
+The rc.1 preview pack is ready for a final clean-checkout release gate, but not
+for full public publication without the remaining approval-gated release, package, plugin, and
+announcement steps above. GitHub and npm are now recorded; plugin, video,
+billing, and outbound approvals remain open.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/publication-evidence-2026-05-12.md

@@ -0,0 +1,103 @@
+# ECC v2.0.0-rc.1 Publication Evidence — 2026-05-12
+
+This is dry-run release evidence only. It does not create a GitHub release, npm
+publication, plugin tag, marketplace submission, or announcement post.
+
+## Source Commit
+
+| Field | Evidence |
+| --- | --- |
+| Upstream main base | `0598af70a51346bae34d987b9bed143386055967` |
+| Evidence branch | `codex/release-publication-evidence` |
+| Evidence scope | Working tree with this branch's package hygiene and release-doc updates |
+| Git remote | `https://github.com/affaan-m/everything-claude-code.git` |
+| Local status caveat | Working tree had the unrelated untracked `docs/drafts/` directory |
+
+The actual release operator should repeat these checks from the final release
+commit with a clean checkout before publishing.
+
+## Registry And Release State
+
+| Surface | Command | Result |
+| --- | --- | --- |
+| GitHub prerelease | `gh release view v2.0.0-rc.1 --repo affaan-m/everything-claude-code --json tagName,url,isPrerelease` | `release not found` |
+| npm dist-tags | `npm view ecc-universal dist-tags --json` | `{ "latest": "1.10.0" }` |
+| npm package metadata | `node -p "require('./package.json').name + '@' + require('./package.json').version"` | `ecc-universal@2.0.0-rc.1` |
+| Product identity | `rg -n "Everything Claude Code" README.md CHANGELOG.md docs/releases/2.0.0-rc.1` | Present in README and rc.1 release docs |
+
+## npm Dry Run
+
+The first pack pass exposed local Python bytecode cache files in the tarball
+because broad package `files` entries included untracked local `__pycache__`
+paths. This branch adds explicit package-file exclusions and a regression test
+so `npm pack` fails if Python bytecode appears in the package surface.
+
+| Command | Result |
+| --- | --- |
+| `node tests/scripts/npm-publish-surface.test.js` | Passed `2/2`; includes Python bytecode exclusion assertion |
+| `npm pack --dry-run --json` | `ecc-universal-2.0.0-rc.1.tgz`; `entryCount: 965`; `size: 1565968`; `unpackedSize: 4934637`; `hasBytecode: false` |
+| `npm publish --tag next --dry-run --json` | Dry-run target is npm registry with `tag next`; `entryCount: 965`; `hasBytecode: false` |
+
+Temporary install smoke:
+
+| Command | Result |
+| --- | --- |
+| `npm pack --pack-destination /tmp/ecc-publication-smoke-dd9ud5 --json` | Created `ecc-universal-2.0.0-rc.1.tgz` for local install smoke |
+| `npm install --prefix /tmp/ecc-publication-smoke-dd9ud5 /tmp/ecc-publication-smoke-dd9ud5/ecc-universal-2.0.0-rc.1.tgz` | Added 8 packages |
+| `node /tmp/ecc-publication-smoke-dd9ud5/node_modules/ecc-universal/scripts/ecc.js --help` | Printed ECC selective-install CLI help |
+| `node /tmp/ecc-publication-smoke-dd9ud5/node_modules/ecc-universal/scripts/catalog.js profiles --json` | Returned the 6 install profiles: `minimal`, `core`, `developer`, `security`, `research`, `full` |
+| `find /tmp/ecc-publication-smoke-dd9ud5/node_modules/ecc-universal -path '*__pycache__*' -o -name '*.pyc' -o -name '*.pyo' -o -name '*.pyd'` | No output |
+
+## Plugin And Harness Evidence
+
+| Surface | Command | Result |
+| --- | --- | --- |
+| Claude plugin manifest | `claude plugin validate .claude-plugin/plugin.json` | Passed |
+| Claude plugin tag preflight | `claude plugin tag .claude-plugin --dry-run` | Blocked by unrelated untracked `docs/drafts/` |
+| Claude plugin tag forced dry-run | `claude plugin tag .claude-plugin --dry-run --force` | Would create `ecc--v2.0.0-rc.1` at HEAD; do not use `--force` for real release unless maintainer decides |
+| Codex marketplace CLI | `codex plugin marketplace --help` and subcommand help | Supports `add`, `upgrade`, and `remove`; `add` supports repo and local marketplace roots |
+| OpenCode package | `npm run build:opencode` | Passed |
+| Claude hook/plugin route | `node tests/hooks/hooks.test.js` | Passed `236/236` |
+| Codex release surface | `node tests/docs/ecc2-release-surface.test.js` | Passed `18/18` |
+| Agent/catalog metadata | `node tests/scripts/catalog.test.js` | Passed `7/7` |
+| Observability gate | `npm run observability:ready` | Passed `16/16` |
+
+## Clean-Checkout Claude Plugin Smoke
+
+This follow-up pass used a detached clean worktree at
+`/tmp/ecc-clean-plugin-evidence` from commit
+`bfacf37715b39655cbc2c48f12f2a35c67cb0253`. It used an isolated temp home
+(`HOME=/tmp/ecc-clean-plugin-home`) and a temp local project
+(`/tmp/ecc-plugin-install-smoke`), so it did not write to the user's real Claude
+plugin config.
+
+| Command | Result |
+| --- | --- |
+| `git -C /tmp/ecc-clean-plugin-evidence status --short --branch` | `## HEAD (no branch)` with no dirty or untracked files |
+| `claude plugin validate .claude-plugin/plugin.json` | Passed |
+| `claude plugin validate .claude-plugin/marketplace.json` | Passed |
+| `claude plugin tag .claude-plugin --dry-run` | Passed without `--force`; would create `ecc--v2.0.0-rc.1` at HEAD and push `refs/tags/ecc--v2.0.0-rc.1` |
+| `claude plugin marketplace add /tmp/ecc-clean-plugin-evidence --scope local` with temp `HOME` | Added marketplace `ecc` in local settings |
+| `claude plugin list --available --json` with temp `HOME` | Listed `ecc@ecc`, version `2.0.0-rc.1`, source `./` |
+| `claude plugin install ecc@ecc --scope local` with temp `HOME` | Installed `ecc@ecc` in local scope |
+| `claude plugin list --json` with temp `HOME` | Listed `ecc@ecc`, version `2.0.0-rc.1`, enabled, local scope, install path under `/tmp/ecc-clean-plugin-home/.claude/plugins/cache/ecc/ecc/2.0.0-rc.1` |
+| `claude plugin uninstall ecc@ecc --scope local` with temp `HOME` | Uninstalled successfully; final plugin list was `[]` |
+
+## Announcement Placeholder Check
+
+The forbidden-placeholder scan only returned the publication-readiness checklist
+lines that name those forbidden placeholders. No launch-pack placeholder
+instances were found.
+
+## Remaining Blockers
+
+- Create or verify GitHub prerelease `v2.0.0-rc.1`.
+- Publish `ecc-universal@2.0.0-rc.1` with npm dist-tag `next`.
+- Create and push the Claude plugin tag only after explicit approval. The clean
+  checkout dry run and temp install smoke now pass.
+- Confirm the live Claude/Codex/OpenCode marketplace submission path or record
+  the manual submission owner and status.
+- Verify ECC Tools billing/App/Marketplace claims before using them in launch
+  copy.
+- Refresh announcement copy with live URLs after release and package/plugin
+  URLs exist.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/publication-evidence-2026-05-13-post-hardening.md

@@ -0,0 +1,98 @@
+# ECC v2.0.0-rc.1 Publication Evidence - 2026-05-13 Post-Hardening
+
+This is release-readiness evidence only. It does not create a GitHub release,
+npm publication, plugin tag, marketplace submission, or announcement post.
+
+## Source Commit
+
+| Field | Evidence |
+| --- | --- |
+| Upstream main base | `209abd403b7eaa968c6d4fa67be82e04b55706d6` |
+| Evidence branch | `docs/post-hardening-release-evidence-20260513` |
+| Evidence scope | Current `main` after PR #1850 and PR #1851 |
+| Git remote | `https://github.com/affaan-m/everything-claude-code.git` |
+| Local status caveat | Working tree had the unrelated untracked `docs/drafts/` directory |
+
+The actual release operator should repeat these checks from the final release
+commit with a clean checkout before publishing.
+
+## Queue And Release State
+
+| Surface | Command | Result |
+| --- | --- | --- |
+| GitHub PRs and issues | `gh pr list` / `gh issue list` across trunk, AgentShield, and JARVIS | 0 open PRs and 0 open issues on accessible `affaan-m` repos |
+| Trunk discussions | GraphQL discussion count for `affaan-m/everything-claude-code` | 0 open discussions |
+| Dependabot alerts | Dependabot alert API for trunk, AgentShield, and JARVIS | 0 open alerts |
+| Release state | `gh release view v2.0.0-rc.1` | Still not created; release remains approval-gated |
+
+ECC-Tools organization repo counts were not rechecked through the current
+GraphQL token in this pass because the token cannot resolve those org repos.
+The prior post-#42 local checkout handoff recorded both ECC-Tools repos at
+0 open PRs and 0 open issues.
+
+## Hardening Landed Since Previous Evidence
+
+| PR | Merge commit | Evidence |
+| --- | --- | --- |
+| #1850 | `248673271455e9dc85b8add2a6ab76107b718639` | Removed `Bash` tool access from read-only analyzer agents and zh-CN copies; AgentShield high findings on that surface dropped 21 -> 18 with no new high findings |
+| #1851 | `209abd403b7eaa968c6d4fa67be82e04b55706d6` | Disabled `actions/checkout` credential persistence in write-permission workflows and added a workflow-security validator rule to keep that guard in place |
+
+## Required Command Evidence
+
+| Evidence | Command | Result |
+| --- | --- | --- |
+| Harness audit | `npm run harness:audit -- --format json` | `overall_score: 70`, `max_score: 70`, no top actions |
+| Adapter scorecard | `npm run harness:adapters -- --check` | `Harness Adapter Compliance: PASS`; 11 adapters |
+| Observability readiness | `npm run observability:ready -- --format json` | `overall_score: 21`, `max_score: 21`, `ready: true`, no top actions; includes Release Safety 3/3 |
+| Workflow security validator | `node scripts/ci/validate-workflow-security.js` | Validated 7 workflow files |
+| Workflow validator tests | `node tests/ci/validate-workflow-security.test.js` | Passed 14/14 |
+| Release surface | `node tests/docs/ecc2-release-surface.test.js` | Passed 18/18 |
+| Package surface | `node tests/scripts/npm-publish-surface.test.js` | Passed 2/2 |
+| Root suite | `node tests/run-all.js` | Passed 2381/2381, 0 failed |
+| Markdown lint | `npx markdownlint-cli '**/*.md' --ignore node_modules --ignore docs/drafts` | Passed |
+| Rust surface | `cd ecc2 && cargo test` | Passed 462/462; warnings only for unused functions/fields |
+| GitGuardian Security Checks | GitHub check on post-hardening security PRs | Passed before merge |
+
+## Supply-Chain Evidence
+
+| Surface | Command or check | Result |
+| --- | --- | --- |
+| Local npm vulnerability audit | `npm audit --json` | 0 vulnerabilities |
+| Local npm signature audit | `npm audit signatures` | 241 verified registry signatures and 30 verified attestations |
+| Rust advisory audit | `cd ecc2 && cargo audit -q` | Passed silently |
+| TanStack / Mini Shai-Hulud IOC check | Grep for affected package namespaces, payload filenames, and known commit marker | No runtime or lockfile dependency on affected packages; no worm IOC matches |
+| GitGuardian Security Checks | GitHub check on post-hardening security PRs | Passed before merge |
+
+## External Advisory Mapping
+
+The May 2026 TanStack incident maps to ECC release risk through three workflow
+classes:
+
+- `pull_request_target` workflows that execute or checkout untrusted PR code;
+- shared dependency caches crossing fork, base, and release workflow trust
+  boundaries;
+- release jobs with writable tokens or OIDC tokens exposed to subsequent
+  process execution.
+
+ECC's current guardrails cover those classes through:
+
+- rejection of untrusted checkout refs in `workflow_run` and
+  `pull_request_target` workflows;
+- rejection of shared caches in `pull_request_target` and `id-token: write`
+  workflows;
+- mandatory `npm audit signatures` when workflows run `npm audit`;
+- mandatory `npm ci --ignore-scripts` in workflows with write permissions;
+- mandatory `persist-credentials: false` on `actions/checkout` in workflows
+  with write permissions.
+
+## Blockers Still Requiring Approval Or External Action
+
+- Create or verify GitHub prerelease `v2.0.0-rc.1`.
+- Publish `ecc-universal@2.0.0-rc.1` with npm dist-tag `next`.
+- Create and push the Claude plugin tag only after explicit approval.
+- Confirm the live Claude/Codex/OpenCode marketplace submission path or record
+  the manual submission owner and status.
+- Verify ECC Tools billing/App/Marketplace claims before using them in launch
+  copy.
+- Refresh announcement copy with live URLs after release and package/plugin
+  URLs exist.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/publication-evidence-2026-05-13.md

@@ -0,0 +1,60 @@
+# ECC v2.0.0-rc.1 Publication Evidence - 2026-05-13
+
+This is release-readiness evidence only. It does not create a GitHub release,
+npm publication, plugin tag, marketplace submission, or announcement post.
+
+## Source Commit
+
+| Field | Evidence |
+| --- | --- |
+| Upstream main base | `797f283036904128bb1b348ae62019eb9f08cf39` |
+| Evidence branch | `docs/release-readiness-20260513` |
+| Evidence scope | Current `main` after PR #1846 plus markdownlint-only zh-CN CLAUDE list-marker normalization |
+| Git remote | `https://github.com/affaan-m/everything-claude-code.git` |
+| Local status caveat | Working tree had the unrelated untracked `docs/drafts/` directory |
+
+The actual release operator should repeat these checks from the final release
+commit with a clean checkout before publishing.
+
+## Queue And Release State
+
+| Surface | Command | Result |
+| --- | --- | --- |
+| GitHub PRs and issues | `gh pr list` / `gh issue list` across trunk, AgentShield, JARVIS, ECC-Tools, ECC-website | 0 open PRs and 0 open issues across tracked repos |
+| Trunk discussions | GraphQL discussion sweep for `affaan-m/everything-claude-code` | Latest 100 discussions were closed; no open discussion backlog found |
+| npm audit signature gate | PR #1846 | Merged as `797f283`; workflows that run `npm audit` now need `npm audit signatures` |
+
+## Required Command Evidence
+
+| Evidence | Command | Result |
+| --- | --- | --- |
+| Harness audit | `npm run harness:audit -- --format json` | `overall_score: 70`, `max_score: 70`, no top actions |
+| Adapter scorecard | `npm run harness:adapters -- --check` | `Harness Adapter Compliance: PASS`; 11 adapters |
+| Observability readiness | `npm run observability:ready -- --format json` | `overall_score: 16`, `max_score: 16`, `ready: true`, no top actions |
+| Root suite | `node tests/run-all.js` | `2376` passed, `0` failed |
+| Markdown lint | `npx markdownlint-cli '**/*.md' --ignore node_modules` | Passed after normalizing two zh-CN CLAUDE docs from asterisk bullets to dash bullets |
+| Package surface | `node tests/scripts/npm-publish-surface.test.js` | Passed `2/2`; package surface still excludes Python bytecode/cache artifacts |
+| Release surface | `node tests/docs/ecc2-release-surface.test.js` | Passed `18/18` |
+| Rust surface | `cd ecc2 && cargo test` | Passed `462/462`; warnings only for unused functions/fields |
+
+## Security Gate Evidence
+
+| Surface | Command or check | Result |
+| --- | --- | --- |
+| Local npm signature audit | `npm audit signatures` before PR #1846 | 241 verified registry signatures and 30 verified attestations |
+| Local npm vulnerability audit | `npm audit --audit-level=high` before PR #1846 | 0 vulnerabilities |
+| Workflow security validator | `node scripts/ci/validate-workflow-security.js` | Validated 7 workflow files |
+| Workflow validator tests | `node tests/ci/validate-workflow-security.test.js` | Passed `11/11`, including the new signature-gate cases |
+| GitHub CI for #1846 | Current-head PR checks | Full OS/package-manager matrix passed, including `windows-latest / Node 18.x / pnpm` |
+
+## Blockers Still Requiring Approval Or External Action
+
+- Create or verify GitHub prerelease `v2.0.0-rc.1`.
+- Publish `ecc-universal@2.0.0-rc.1` with npm dist-tag `next`.
+- Create and push the Claude plugin tag only after explicit approval.
+- Confirm the live Claude/Codex/OpenCode marketplace submission path or record
+  the manual submission owner and status.
+- Verify ECC Tools billing/App/Marketplace claims before using them in launch
+  copy.
+- Refresh announcement copy with live URLs after release and package/plugin
+  URLs exist.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/publication-evidence-2026-05-15.md

@@ -0,0 +1,187 @@
+# ECC v2.0.0-rc.1 Publication Evidence - 2026-05-15
+
+This is release-readiness evidence only. It does not create a GitHub release,
+npm publication, plugin tag, marketplace submission, or announcement post.
+
+## Source Commit
+
+| Field | Evidence |
+| --- | --- |
+| Upstream main base | `1949d75e18e59a37de269d88b188fc701f5cf122` |
+| Evidence branch | `codex/rc1-agentshield-86-evidence` |
+| Evidence scope | Current `main` after PR #1932, #1933, #1934, #1935, and #1936; AgentShield #86; and ECC-Tools #75 |
+| Git remote | `https://github.com/affaan-m/everything-claude-code.git` |
+| Local status caveat | Working tree had the unrelated untracked `docs/drafts/` directory before this docs refresh |
+
+The actual release operator should repeat all publish-facing checks from the
+final release commit with a clean checkout before publishing.
+
+## Queue And Discussion State
+
+| Surface | Command | Result |
+| --- | --- | --- |
+| Trunk PRs/issues | `gh pr list` and `gh issue list` for `affaan-m/everything-claude-code` | 0 open PRs, 0 open issues |
+| AgentShield PRs/issues | `gh pr list` and `gh issue list` for `affaan-m/agentshield` | 0 open PRs, 0 open issues |
+| JARVIS PRs/issues | `gh pr list` and `gh issue list` for `affaan-m/JARVIS` | 0 open PRs, 0 open issues |
+| ECC Tools PRs/issues | `env -u GITHUB_TOKEN gh pr list` and `env -u GITHUB_TOKEN gh issue list` for `ECC-Tools/ECC-Tools` | 0 open PRs, 0 open issues |
+| ECC website PRs/issues | `env -u GITHUB_TOKEN gh pr list` and `env -u GITHUB_TOKEN gh issue list` for `ECC-Tools/ECC-website` | 0 open PRs, 0 open issues |
+| Trunk discussions | GraphQL discussion count and maintainer-touch sweep | 58 total discussions; 0 without maintainer touch after May 15 maintainer comments |
+| Other repo discussions | GraphQL discussion count for AgentShield, JARVIS, ECC Tools, and ECC website | Discussions disabled or 0 total |
+| Platform audit | `node scripts/platform-audit.js --json --allow-untracked docs/drafts/` | Ready; open PRs 0/20, open issues 0/20, discussions needing maintainer touch 0, conflicting open PRs 0, blocking dirty files 0 |
+
+The ECC Tools organization is reachable with the configured GitHub host
+credential. In this shell, the exported `GITHUB_TOKEN` overrides that credential
+and causes false 404/403 failures for `ECC-Tools/*`. Use `env -u GITHUB_TOKEN`
+for ECC Tools verification commands until that environment override is cleaned
+up.
+
+## Linear Roadmap State
+
+The detailed execution roadmap now lives in Linear project:
+
+<https://linear.app/itomarkets/project/ecc-platform-roadmap-52b328ee03e1>
+
+The project contains 16 issue-level lanes and 5 milestones:
+
+| Milestone | Issues |
+| --- | --- |
+| Security and Access Baseline | `ITO-44`, `ITO-57`, `ITO-58` |
+| ECC 2.0 Preview and Publication | `ITO-45`, `ITO-46`, `ITO-47`, `ITO-56` |
+| AgentShield Enterprise Iteration | `ITO-48`, `ITO-49` |
+| ECC Tools Next-Level Platform | `ITO-50`, `ITO-51`, `ITO-52`, `ITO-53`, `ITO-54`, `ITO-59` |
+| Legacy Audit and Salvage | `ITO-55` |
+
+Project documents added in Linear:
+
+- Roadmap Index and Current Execution Baseline
+- Status Update 2026-05-15
+- GitHub Queue Snapshot 2026-05-15
+- Completion Audit Snapshot 2026-05-15
+- Discussion Queue Evidence 2026-05-15
+- ECC-Tools Access Evidence 2026-05-15
+
+## Supply-Chain Evidence
+
+| Surface | Evidence |
+| --- | --- |
+| PR #1921 | Merged supply-chain IOC expansion for Mini Shai-Hulud/TanStack follow-up |
+| Node IPC follow-up / PR #1924 | Added May 14 `node-ipc` malicious-version, hash, DNS, and runtime IOC coverage |
+| PR #1926 | Added `platform:audit` and `security-ioc-scan` command surfaces plus release workflow IOC gates |
+| PR #1932 | Added `scripts/platform-audit.js` JSON/Markdown/file-output modes so queue, discussion, roadmap, and release evidence can be captured as a durable artifact instead of terminal-only output |
+| PR #1933 | Expanded home-scan IOC coverage to Claude `settings.local.json`, `.claude/hooks/hooks.json`, and user-level VS Code / Code Insiders `tasks.json` across macOS, Linux, and Windows |
+| PR #1934 | Switched ordinary CI dependency caches to restore-only `actions/cache/restore` usage so test jobs do not save mutable dependency state back into shared caches |
+| PR #1935 | Stabilized `ecc2` current-directory-mutating tests with a test-only serialized current-dir guard, preserving the Rust release-surface gate under parallel test execution |
+| PR #1940 | Added `.github/workflows/supply-chain-watch.yml`, scheduled every 6 hours, so the TanStack/Mini Shai-Hulud/node-ipc IOC scan and npm signature/audit checks produce a durable `supply-chain-ioc-report.json` artifact |
+| PR #1941 | Removed GitHub Actions dependency cache use from CI test workflows, disabled package-manager lifecycle scripts for npm/pnpm/Yarn/Bun installs, purged existing Actions caches, and added validator tests that reject unsafe install/cache patterns |
+| AgentShield PR #83 | Merged Mini Shai-Hulud IOC coverage for TanStack, Mistral, OpenSearch, Guardrails, UiPath, Squawk, Claude Code / VS Code persistence, and dead-man switch artifacts |
+| AgentShield PR #84 | Merged the broader Mini Shai-Hulud full-campaign affected-package table, including additional `@cap-js`, `@draftlab`, `@tallyui`, `intercom-client`, `lightning`, and related package/version IOCs |
+| AgentShield PR #85 | Added GitHub Action supply-chain verification, gating, and evidence packs so AgentShield's enterprise scanner release path has a verified registry-signature surface |
+| AgentShield PR #86 | Added `ci-context.json` to AgentShield evidence packs with whitelisted GitHub Actions workflow, commit, run, and runtime provenance while keeping arbitrary environment variables and tokens out of the bundle |
+| ECC-Tools PR #75 | Tightened the native GitHub payments announcement gate so public billing claims remain blocked until live Marketplace-managed test-account readback is ready |
+| Trunk merge commits | `f04702bdac132662c8496e817bcd850c86e2b854`, `ee85e1482e3d6322ddb2706392ea0fc97469bd26`, `13585f1092c92fa3f20ffe0d756e40c5720b0de5`, `553d507ea63bc252e815a924c0d2baea961351a1`, `c0bac4d6ced7f78a5464c6e3fd8cfbb43515a9d5`, `c2c54e7c0b84a213848b9ab3dfeb3ae16fb9844d`, `6b8a49a6eed11cc7df19d8b1f2add085b37cf466`, `1949d75e18e59a37de269d88b188fc701f5cf122`, `6951b8d5d29d13cac6b89b461104ad03838553de`, `f7035b5644ffc857879b71c39353b2141f17c3f0` |
+| AgentShield merge commits | `f899b27ba3fa60ec7e0dca41cc2dadcb1a1fb75d`, `d1aa5313afd915d0b7296e57aabaeb979b1ea93b`, `908d8f3a52a6a65b21e737339b56906603eb1345`, `69a5e25b675b77666d0c96abc22639a5ba883403` |
+| ECC-Tools merge commits | `6d00d67043e92cadc80f160bfe947115bfef33b1` |
+| Local IOC tests | `node tests/ci/scan-supply-chain-iocs.test.js` passed 15/15 |
+| Unicode safety | `node scripts/ci/check-unicode-safety.js` passed |
+| IOC scan | `node scripts/ci/scan-supply-chain-iocs.js --root <ECC-workspace> --home` passed with 229 files inspected after the no-lifecycle install refresh |
+| npm registry verification | `npm audit signatures` verified 241 registry signatures and 30 attestations; `npm audit --audit-level=high` found 0 vulnerabilities |
+| Actions cache purge | `gh cache delete --all --succeed-on-no-caches` completed and `gh cache list --limit 20` returned no caches |
+| Rust release-surface gate | `cd ecc2 && cargo test` passed 462/462 with the existing 14 dead-code/unused warnings |
+| Root suite | `node tests/run-all.js` passed 2442/2442, 0 failed |
+| Repo sweeps | Targeted persistence path checks found no active `gh-token-monitor`, `pgsql-monitor`, `transformers.pyz`, or `pgmonitor.py` artifacts |
+
+The May 15 IOC expansion added coverage for OpenSearch/Mistral/Guardrails/
+UiPath/Squawk-style campaign variants, `opensearch_init.js`, `vite_setup.mjs`,
+dead-drop/session protocol strings, and AI-tooling persistence surfaces without
+committing full high-entropy indicators that trip secret scanners.
+The May 15 node-ipc follow-up blocks `node-ipc@9.1.6`, `9.2.3`, `10.1.1`,
+`10.1.2`, `11.0.0`, `11.1.0`, and `12.0.1`, plus the `node-ipc.cjs` payload
+hash, malicious tarball hashes, DNS exfil domains, and runtime markers reported
+by Socket.
+AgentShield PR #83 adds the matching scanner-side enterprise coverage:
+version-pinned package detections, `.claude` / `.vscode` automation-surface
+discovery, `gh-token-monitor` LaunchAgent/systemd/local-bin artifact detection,
+network/payload IOCs, built action/CLI bundles, 1758/1758 local tests, and
+green GitHub Actions verification before merge.
+AgentShield PR #84 closes the later full-campaign package-table gap by adding
+the extra affected npm package scopes and unscoped packages reported in the
+current Wiz table, rebuilding `dist/action.js` and `dist/index.js`, and passing
+1758/1758 local tests plus the full AgentShield GitHub Actions matrix before
+merge.
+AgentShield PR #85 and trunk PRs #1934, #1940, and #1941 extend the response
+from IOC detection into release-path hardening: AgentShield now records
+registry-signature evidence for its action surface, trunk has a scheduled IOC
+watch workflow, and trunk CI no longer uses dependency caches or package-manager
+lifecycle scripts in the test install matrix during active supply-chain
+hardening.
+AgentShield PR #86 completes the next evidence-pack provenance slice:
+`agentshield scan --evidence-pack <dir>` now writes `ci-context.json`, includes
+that artifact in the signed bundle digest, documents it in the bundle README,
+and verifies that token-bearing environment variables such as `GITHUB_TOKEN`
+are not copied into long-lived security-review artifacts. The PR passed local
+build, typecheck, lint, 1764/1764 tests, and the full GitHub Actions matrix
+across Node 18, 20, and 22 before merge.
+PR #1933 closes the practical workstation persistence gap for the documented
+Claude Code and VS Code automation paths, including user-level config files that
+survive package uninstall.
+
+## Preview Pack State
+
+`preview-pack-manifest.md` now assembles the rc.1 preview-pack boundary:
+
+- release notes, quickstart, launch checklist, publication readiness, naming
+  matrix, and May 15 evidence;
+- `docs/HERMES-SETUP.md` and `skills/hermes-imports/SKILL.md` as the public
+  Hermes-specialized surface;
+- cross-harness, harness-adapter, observability, and progress-sync docs;
+- X, LinkedIn, article, Telegram, and demo collateral that must receive final
+  live URLs after release/package/plugin publication;
+- explicit blockers for GitHub release, npm `next` publish, Claude plugin,
+  Codex plugin, ECC Tools billing/product-readiness, and announcements.
+
+The preview pack is assembled for final clean-checkout gating, but it is still
+not a publication action.
+
+## Codex Marketplace Evidence
+
+OpenAI's current Codex plugin docs now distinguish repo/personal marketplace
+distribution from the official Plugin Directory. Repo marketplaces live at
+`.agents/plugins/marketplace.json`; `codex plugin marketplace add <source>`
+can add GitHub shorthand, Git URLs, SSH URLs, or local marketplace roots.
+Official Plugin Directory publishing and self-serve management are documented
+as coming soon:
+
+- <https://developers.openai.com/codex/plugins/build#add-a-marketplace-from-the-cli>
+- <https://developers.openai.com/codex/plugins/build#how-codex-uses-marketplaces>
+- <https://developers.openai.com/codex/plugins/build#publish-official-public-plugins>
+
+| Surface | Evidence |
+| --- | --- |
+| CLI shape | `codex plugin marketplace add --help` supports GitHub shorthand, Git URLs, SSH URLs, local marketplace roots, `--ref`, and Git-only `--sparse` |
+| Repo marketplace | `.agents/plugins/marketplace.json` exposes `ecc@2.0.0-rc.1` with `source.path: "./"` from the marketplace root |
+| Local add smoke | `HOME="$(mktemp -d)" codex plugin marketplace add <local-checkout>` added marketplace `ecc` and recorded the installed marketplace root as `<local-checkout>` without touching the real Codex config |
+| README alignment | `.codex-plugin/README.md` now uses `codex plugin marketplace add`, not the stale `codex plugin install` command |
+| Public-directory status | The supported Codex distribution path for rc.1 is repo-marketplace/manual install; official Plugin Directory submission remains blocked on OpenAI self-serve publishing availability |
+
+## Current Publication Blockers
+
+- GitHub prerelease `v2.0.0-rc.1` is still not created in this pass.
+- npm `ecc-universal@2.0.0-rc.1` is still not published to the `next` dist-tag.
+- Claude plugin tag and marketplace propagation remain approval-gated.
+- Codex plugin repo-marketplace distribution is verified for rc.1, but official
+  Plugin Directory publishing is still blocked on OpenAI's coming-soon
+  self-serve publishing surface.
+- ECC Tools PR #73 added a fail-closed `/api/billing/readiness`
+  `announcementGate` for native GitHub payments claims, and ECC Tools PR #74
+  added `npm run billing:announcement-gate` as the operator verifier, but the
+  live Marketplace-managed test-account readback still must return
+  `announcementGate.ready === true` before any public payment announcement.
+- Release notes, X, LinkedIn, and longform copy still need final live URLs after
+  release/package/plugin URLs exist.
+
+## Result
+
+The queue, discussion, Linear roadmap, and supply-chain evidence are fresher
+than the May 13 publication evidence. They improve readiness, but they do not
+replace the final clean-checkout publish pass required by
+`publication-readiness.md`.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/publication-evidence-2026-05-16.md

@@ -0,0 +1,86 @@
+# ECC v2.0.0-rc.1 Publication Evidence - 2026-05-16
+
+This is release-readiness evidence only. It does not create a GitHub release,
+npm publication, plugin tag, marketplace submission, or announcement post.
+
+## Source Commit
+
+| Field | Evidence |
+| --- | --- |
+| Upstream main | `6bced468d76b269243a6f0bd28472853aa78e0e4` |
+| Git remote | `https://github.com/affaan-m/everything-claude-code.git` |
+| Evidence scope | Current `main` after PR #1944, PR #1945, issue #1946 triage, PR #1947 supply-chain protection, AgentShield PR #87, AgentShield PR #88, AgentShield PR #89, AgentShield PR #90, AgentShield PR #91, AgentShield PR #92, ECC-Tools PR #76, ECC-Tools PR #77, ECC-Tools PR #78, Japanese localization triage, ITO-57 sync, and operator dashboard refresh |
+| Local status caveat | `git status --short --branch` showed `## main...origin/main` plus unrelated untracked `docs/drafts/` |
+
+The actual release operator should repeat all publish-facing checks from the
+final release commit with a strictly clean checkout before publishing.
+
+## Queue And Discussion State
+
+| Surface | Command | Result |
+| --- | --- | --- |
+| Trunk PRs | `gh pr list --state open --json number,title,url --limit 20` | 6 open PRs: Dependabot #1959-#1963 plus PR #1953, which remains open with changes requested for Japanese localization parity |
+| Trunk issues | `gh issue list --state open --json number,title,url --limit 20` | 3 open issues: #1951 linked to held localization PR, plus #1957 and #1958 awaiting the next queue batch |
+| Platform audit | `node scripts/platform-audit.js --json --allow-untracked docs/drafts/` | Ready; open PRs 6, open issues 3, discussion maintainer-touch gaps 0, discussion missing-answer gaps 0, blocking dirty files 0 on a clean checkout; current branch generation sees the mirror edits as local dirty work |
+| Operator dashboard | `npm run operator:dashboard -- --json --allow-untracked docs/drafts/` | `dashboardReady: true`, `platformReady: true`, head `6bced468d76b269243a6f0bd28472853aa78e0e4` |
+
+## Merge And Triage Batch
+
+| Item | Result |
+| --- | --- |
+| PR #1944 | Merged statusline ANSI palette update as `50ac061f9e72d7daa137f1bd08760cf74e9b577d`; targeted `node tests/hooks/ecc-statusline.test.js` and `node scripts/ci/validate-hooks.js` passed before merge |
+| PR #1945 | Merged `recsys-pipeline-architect` community skill as `9e973b29fb1a2a0aeb9e6980017b67c3ddb05201`; maintainer patches synced catalog counts and removed emoji blocked by Unicode safety |
+| Issue #1946 | Closed as triaged with a corrected maintainer comment; Linear `ITO-60` now tracks GateGuard proactive fact-forcing preflight UX |
+| PR #1947 | Merged scheduled supply-chain watch/advisory-source evidence as `4093d1bb7a14db1b4d4ea5bd00f2073baf94bfb0`; trunk now has the TanStack/Mini Shai-Hulud/node-ipc IOC scan plus advisory-source report surfaces wired into scheduled watch evidence |
+| AgentShield PR #87 | Merged plugin-cache runtime-confidence classification as `26bb44650663816d07180e0d20c1895e431a326c`; installed Claude plugin cache findings now emit `runtimeConfidence: plugin-cache`, `plugins/cache` only maps to Claude cache under `.claude`, and cached hook implementations are no longer mislabeled as active `hook-code` |
+| AgentShield PR #88 | Merged evidence-pack inspect/readback as `65ed6e2a87545dc99d962b58413f49096a4d70ec`; `agentshield evidence-pack inspect` now emits verified JSON/text summaries for report, policy, baseline, supply-chain, CI context, remediation, and malformed artifact errors |
+| AgentShield PR #89 | Merged evidence-pack fleet routing as `521ada9091bb6d818511ab8589ae675b920c106a`; `agentshield evidence-pack fleet <dirs...> [--json]` now aggregates multiple verified bundles into ready, security-blocker, policy-review, baseline-regression, supply-chain-review, and invalid routes with finding, policy, baseline, supply-chain, and remediation totals |
+| AgentShield PR #90 | Merged fleet review items as `6d1c57c92000541d65a3b6bc366f0322d7d0dacc`; `agentshield evidence-pack fleet --json` now emits `reviewItems` with route, severity, repository/target context, source evidence paths, reason, and owner-ready recommendation, and the text CLI prints a `Review items` block |
+| AgentShield PR #91 | Merged checksum-backed policy export as `73e1e3586dc4513a462e39c9799f75eea104e110`; `agentshield policy export` writes one JSON policy file per selected pack plus `manifest.json` with SHA-256 digests, and supports pack selection, repeated owners, name prefixes, and JSON output |
+| AgentShield PR #92 | Merged checksum-verified policy promotion as `e7e259dc6212b63a8e03a253ca6b8c1e3c2abff7`; `agentshield policy promote` verifies the export manifest and selected policy digest, rejects tampered JSON, requires explicit pack selection for multi-pack manifests, supports dry-run JSON review, and writes the active policy only after verification |
+| ECC-Tools PR #76 | Merged AgentShield fleet-summary consumption as `5bde2328d15f584481fb6334e6960716dbf3e16f`; hosted `security-evidence-review` now recognizes `agentshield-evidence/fleet-summary.json`, classifies it as `evidence-pack-fleet`, routes invalid/security-blocker/policy/baseline/supply-chain fleet outcomes into hosted findings, and fails closed on malformed fleet JSON |
+| ECC-Tools PR #77 | Merged hosted finding source-evidence output as `31fd883b3f0cee135aee4839b01d34855b7867f6`; hosted job PR comments and check-run details now include an `Evidence` column with up to three source evidence paths per finding, including AgentShield fleet-derived findings |
+| ECC-Tools PR #78 | Merged AgentShield fleet-route harness review as `0d4eb949aa56f56da88e6654273a22ffb95983a1`; hosted `harness-compatibility-audit` now collects fleet summaries, maps route target paths to Claude/Codex/OpenCode/MCP/plugin harness owners, and emits owner-review findings with source evidence paths |
+| ITO-57 | Updated with PR #1947 advisory-source evidence, post-merge source refresh, IOC scan, npm audit/signature checks, and OpenAI app update caveat |
+| ITO-49 | Updated with AgentShield PR #87, #88, #89, #90, #91, and #92 merge evidence, local test evidence, CI status, live `~/.claude` scan classification counts, local Mini Shai-Hulud protection scan results, and policy promotion validation |
+| ITO-50 | Updated with ECC-Tools PR #76, PR #77, and PR #78 merge evidence, hosted security review behavior, hosted finding evidence-path behavior, harness fleet-route owner-review behavior, local test evidence, and remote Verify/Security Audit/Workers build checks |
+| ITO-44 | Updated with queue cleanup, dashboard refresh, and remaining macro gaps |
+
+## Release Gate Commands
+
+| Gate | Command | Result |
+| --- | --- | --- |
+| Root suite | `npm test` | 2469 passed, 0 failed |
+| Rust `ecc2` suite | `cd ecc2 && cargo test` | 462 passed, 0 failed; existing dead-code/unused warnings only |
+| Release surface | `node tests/docs/ecc2-release-surface.test.js` | 20 passed |
+| Harness adapters | `npm run harness:adapters -- --check` | PASS; 11 adapters |
+| Harness audit | `npm run harness:audit -- --format json` | 70/70, no top actions |
+| Observability readiness | `npm run observability:ready` | 21/21, ready yes |
+| Supply-chain IOC scan | `npm run security:ioc-scan` | Passed; 227 files inspected |
+| Advisory source refresh | `npm run security:advisory-sources -- --refresh --json` | Ready; 9 active sources; Linear payload still points at `ITO-57` for sync |
+| npm audit | `npm audit --audit-level=moderate` | 0 vulnerabilities |
+| npm signatures | `npm audit signatures` | 241 verified registry signatures; 30 verified attestations |
+| Dashboard renderer | `node tests/scripts/operator-readiness-dashboard.test.js` | 7 passed, 0 failed |
+
+## Current Publication Blockers
+
+- GitHub prerelease `v2.0.0-rc.1` is still not created in this pass.
+- npm `ecc-universal@2.0.0-rc.1` is still not published to the `next` dist-tag.
+- Claude plugin tag and marketplace propagation remain approval-gated.
+- Codex repo-marketplace distribution is verified for rc.1, but official
+  Plugin Directory publishing remains blocked on OpenAI's coming-soon
+  self-serve publishing surface.
+- ECC Tools billing/native-payments copy remains blocked until live
+  Marketplace-managed test-account readback returns an announcement-ready gate.
+- Release notes, X, LinkedIn, GitHub release, and longform copy still need final
+  live URLs after release/package/plugin URLs exist.
+- The local checkout still has unrelated untracked `docs/drafts/`, so a strict
+  clean-checkout release pass remains required before real publication.
+
+## Result
+
+The public PR queue, issue queue, and discussion queue are clear, and the rc.1
+preview pack passed the main Node, Rust, release-surface, harness, observability,
+and supply-chain gates on May 16, 2026. This improves publication readiness but
+does not replace the approval-gated release, package, plugin, and announcement
+steps in `publication-readiness.md`.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/publication-evidence-2026-05-17.md

@@ -0,0 +1,113 @@
+# ECC v2.0.0-rc.1 Publication Evidence - 2026-05-17
+
+This is release-readiness evidence only. It does not create a GitHub release,
+npm publication, plugin tag, marketplace submission, or announcement post.
+
+## Source Commit
+
+| Field | Evidence |
+| --- | --- |
+| Upstream main | `e6c16b40b80b3b323586c9e8341faa87c01a728c` |
+| Git remote | `https://github.com/affaan-m/everything-claude-code.git` |
+| Evidence scope | Current `main` after the Japanese and Thai localization merge batch, post-merge ja-JP markdown anchor repair, Zed install-target support, Mini Shai-Hulud/TanStack protection recheck, `gh-token-monitor` token-store IOC coverage, AgentShield policy-promotion Action output mirror, ECC-Tools hosted promotion judge audit-trace mirror, ECC-Tools billing announcement preflight mirror, ECC-Tools production Marketplace readback-state mirror, legacy-tail dashboard routing, Linear progress readiness, and the deterministic preview-pack smoke gate |
+| Local status caveat | `git status --short --branch` showed `## main...origin/main` plus unrelated untracked `docs/drafts/`; generated evidence files are committed after the source snapshot they describe |
+
+The actual release operator should repeat all publish-facing checks from the
+final release commit with a strictly clean checkout before publishing.
+
+## Queue And Discussion State
+
+| Surface | Command | Result |
+| --- | --- | --- |
+| Trunk PRs | `gh pr list --state open --limit 50 --json number,title` | 0 open PRs |
+| Trunk issues | `gh issue list --state open --limit 50 --json number,title` | 0 open issues |
+| Platform audit | `node scripts/platform-audit.js --json --allow-untracked docs/drafts/` | Ready; tracked repos report 0 open PRs, 0 open issues, 0 discussion maintainer-touch gaps, 0 answerable Q&A missing accepted answers, and 0 blocking dirty files |
+| Operator dashboard | `npm run operator:dashboard -- --markdown --allow-untracked docs/drafts/ --write docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-17.md` | Generated current dashboard for `e6c16b40b80b3b323586c9e8341faa87c01a728c`; dashboard ready true, publication ready false because release, npm, plugin, billing, and announcement gates are approval-gated |
+
+Tracked repositories in the platform audit were:
+
+- `affaan-m/everything-claude-code`
+- `affaan-m/agentshield`
+- `affaan-m/JARVIS`
+- `ECC-Tools/ECC-Tools`
+- `ECC-Tools/ECC-website`
+
+## Merge And Triage Batch
+
+| Item | Result |
+| --- | --- |
+| Issue #1957 | Closed with maintainer guidance after confirming README and hooks docs already document supported manual hook installation |
+| Issue #1958 | Closed in the earlier queue batch after the supply-chain IOC scan and protection pass |
+| PR #1962 | Closed instead of merged because ESLint 10 requires a newer Node engine range than the current Node 18 support contract |
+| PR #1961 | Merged TypeScript 6.0.3 as `344a9bdf9c45c7589dedd3c66a8a2ebf2cbf2e5b`; maintainer patch added Node types to `.opencode/tsconfig.json`; full GitHub Actions matrix passed |
+| PR #1963 | Merged `@types/node` 25.8.0 as `b66ae3fbe070ef1fd2b610b4011f1345b4d75875`; maintainer patch synced the npm lockfile; full GitHub Actions matrix passed |
+| PR #1953 | Merged Japanese localization as `9495b109e2c5fc5b1044ddfa1e2179f9d4aa86be`; maintainer patches fixed localized security/sponsorship links, translated the stale cubic-reported frontmatter items, confirmed `docs/zh-CN` to `docs/ja-JP` parity has 0 missing files, and approved after CodeRabbit, GitGuardian, and cubic passed |
+| Post-merge trunk fix | Pushed `afe0ae8d725f7773147dc4aa7943a45846853a0d` to remove broken intra-file anchors from `docs/ja-JP/skills/autonomous-loops/SKILL.md`; this restored root lint on `main` after PR #1953 |
+| Issue #1951 | Closed automatically as completed when PR #1953 merged |
+| Zed adapter commit | Pushed `2371a3cf0543365c1c18e84eba786b1abcb28941` to add project-local Zed support through the selective install target, README Zed guidance, and `.zed/settings.json` planning coverage |
+| Zed Windows CI fix | Pushed `744f4169972fd81618c3114ea1ca5ffb85ef4c82` to normalize the Zed install-plan source-path assertion across Windows path separators |
+| Discussion #1896 | Added a maintainer update confirming Zed support on `main`, documenting the dry-run command, and clarifying that BYOK/OpenRouter secrets stay in Zed/local user settings rather than ECC-managed project files |
+| PR #1967 | Merged Thai localization as `6b282aaa4389e9411e86bfe09d8f4de8018dcf8e` after applying the two maintainer cleanup comments, validating markdownlint and language-switcher coverage, and approving after CodeRabbit, GitGuardian, Greptile, and cubic passed on current head |
+| Supply-chain token-store scanner slice | Pushed `36d390aa7d733d458963a203b91998d3aec477b2` to detect the Mini Shai-Hulud `~/.config/gh-token-monitor/token` dead-man-switch token store, update the incident-response runbook, and add fixture coverage; local sweeps stayed clean and GitHub Actions `26003629550` passed |
+| Legacy-tail dashboard slice | Pushed `f397216aee5a0ca7d168726d3cc41eb47f728b37` and dashboard regeneration commits to keep localization-tail evidence attached to ITO-55 and prevent stale legacy work from being treated as release-current |
+| Linear progress readiness slice | Pushed `355c4f128183aa7f7ce9da9485af07d257d67f69` and dashboard regeneration commit `1a384dc5dbd24a3be725e1b26c169bddb6c850b6` to require refreshed Linear progress evidence after significant merge batches |
+| Preview-pack smoke slice | Pushed `3215e655eff70b9fea5382ce5996666a1f48d1af` to add `npm run preview-pack:smoke`, covering preview-pack artifacts, Hermes import boundaries, verification commands, and approval-gated publication blockers; lint and dashboard follow-up commits landed through `27dc2918a24a50b8dd5e23dba2aa6a05bd17c0d7` |
+| AgentShield hardening-output slice | Pushed AgentShield `1124535345d7040242ecd3803f65bcd4dcaf6ec2` to expose package-manager hardening status/count outputs and redacted GitHub Action job-summary evidence for registry credentials, lifecycle-script drift, and release-age gate drift |
+| AgentShield policy-promotion Action slice | Pushed AgentShield `1593925dca025632dd8a6454509fce3fe7517cdf` to expose policy-promotion status/count/digest outputs plus GitHub Action job-summary review items for owner approval, protected rollout, and runtime smoke; the same Action job marks runtime smoke verified when it scans with the promoted policy |
+| ECC-Tools policy-promotion telemetry slice | Pushed ECC-Tools `86589517b11b95f1b0216ae7737563fb67ee1604` to route AgentShield policy-promotion Action outputs into hosted security review findings and Hosted Promotion Readiness scoring |
+| ECC-Tools policy-promotion operator UX slice | Pushed ECC-Tools `16c537fd385458c438ff32fb4211079b2f8ea1c4` to render policy-promotion Action output status, pack, review item count, remaining action count, and digest in hosted security job comments and check-runs |
+| ECC-Tools hosted promotion judge audit trace slice | Pushed ECC-Tools `05d4e8296e37ba72e471beaa23ea4c81eb2aa31f` to render hosted promotion judge request fingerprints and allowed-citation audit traces without exposing raw provider output |
+| ECC-Tools billing announcement preflight slice | Pushed ECC-Tools `91a441b92342b842832ac28b018ee46f0c4a906f` to add `npm run billing:announcement-gate -- --preflight` for safe Marketplace readback input and endpoint verification before privileged API calls |
+| ECC-Tools production Marketplace readback-state slice | Pushed ECC-Tools `eb6941290b2fa70db01a51084e9e79a160238468` to record that production Cloudflare secret names include `INTERNAL_API_SECRET`, but production KV currently has no `account-billing:*` or `billing-state:*` records |
+
+## Release Gate Commands
+
+| Gate | Command | Result |
+| --- | --- | --- |
+| Root lint | `npm run lint` | Passed after the ja-JP autonomous-loop anchor repair |
+| Root suite | `npm test` | 2487 passed, 0 failed |
+| GitHub Actions CI | `gh run view 25989533576 --json status,conclusion,jobs` | Completed successfully with 37/37 jobs green, including Security Scan and all Windows test jobs |
+| Harness audit | `node scripts/harness-audit.js --format json` | 70/70, no top actions |
+| Observability readiness | `npm run observability:ready -- --format json` | 21/21, ready yes |
+| Workflow security | `node scripts/ci/validate-workflow-security.js` | Validated 8 workflow files |
+| Supply-chain IOC scan | `node scripts/ci/scan-supply-chain-iocs.js --root ~/GitHub --home --json`; `node scripts/ci/scan-supply-chain-iocs.js --root ~/Documents/GitHub --home --json` | Passed; each workspace sweep inspected 1,879 files with 0 findings, including user-level persistence targets |
+| npm audit | `npm audit --audit-level=high` | 0 vulnerabilities |
+| npm signatures | `npm audit signatures` across `agentshield`, `everything-claude-code`, `ECC-Tools`, `ECC-website`, and `JARVIS/frontend` | Passed across the primary ECC Node package roots |
+| Preview-pack smoke | `npm run preview-pack:smoke` | Passed; ready yes; digest `dfb1ed014607`; 5 checks passed and 0 failed |
+| AgentShield enterprise CI output slice | AgentShield local `npm run build`, focused action tests, `npm run typecheck`, `npm run lint`, full `npm test`, and `git diff --check`; GitHub Actions `25994354007`, `25994354011`, `25994354026` | Local gates passed; remote CI, Test GitHub Action, and Self-Scan completed successfully for `1124535` |
+| AgentShield policy-promotion Action output slice | AgentShield local `npm run build`, `npx vitest run tests/action-promotion.test.ts tests/action.test.ts`, `npm run typecheck`, `npm run lint`, full `npm test`, and `git diff --check`; GitHub Actions `25995929182`, `25995929190`, `25995929161` | Local gates passed; remote CI, Test GitHub Action, and Self-Scan completed successfully for `1593925` |
+| ECC-Tools policy-promotion hosted telemetry slice | ECC-Tools local focused vitest checks for policy-promotion Action-output routing and hosted-promotion readiness, `npm run typecheck`, `npm run lint`, full `npm test`, and `git diff --check`; GitHub Actions `25996758218` | Local gates passed; remote CI completed successfully for `8658951` |
+| ECC-Tools policy-promotion operator UX slice | ECC-Tools local focused vitest checks for policy-promotion Action output values in hosted findings/comments/checks, `npm run typecheck`, `npm run lint`, full `npm test`, and `git diff --check`; GitHub Actions `25997300046` | Local gates passed; remote CI completed successfully for `16c537f` |
+| ECC-Tools hosted promotion judge audit trace slice | ECC-Tools local focused vitest checks for hosted model-judge audit traces, `npm run typecheck`, `npm run lint`, full `npm test`, and `git diff --check`; GitHub Actions `25997840703` | Local gates passed; remote CI completed successfully for `05d4e82` |
+| ECC-Tools billing announcement preflight slice | ECC-Tools local focused vitest preflight tests, `npm run typecheck`, `npm run lint`, full `npm test`, and `git diff --check`; GitHub Actions `25998238507` | Local gates passed; remote CI completed successfully for `91a441b` |
+| ECC-Tools production Marketplace readback-state slice | ECC-Tools local `npm test` and `git diff --check`; Cloudflare `wrangler secret list` confirmed `INTERNAL_API_SECRET` exists by name; `wrangler kv key list` for `account-billing:` and `billing-state:` both returned empty lists; GitHub Actions `25998610438` | Local gates passed; remote CI completed successfully for `eb69412`; live announcement remains blocked until Marketplace purchase/webhook records populate KV |
+| GitHub queues | `gh pr list`; `gh issue list`; `node scripts/platform-audit.js --json --allow-untracked docs/drafts/` | 0 open PRs, 0 open issues, 0 discussion maintainer-touch gaps, 0 answerable Q&A missing accepted answers, 0 GitHub fetch errors, and platform audit ready across the tracked repo set after generated evidence is committed |
+| Operator dashboard | `npm run operator:dashboard -- --markdown --allow-untracked docs/drafts/ --write docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-17.md` | Dashboard generated for `e6c16b40b80b3b323586c9e8341faa87c01a728c` with platform ready true, dashboard ready true, and macro publication gates still incomplete |
+| GitHub Actions CI | `gh run watch 26003629550 --repo affaan-m/everything-claude-code --exit-status` | Completed successfully for `36d390aa7d733d458963a203b91998d3aec477b2`, including Validate Components, Lint, Security Scan, Coverage, and the full OS/Node/package-manager matrix |
+
+## Current Publication Blockers
+
+- GitHub prerelease `v2.0.0-rc.1` is still not created in this pass.
+- npm `ecc-universal@2.0.0-rc.1` is still not published to the `next`
+  dist-tag.
+- Claude plugin tag and marketplace propagation remain approval-gated.
+- Codex repo-marketplace distribution is verified for rc.1, but official
+  Plugin Directory publishing remains blocked on OpenAI's self-serve publishing
+  surface.
+- ECC Tools billing/native-payments copy remains blocked until a Marketplace
+  purchase/webhook path writes production `account-billing:*` and
+  `billing-state:*` records, then `npm run billing:announcement-gate --
+  --account <github-login>` returns an announcement-ready gate.
+- Release notes, X, LinkedIn, GitHub release, and longform copy still need final
+  live URLs after release/package/plugin URLs exist.
+- The local checkout still has unrelated untracked `docs/drafts/`, so a strict
+  clean-checkout release pass remains required before real publication.
+
+## Result
+
+The tracked public PR queue, issue queue, and discussion queue are clean on
+May 17, 2026, and current `main` passed the Node, harness, observability,
+workflow-security, npm audit/signature, and supply-chain IOC gates listed above.
+This improves publication readiness but does not replace the approval-gated
+release, package, plugin, billing, and announcement steps in
+`publication-readiness.md`.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/publication-evidence-2026-05-18.md

@@ -0,0 +1,150 @@
+# ECC v2.0.0-rc.1 Publication Evidence - 2026-05-18
+
+This is release-readiness evidence only. It does not create a GitHub release,
+npm publication, plugin tag, marketplace submission, or announcement post.
+
+## Source Commit
+
+| Field | Evidence |
+| --- | --- |
+| Upstream main | `4470e2e6702f17099d6feb137ba03ff00582c202` |
+| Git remote | `https://github.com/affaan-m/everything-claude-code.git` |
+| Evidence scope | Current `main` after PR #1970 workflow-security validator bypass fixes, PR #1971 metrics bridge cost-reporting fixes, PR #1972 `uncloud` skill merge, PR #1973 stale script cleanup, issue #1974 cost-reporting verification/closure, PR #1976 OpenAI/AstraFlow provider response guards, PR #1978 review/closure, catalog/operator dashboard refresh, ECC-Tools Wrangler OAuth billing readback mirror, AgentShield `840952a` fleet-ticket and Mini Shai-Hulud IOC evidence mirror, Mini Shai-Hulud/TanStack protection recheck, defensive-deny IOC scanner hardening, release name/plugin publication checklist, readiness/smoke gate enforcement for that checklist, release OIDC publishing-scope hardening, workflow line-ending normalization, current-head CI/security scan, work-items sync, Linear progress sync, the ITO-46 publication-path dry-run refresh, ITO-46 Linear closure, and the post-closure operator dashboard refresh |
+| Local status caveat | `git status --short --branch` was clean at dashboard generation time; generated evidence files are committed after the source snapshot they describe |
+
+The actual release operator should repeat all publish-facing checks from the
+final release commit with a strictly clean checkout before publishing.
+
+## Queue And Discussion State
+
+| Surface | Command | Result |
+| --- | --- | --- |
+| Trunk PRs | `gh pr list --limit 100 --json number,title,state,author,updatedAt,url` | 0 open PRs |
+| Trunk issues | `gh issue list --limit 100 --json number,title,state,updatedAt,url,labels` | 0 open issues |
+| Discussion audit | `npm run discussion:audit -- --json` | Ready; 58 sampled discussions in `affaan-m/everything-claude-code`, 0 needing maintainer touch, 0 answerable discussions missing accepted answer, and 0 fetch errors |
+| Platform audit | `node scripts/platform-audit.js --json --allow-untracked docs/drafts/` | Ready; tracked repos report 0 open PRs, 0 open issues, 0 discussion maintainer-touch gaps, 0 answerable Q&A missing accepted answers, and 0 blocking dirty files |
+| Work-items sync | `node scripts/work-items.js sync-github --repo <tracked-repo>` for five tracked repos; `node scripts/status.js --json`; `node scripts/work-items.js list --json` | All five tracked repos synced with 0 open PRs/issues and no changed work items; local status reports 0 open, 0 blocked, and 0 closed work items |
+| Operator dashboard | `npm run operator:dashboard -- --markdown --write docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-18.md` | Regenerated at `4470e2e6702f17099d6feb137ba03ff00582c202`; dashboard ready true, publication ready false because release, npm, plugin, billing, and announcement gates are approval-gated; 0 PRs, 0 issues, and 0 discussion gaps remain across tracked repos; AgentShield enterprise evidence includes `840952a`; ECC Tools native-payments gate now names the narrowed ITO-61 blocker: create or verify Marketplace-managed Pro target billing-state with webhook provenance, configure the target account and `INTERNAL_API_SECRET`, then rerun target readback and the live announcement gate |
+
+Tracked repositories in the platform audit and work-items sync were:
+
+- `affaan-m/everything-claude-code`
+- `affaan-m/agentshield`
+- `affaan-m/JARVIS`
+- `ECC-Tools/ECC-Tools`
+- `ECC-Tools/ECC-website`
+
+## Merge And Triage Batch
+
+| Item | Result |
+| --- | --- |
+| PR #1970 | Merged workflow-security validator fixes for quoted `write-all` and `refs/pull/*` checkout bypasses; main includes `e06d0382` and `7bb31720` from that slice |
+| PR #1971 | Merged metrics bridge cost-reporting fixes, full costs-file scan behavior, and persistent warning de-duplication across hook subprocesses; main includes commits through `9b1d8918` |
+| PR #1972 | Merged `skills/uncloud/SKILL.md` with activation structure and uncloud command references; main includes `8b6aed0`, `2e5f30f`, and `caee7cf` |
+| PR #1973 | Merged stale `skills/strategic-compact/suggest-compact.sh` removal after confirming the active hook is `scripts/hooks/suggest-compact.js`; remote main includes `812d4d06` |
+| Issue #1974 | Closed after verifying current `origin/main` already reads the latest cumulative metrics bridge cost row and focused cost/metrics tests pass |
+| Catalog/operator refresh | Pushed `81fca2ce` to refresh generated catalog count, URL ledger, and operator dashboard state after #1973/#1974 |
+| PR #1976 | Merged provider response hardening for OpenAI-compatible and AstraFlow providers; main includes `eb0d8939` follow-up guards for empty/filtered provider choices, missing OpenAI `response.usage`, shared filtered-response error text, and credential-less provider construction validation |
+| Provider guard validation | `uv run --extra dev pytest -q tests/test_provider_tools.py tests/test_astraflow_provider.py`, `uv run --extra dev pytest -q`, `node tests/run-all.js`, and `git diff --check` passed before merging #1976 follow-up into main: 11 provider-focused Python tests, 76 full Python tests, 2509 Node tests, and clean whitespace checks |
+| Defensive-deny IOC scanner hardening | Pushed `04d4d819` so explicit Claude `permissions.deny` IOC entries are treated as defensive controls while the same IOC still fails in hooks, tasks, scripts, locks, and payload files; local `npm test` passed 2511/2511 and current-head CI `26017368895` passed 37/37 |
+| Release name/plugin publication checklist | Pushed `6c0fbfb6` to add `docs/releases/2.0.0-rc.1/release-name-plugin-publication-checklist-2026-05-18.md`; the artifact freezes rc.1 as Everything Claude Code / ECC, keeps npm `ecc-universal`, keeps Claude/Codex plugin slug `ecc`, cites current Anthropic/OpenAI plugin publication paths, and blocks rename/npm publish/plugin tag/submission/billing/social actions until final release evidence exists; GitHub Actions CI `26034898420` passed |
+| Dashboard and preview-pack checklist enforcement | Added `680aeff0` so `scripts/operator-readiness-dashboard.js` and `scripts/preview-pack-smoke.js` require the release-name/plugin publication checklist; local dashboard and smoke tests passed and preview-pack smoke now enforces 26 required artifacts |
+| AgentShield enterprise evidence mirror | Added `2ba0c62d` and refreshed the dashboard generator/GA roadmap/AgentShield enterprise roadmap so the ECC release evidence names AgentShield `840952a` fleet review ticket payloads and current Mini Shai-Hulud IOC breadcrumb coverage |
+| PR #1978 | Closed broad/failing outside Excel harness PR after review; recorded a corrected split path for a future smaller Excel harness proposal, install-target/tooling PR, plugin-runtime PR, and translation-automation PR |
+| Announcement draft tracking | Added `docs/drafts/release-1.10.1-announcement.md` so the stabilization announcement draft is tracked instead of remaining as release-blocking untracked local state |
+| Clean-worktree preview-pack smoke | Detached worktree at `680aeff0fb9a8598858e3105ba4742973ef386ab`; `node scripts/preview-pack-smoke.js --root <worktree> --format json` passed 5/5 with digest `0ed831dbd0cf`; 26 required artifacts, final verification commands, Hermes public sanitization boundary, and approval-gated publication blockers were all preserved |
+| Public queues | Rechecked after the merge and issue-closure batch; 0 PRs, 0 issues, and 0 discussion gaps remain across tracked repos |
+| Release OIDC publishing scope | Pushed `7911af4a` to keep the release workflow's trusted-publishing path scoped to release publication instead of broadening OIDC permissions across unrelated jobs; local workflow security validation passed |
+| Release workflow normalization | Pushed `97567a91` to normalize release workflow line endings after the OIDC hardening slice; current-head CI `26050727969` passed for `97567a91e79e1ee4c291eb78f5f9c30c2046ac94` |
+| Operator readiness evidence refresh | Pushed `0f1775e3`, `fe7b4f2b`, and `67e63e63` to refresh blocker evidence, regenerate the operator dashboard, and align publication readiness to the latest CI/security evidence; pushed `4470e2e6` to close ITO-46 publication-path evidence, then regenerated the dashboard at `4470e2e6702f17099d6feb137ba03ff00582c202`; current-head CI `26057806361` passed for `4470e2e6702f17099d6feb137ba03ff00582c202` |
+
+## Supply-Chain And Security Evidence
+
+| Gate | Command | Result |
+| --- | --- | --- |
+| Repo IOC scan | `npm run security:ioc-scan` | Passed; 198 files inspected |
+| Home persistence IOC scan | `node scripts/ci/scan-supply-chain-iocs.js --home --json` | Passed; 200 files inspected; `findings: []` |
+| ECC workspace IOC recheck | `node scripts/ci/scan-supply-chain-iocs.js --root <local ECC root> --home --json` | Passed; 1212 files inspected; `findings: []`; exact local path is kept out of public release evidence |
+| Narrow active persistence sweep | Targeted search over user-level Claude, VS Code, LaunchAgent/systemd, local-bin, `/tmp`, and `/private/tmp` campaign paths | Existing active targets: 2; no campaign marker hits |
+| Scanner fixture tests | `node tests/ci/scan-supply-chain-iocs.test.js` | 20 passed, 0 failed, including defensive Claude deny-wall pass and hook-with-same-IOC fail-closed coverage |
+| Advisory source refresh | `node scripts/ci/supply-chain-advisory-sources.js --refresh --json` | Ready with 9 sources; live refresh produced 1 OpenAI URL warning from Node fetch while primary TanStack, GitHub advisory, StepSecurity, Wiz, Socket, npm, and CISA sources returned OK |
+| No-lifecycle install | `npm ci --ignore-scripts` | Completed cleanly; 213 packages installed, 0 vulnerabilities |
+| npm audit | `npm audit --audit-level=high` | 0 vulnerabilities |
+| npm signatures | `npm audit signatures` | 213 verified registry signatures; 17 verified attestations |
+| Workflow security | `node scripts/ci/validate-workflow-security.js` | Validated 8 workflow files after the release OIDC publishing-scope hardening |
+| AgentShield project scan | `npx --no-install ecc-agentshield scan --format json` | Grade A / 99; 0 critical, 0 high, 0 medium; 6 low docs-example skill telemetry/governance findings |
+| Current-head CI security scan | `gh run view 26057806361 --repo affaan-m/everything-claude-code --json status,conclusion,headSha,jobs,url` | Completed successfully for `4470e2e6702f17099d6feb137ba03ff00582c202`; 37/37 CI jobs passed, including lint, workflow/component validation, coverage, cross-platform package-manager tests, npm audit, and supply-chain IOC scan |
+| Latest Supply-Chain Watch | `gh run view 26010432490 --repo affaan-m/everything-claude-code --json status,conclusion,headSha,url` | Completed successfully for `25ac57ac40e9fc5a0606e76e6339e72c79748c99`; rerun from the final release commit before publication |
+
+## ITO-46 Publication Path Refresh
+
+| Gate | Command | Result |
+| --- | --- | --- |
+| Clean publication-path baseline | `git status --short --branch`; `git rev-parse HEAD`; `git remote get-url origin` | Clean `main` at `67e63e63f9bfd074bd6a21bf6bac71f3dfefa58b`; remote `https://github.com/affaan-m/everything-claude-code.git` |
+| Package/plugin identity readback | `node -p "JSON.stringify({pkg, claude, codex, opencode}, null, 2)"` | `ecc-universal@2.0.0-rc.1`; Claude plugin `ecc@2.0.0-rc.1`; Codex plugin `ecc@2.0.0-rc.1`; OpenCode package `ecc-universal@2.0.0-rc.1` |
+| Name availability | `npm view ecc name version description repository.url --json`; `npm view @affaan-m/ecc name version --json`; `npm view ecc-universal name version dist-tags --json` | `ecc` is occupied by unrelated `ecc@0.0.2`; `@affaan-m/ecc` returns 404; `ecc-universal` registry latest remains `1.10.0` with no `next` dist-tag |
+| Plugin manifest tests | `node tests/plugin-manifest.test.js` | 54 passed, 0 failed |
+| Release surface tests | `node tests/docs/ecc2-release-surface.test.js` | 21 passed, 0 failed |
+| Claude plugin validation | `claude plugin validate .claude-plugin/plugin.json`; `claude plugin validate .`; `claude plugin tag .claude-plugin --dry-run` | Claude Code `2.1.143`; manifest validation passed; full plugin validation passed with one expected root `CLAUDE.md` context warning; tag dry run would create `ecc--v2.0.0-rc.1` |
+| Claude marketplace source help | `claude plugin marketplace add --help`; `claude plugin marketplace update --help` | Marketplace add supports URL, local path, GitHub repo, `--scope`, and `--sparse`; update supports targeted or all-marketplace refresh |
+| Codex marketplace help | `codex plugin marketplace add --help` | Codex CLI `0.131.0`; marketplace add supports local paths, `owner/repo[@ref]`, HTTPS Git URL, SSH Git URL, `--ref`, and `--sparse` |
+| Codex local marketplace smoke | `HOME="$(mktemp -d)" codex plugin marketplace add ./` | Added marketplace `ecc` from the local checkout without touching the real Codex config |
+| Codex GitHub-ref marketplace smoke | `HOME="$(mktemp -d)" codex plugin marketplace add affaan-m/everything-claude-code --ref "$(git rev-parse HEAD)"` | Added marketplace `ecc` from the public GitHub repo pinned to `67e63e63f9bfd074bd6a21bf6bac71f3dfefa58b` without touching the real Codex config |
+| npm package dry-run | `NPM_CONFIG_USERCONFIG=/dev/null npm pack --dry-run --json`; `NPM_CONFIG_USERCONFIG=/dev/null npm publish --tag next --dry-run` | Pack produced `ecc-universal-2.0.0-rc.1.tgz`, 2228 files, 4,348,504 bytes packed, 13,024,929 bytes unpacked, shasum `29d6a17029d80f5cb1df068880ba86c55a5d60f1`; publish dry-run would publish `ecc-universal@2.0.0-rc.1` with tag `next` |
+| OpenCode package build | `npm run build:opencode` | Passed |
+| Preview pack smoke | `npm run preview-pack:smoke` | Ready yes; digest `0ed831dbd0cf`; 5 passed, 0 failed |
+| Official docs check | Anthropic `https://code.claude.com/docs/en/plugins` and `https://code.claude.com/docs/en/plugin-marketplaces`; OpenAI `https://developers.openai.com/codex/plugins/build` | Anthropic documents self-hosted marketplace sources; OpenAI documents repo/personal marketplaces and the official Plugin Directory. ECC has not created a real release tag, official listing, or npm publication in this pass |
+| ITO-46 closure | Linear ITO-46 comment `9ef92056-ab23-4eed-bfdb-932dddc2b056`; Linear issue status `Done`; GitHub Actions `26057806361` | Publication-path docs now record every channel, name conflicts, package/plugin dry-run commands, and blocker register; Codex repo-marketplace distribution is verified but official Plugin Directory listing is not claimed before OpenAI submission/listing evidence |
+
+## Linear Progress Sync
+
+| Surface | Evidence |
+| --- | --- |
+| ITO-57 issue comments | `0b9931b9-1556-4ebc-a70c-f3635557625d` records May 18 queue counts, #1970/#1971/#1972/#1976 merge evidence, supply-chain verification, current-head CI URL, deferred gates, and next slices; reply `6fa15367-d994-4e53-ade3-9462477e1100` records the expanded TanStack/Mini Shai-Hulud recheck, defensive-deny scanner fix, current-head CI `26017368895`, and post-push platform audit; comment `3fe5b2b7-c4fe-401c-a317-b40d72119cb3` records the final emergency refresh against `97567a91`, AgentShield `4e36aab`, clean ECC/Ito/Documents workspace IOC scans, absent dead-man/persistence artifacts, and package-manager/Claude deny-wall posture; comment `43837404-c01c-4aaa-b5e2-1e784c136d69` records ECC-Tools `brace-expansion` alert 44 fixed in `e56fc1a` with CI `26054671308` and Dependabot API `state: fixed` |
+| ITO-52 issue status | `f2e5a208-de91-4a3a-960b-5362d12aa5a4` records ECC-Tools `69ca535` team-learning feedback controls, local verification, and CI `26054455434`; Linear ITO-52 is Done |
+| ITO-61 issue status | `6904e4fb-bec7-4787-90e2-759f077a628c` records the narrowed native-payments readback blocker: Wrangler OAuth now works, aggregate readback is clean, but there is still no Marketplace-managed Pro target billing-state with webhook provenance and the local announcement preflight is missing the target account plus `INTERNAL_API_SECRET` |
+| ECC platform project comment | `e32e5b7a-287b-4bf4-9ed7-314389a157e1` records the earlier current public queue, security, #1976, and remaining-gate state at the project level; follow-up ITO-44 comments `a01eeef3-c69b-48c0-8804-a4682acfc1ef` and `6b0885cc-c4e9-40db-899b-f7b88b4aa046` record ITO-52 completion and the fixed ECC-Tools Dependabot alert |
+| Project status update caveat | Linear returned "Project status updates are not enabled for this workspace"; project comment was used as the supported status surface |
+
+## Current Publication Blockers
+
+- GitHub prerelease `v2.0.0-rc.1` is still not created in this pass.
+- npm `ecc-universal@2.0.0-rc.1` is still not published to the `next`
+  dist-tag.
+- Claude plugin tag and marketplace propagation remain approval-gated.
+- Codex repo-marketplace distribution is verified for rc.1, but official
+  Plugin Directory publishing remains blocked on OpenAI's self-serve publishing
+  surface.
+- ECC Tools billing/native-payments copy remains blocked until a Marketplace
+  Pro purchase/webhook path writes ready production `billing-state:*`
+  provenance for the target Marketplace test account, then
+  `npm run billing:kv-readback -- --account <github-login> --require-ready`
+  with working Cloudflare API auth or repaired Wrangler OAuth, followed by
+  `npm run billing:announcement-gate -- --account <github-login>`, return
+  announcement-ready gates. The latest Wrangler OAuth aggregate readback found
+  256 `account-billing:*` records, 256 `billing-state:*` records, 197
+  Marketplace-source records, 59 Stripe-source records, 53 Pro records, 4
+  Marketplace webhook-provenance records, all `Open Source`, 0 Marketplace Pro
+  states, 0 ready-like Marketplace Pro states, and 0 parse failures. ECC-Tools
+  commit `632e059` adds the follow-up target-account readback mode, redacts
+  the account login and raw KV key names, and requires both target key families
+  before `--require-ready` can pass. ECC-Tools commit `13cd3fc` normalizes
+  billing-state key casing. The latest ITO-61 retry fails because no
+  Marketplace-managed Pro state exists and the announcement preflight is
+  missing the target account plus `INTERNAL_API_SECRET`; Linear ITO-61 tracks
+  the exact target-account acceptance criteria.
+- Release notes, X, LinkedIn, GitHub release, and longform copy still need final
+  live URLs after release/package/plugin URLs exist.
+- The local checkout is clean after the dashboard/evidence refresh, but a
+  strict clean-checkout release pass remains required before real publication.
+
+## Result
+
+The tracked public PR queue, issue queue, discussion queue, local work-items
+bridge, release-name/plugin publication gate, and Mini Shai-Hulud/TanStack
+protection loop are current on May 18, 2026 for current `main` through
+`97567a91`, with follow-up ECC Tools billing-gate hardening in `632e059`
+and AgentShield enterprise/security hardening through `4e36aab`.
+This improves publication readiness but does not replace the approval-gated
+release, package, plugin, billing, and announcement steps in
+`publication-readiness.md`.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/publication-evidence-2026-05-19.md

@@ -0,0 +1,207 @@
+# ECC v2.0.0-rc.1 Publication Evidence - 2026-05-19
+
+This is release-readiness evidence only. It does not create a GitHub release,
+npm publication, plugin tag, marketplace submission, billing announcement, or
+social announcement.
+
+## Source Commit
+
+| Field | Evidence |
+| --- | --- |
+| Upstream main | `c2471fe5c535310f8a8008c9ed7ea9f6757b33f2` |
+| Git remote | `https://github.com/affaan-m/ECC.git` |
+| Evidence scope | Current `main` after PR #1990 harness-audit GitHub integration scoring, PR #1991 canonical ECC identity gate, PR #1992 release video-suite gate, PR #1993 growth outreach pack, PR #1994 May 19 publication evidence refresh, PR #1995 operator dashboard refresh, PR #1996 primary render self-eval gate, PR #1997 publish-candidate gate, PR #1998 visual QA gate, PR #1999 video dashboard evidence refresh, PR #2000 suite-count evidence refresh, PR #2001 owner approval packet addition, PR #2002 owner approval dashboard gate refresh, PR #2004 Linear readiness evidence sync, PR #2005 post-PR #2004 evidence refresh, PR #2008 release supply-chain evidence gate fix, PR #2006 per-project Claude Code adapter, PR #2009 continuous-learning project registry hygiene fix, PR #2011 GateGuard quoted git introspection fix, PR #2013 deterministic release approval gate, PR #2017 AgentShield adapter evidence sync, PR #2018 AgentShield Dependabot evidence sync, ECC-Tools #80-#91 hosted observability/readback, Marketplace Pro selected-target, selected-target announcement gate, and env-file operator-path batch, AgentShield #94 Zed/VS Code adapter coverage, AgentShield #95 Dependabot alert closure, PR #2019 Marketplace Pro release-gate sync, and PR #2020 selected-target announcement gate sync |
+| Local status caveat | `git status --short --branch` was clean after pulling `origin/main`; generated evidence files are committed after the source snapshot they describe |
+
+The release operator must repeat all publish-facing checks from the exact final
+release commit with a strictly clean checkout before publishing.
+
+## Queue And Discussion State
+
+| Surface | Command | Result |
+| --- | --- | --- |
+| Platform audit | `node scripts/platform-audit.js --json` | Ready true; tracked repos report 0 open PRs, 0 open issues, 0 discussion maintainer-touch gaps, 0 answerable Q&A gaps, 0 conflicting PRs, and 0 blocking dirty files |
+| Trunk PRs | `gh pr list --repo affaan-m/ECC --state open --json number,title,url,author --limit 100` | `[]` |
+| Trunk issues | `gh issue list --repo affaan-m/ECC --state open --json number,title,url,author --limit 100` | `[]` |
+| Discussion audit through platform audit | `node scripts/platform-audit.js --json` | `affaan-m/ECC` discussions enabled; 60 sampled after #2015 setup-location Q&A was answered and accepted; 0 needing maintainer touch; 0 answerable without accepted answer |
+| Worktree | `git status --short --branch` | `## main...origin/main` |
+
+Tracked repositories in the platform audit were:
+
+- `affaan-m/ECC`
+- `affaan-m/agentshield`
+- `affaan-m/JARVIS`
+- `ECC-Tools/ECC-Tools`
+- `ECC-Tools/ECC-website`
+
+## Merge Batch
+
+| Item | Result |
+| --- | --- |
+| PR #1990 | Merged GitHub integration harness-audit scoring and conflict salvage from the earlier unsafe PR lane |
+| PR #1991 | Merged canonical ECC release identity gate across README, plugin/package metadata, OpenCode surfaces, Marketplace metadata, audit defaults, quickstart, release URL ledger, naming/publication matrix, and release tests |
+| PR #1992 | Merged the release video-suite gate, production manifest, validator, package file surface, preview-pack smoke wiring, release-surface tests, and compact CI JSON output |
+| PR #1993 | Merged the partner, sponsor, consulting, conference, podcast, GitHub Discussion, and video CTA pack for the hypergrowth outbound lane |
+| PR #1994 | Merged the May 19 publication-evidence refresh, platform-audit evidence gate, preview-pack smoke evidence gate, and URL/readiness/roadmap references |
+| PR #1995 | Merged the May 19 operator dashboard refresh with the `$1,728/mo` MRR baseline, `$10,000/mo` target, and release/video/outbound top actions |
+| PR #1996 | Merged the primary launch render self-eval gate for duration, size, resolution, video stream, and audio stream checks |
+| PR #1997 | Merged the publish-candidate gate for the primary launch MP4/captions plus five short clips in wide and vertical formats |
+| PR #1998 | Merged the release video visual QA gate for publish candidates and black-frame segment detection |
+| PR #1999 | Merged the operator dashboard refresh that moved the release video suite to current once publish-candidate evidence was recorded |
+| PR #2000 | Merged the suite-count evidence refresh so the platform audit rejects stale local-suite totals |
+| PR #2001 | Merged the final human decision sheet for release, package, plugin, video, billing, social, and outbound approvals; GitHub Actions run `26102500291` completed successfully |
+| PR #2002 | Merged the owner-approval dashboard refresh so the operator dashboard fails closed when the final decision sheet is missing or incomplete; CI passed before merge |
+| PR #2004 | Merged the May 19 Linear readiness evidence sync after PR #2002, including roadmap, dashboard, preview-pack manifest, publication evidence, operator dashboard generator, and release-surface test updates |
+| PR #2005 | Merged the post-PR #2004 evidence refresh, keeping the May 19 readiness ledger, dashboard, roadmap, and release-surface references current on `main` |
+| PR #2008 | Merged the release supply-chain evidence gate fix so platform-audit readiness keeps matching current publication evidence |
+| PR #2006 | Merged the `claude-project` install target for per-project Claude Code adapter support, then fixed the manifest schema enum on top of the feature branch before merge |
+| PR #2009 | Merged the continuous-learning project registry hygiene fix: non-git hook payloads stay global, no-remote linked worktrees migrate to the main worktree project ID, and `instinct-cli.py projects delete`, `merge`, and `gc` provide operator maintenance commands |
+| PR #2011 | Merged the GateGuard read-only git introspection tokenizer fix so quoted `git show` pathspecs with spaces are preserved while quoted shell separators stay outside the bypass |
+| PR #2013 | Merged the deterministic `release:approval-gate` so final publication, package, plugin, video, billing, social, and outbound actions remain blocked until owner decisions and live URL readbacks are complete |
+| PR #2017 | Merged the AgentShield #94 evidence mirror as `906e06406e95742944ccb05065f95a7e4dd4a036`, syncing roadmap, publication evidence, preview-pack manifest, and supply-chain incident-response surfaces after full GitHub CI passed |
+| PR #2018 | Merged the AgentShield #95 Dependabot evidence mirror as `68b4e45145968acd52e68d900f8422061ed7f4a2`, syncing the roadmap, publication evidence, and preview-pack manifest after full PR CI passed |
+| PR #2019 | Merged the Marketplace Pro selected-target release-gate sync as `30f60710d4e0424fc70d9bbdc105009db141d9d8`, updating the roadmap, publication evidence, naming matrix, preview manifest, and operator dashboard after full PR CI passed |
+| PR #2020 | Merged the selected-target announcement gate sync as `c2471fe5c535310f8a8008c9ed7ea9f6757b33f2`, updating the roadmap, publication evidence, naming matrix, preview manifest, release URL ledger, platform audit surfaces, and operator dashboard after full PR CI passed |
+
+## Post-Queue-Zero Sync - 2026-05-19 Late Pass
+
+| Surface | Evidence |
+| --- | --- |
+| ECC approval gate | PR #2013 merged as `9819626459a662773be7d0b1c18d82c1316b8c36`; GitHub Actions run `26128749863` completed successfully; `npm run release:approval-gate -- --format json` remains intentionally blocked with digest `ef8f49f727b7`, 4/6 passing, and failures only on owner decisions plus live URL readbacks |
+| ECC platform audit | `node scripts/platform-audit.js --json` at `2026-05-19T22:45:15Z` returned ready true, 0 open PRs, 0 open issues, 0 discussion maintainer-touch gaps, 0 answerable Q&A gaps, and 0 dirty blockers across `affaan-m/ECC`, `affaan-m/agentshield`, `affaan-m/JARVIS`, `ECC-Tools/ECC-Tools`, and `ECC-Tools/ECC-website` |
+| ECC-Tools billing hardening | ECC-Tools PR #79 merged as `67ee247ae1b7b50ecc1261ed5d62d65cc8390da8`; preflight and live billing-announcement output now redact account login values to a stable fingerprint while preserving readiness blockers/actions; local validation passed targeted tests, full test suite 678/678, lint, typecheck, manual preflight, and `git diff --check`; post-merge main CI run `26129253509` completed successfully |
+| JARVIS queue drain | JARVIS PR #15 merged the Dependabot `idna` 3.11 to 3.15 security bump as `4b3685d6ee23b4da1f1a7d22281c6b5d6c0a42c7`; PR checks and post-merge CI/CodeQL passed |
+| JARVIS deploy repair | JARVIS PR #16 merged as `4369c34babd21d539c420866da51c7a8365f1c9e`; the deploy workflow no longer uses an invalid job-level `secrets.*` condition, Vercel deploy skips cleanly when secrets are absent, backend image build/push succeeds, and main CI, CodeQL, and Deploy runs `26129539376`, `26129539427`, and `26129539425` completed successfully |
+| Linear roadmap sync | Linear document `ecc-may-19-late-queue-zero-and-release-gate-sync-1c26f65e6b3f`, project comment `d42bf0e2-7a8e-4934-9f3f-e281498ee805`, and issue comments on ITO-44, ITO-50, ITO-54, ITO-56, and ITO-61 record the late-pass queue-zero, release-gate, billing-safety, and progress-sync state. |
+
+## May 20 Hosted Observability And AgentShield Adapter Sync
+
+| Surface | Evidence |
+| --- | --- |
+| ECC discussion queue | Discussion #2015 was answered and marked accepted with conservative setup guidance: do not install in `C:\`; use a normal workspace; install `ecc@ecc` once through the Claude plugin marketplace; copy only needed rule folders when using manual rules; do not stack plugin plus full manual install. |
+| ECC platform audit | `node scripts/platform-audit.js --json` at `2026-05-20T00:25:38Z` returned ready true with 0 open PRs, 0 open issues, 0 discussion maintainer-touch gaps, 0 answerable Q&A gaps, 0 conflicting PRs, and 0 dirty blockers across `affaan-m/ECC`, `affaan-m/agentshield`, `affaan-m/JARVIS`, `ECC-Tools/ECC-Tools`, and `ECC-Tools/ECC-website`. |
+| ECC platform audit recheck | `npm run platform:audit -- --json` at `2026-05-20T00:42:11Z` returned ready true with 0 open PRs, 0 open issues, 0 discussion maintainer-touch gaps, 0 answerable Q&A gaps, 0 conflicting PRs, 0 GitHub errors, and 0 dirty blockers across the same tracked repo set after AgentShield #94 merged. |
+| ECC-Tools #80/#81/#82 | PR #80 merged runtime-receipt failure-reason enforcement as `4efc8cc858022f84c844690f3298633b081c4398`; PR #81 preserved AgentShield fleet approval IDs as `1fbf635f492284f75ba7166c029c39eb8cc15794`; PR #82 rendered those approval IDs in hosted security review comments/check-runs as `7a7b4d096a176ae80b3a2076c09d45601e36013a`. |
+| ECC-Tools #83/#84 | PR #83 merged deterministic Linear external-ID reuse for deferred follow-ups as `b6b107f33961bef18a85fb619f3a976eb5d752dd`; PR #84 merged hosted AgentShield remediation sync to Linear as `73bac7058071c55cb30c6b8ac6db779b3660c02c`. Local validation covered focused route/client tests, typecheck, lint, full ECC-Tools test suite, and whitespace checks before merge; GitHub Verify, Security Audit, and Workers Builds passed. |
+| ECC-Tools #85/#86/#87 | PR #85 merged hosted job observability events as `1637e0f2bfa0a889387f2c20675680ccc5528123`; PR #86 merged hosted status observability readback as `5a9e94d3ff860307c3e7fd9fd065f0de2bd633dd`; PR #87 merged hosted depth-plan observability readback as `508fbc02b63cf1fcb5af2f3624608fa66e53b5d4`. Local validation for the final depth-plan readback slice passed the focused hosted depth-plan route test, full route suite (89/89), typecheck, lint, full ECC-Tools Vitest suite (683/683), and `git diff --check`; GitHub Verify, Security Audit, and Workers Builds passed before merge. |
+| ECC-Tools #88 | PR #88 merged authenticated hosted observability API readback as `c836ac3fb24ed7e2ae38cd61e41c9651ac9c00f8`. `GET /api/analysis/observability` now summarizes hosted events by event type and job for operator/dashboard readback, skips malformed stale KV records, and the deployment runbook includes the production smoke command. Local verification passed typecheck, lint, full ECC-Tools Vitest suite (686/686), and `git diff --check`; GitHub Verify, Security Audit, and Workers Builds passed before merge. |
+| AgentShield #94 | PR #94 merged Zed/VS Code adapter coverage as `4caee27acfadb50a4cd024e738b5c3cbd4b0bb03`. AgentShield now reports Zed and VS Code as first-class harness adapters, discovers `.zed/settings.json`, `.zed/tasks.json`, and `.zed` hook-code files, and flags `.zed/setup.mjs` in the AI-tool persistence IOC rule alongside `.vscode/setup.mjs`. Local verification passed typecheck, lint, focused scanner/rule tests, full `npm test` (1822 tests), `npm run build`, and `git diff --check`; GitHub checks passed across GitGuardian, scan suite, self-scan, self-scan examples, Node 18/20/22 CI, CodeRabbit, and Cubic after rerunning a transient artifact-upload failure. |
+| AgentShield #95 | PR #95 merged the `brace-expansion` Dependabot fix as `25d91f0002214c408da4ceaac7def20bad40ca10`. The lockfile now resolves vulnerable transitive `brace-expansion` 5.x entries to `5.0.6`, local `npm audit --audit-level=moderate` returns 0 vulnerabilities, and `gh api repos/affaan-m/agentshield/dependabot/alerts?state=open` returns `[]`. Local validation passed typecheck, lint, full `npm test` (1822 tests), build, audit, and whitespace checks; GitHub checks passed across Verify Node 18/20/22, self-scan, self-scan examples, Test GitHub Action, GitGuardian, CodeRabbit, and Cubic. |
+| Linear roadmap sync | Linear ITO-54 comment `74dcc101-3be5-4173-be13-62b80d54f569` and ECC Platform Roadmap project comment `348ea8f5-2a2d-46d9-a0fe-ed99653e7fe5` record the May 20 hosted observability status/depth-plan readback batch; Linear comments `291e2a4b-06e3-4672-a057-cdb141478161` and `b2d35de0-ca49-44cb-982a-ddec229e7691` add the #88 observability API readback; Linear ITO-49 comment `faed69dd-35f5-469d-acb5-ddde6a70d6a1` and project comment `70187c1e-d481-4181-b418-09bd65d54b5e` add the #94 AgentShield Zed/VS Code adapter evidence; Linear ITO-49 comment `371fc3e4-611f-4d20-a23f-67db1260b418`, ITO-57 comment `bd06e252-15c1-4256-b667-caa3f64f5968`, and project comment `22c2c388-2fd1-4dea-a939-6141f40c9a21` add the #95 AgentShield Dependabot alert closure; earlier comments on ITO-54, ITO-48, and the project record the #84 hosted remediation sync and #85 hosted observability event emission batches. |
+
+## May 20 Marketplace Pro Release-Gate Sync
+
+| Surface | Evidence |
+| --- | --- |
+| ECC-Tools #89 | PR #89 merged as `512bca6b99cdaa67058a6aa9a4e7e7f0b1d9873a` after Verify, Security Audit, and Workers Builds passed. It added `billing:kv-readback -- --select-ready-target --require-ready`, allowing operators to select a ready Marketplace Pro target internally without passing or printing the login. |
+| Live production readback | The 2026-05-20 Wrangler OAuth readback found ready-like Marketplace Pro records with webhook provenance, selected a target with both key families, seat and webhook readiness, no overage, and 0 blockers, with account details redacted. The old missing Marketplace Pro target-state blocker is cleared. |
+| ECC #2019 | PR #2019 merged as `30f60710d4e0424fc70d9bbdc105009db141d9d8`, syncing the selected-target readback evidence into the GA roadmap, rc.1 publication evidence, naming matrix, preview manifest, and operator dashboard. |
+| ECC-Tools #90 | PR #90 merged as `16a5bb33ee5ce7c31d2ad8d041e5afac03308f05` after Verify, Security Audit, and Workers Builds passed. It added the selected-target official announcement gate through `/api/billing/readiness?selectReadyTarget=1` and `npm run billing:announcement-gate -- --select-ready-target`, keeping the raw account login out of command logs. |
+| ECC #2020 | PR #2020 merged as `c2471fe5c535310f8a8008c9ed7ea9f6757b33f2`, syncing ECC-Tools #90 into the roadmap, publication evidence, naming matrix, preview manifest, publication readiness, release URL ledger, platform audit surfaces, and operator dashboard. |
+| ECC-Tools #91 | PR #91 merged as `72119a1acc6f5a0cd3bb5d90afd6e87fd1fefd05` after Verify, Security Audit, and Workers Builds passed. It added `--env-file` to the billing announcement and KV readback scripts for ignored local operator credential files, with tests proving sentinel secrets and account logins are not printed. |
+| ECC-Tools #92 | PR #92 merged as `18d80197be779619283e0b37e2952bac53819a07` after Verify, Security Audit, and Workers Builds passed. It added the non-breaking `INTERNAL_OPERATOR_API_SECRET` bearer accepted by privileged internal API routes without rotating the primary `INTERNAL_API_SECRET`, and the merged Worker was deployed to `api.ecc.tools`. |
+| May 20 live selected-target gate | Vault-backed Wrangler readback passed with Marketplace Pro state, target fingerprint `e953a74209fe`, both key families, webhook evidence, seat readiness, no overage, and 0 blockers. After rotating the operator bearer, `npm run billing:announcement-gate -- --preflight --select-ready-target` returned ready and `npm run billing:announcement-gate -- --select-ready-target` returned `announcementGateReady: true`, 0 required actions, 0 blockers, and audit summary 6 pass / 1 warn / 0 fail. |
+| ECC-Tools #93 | PR #93 merged as `d3d62df83fa075660fa4530c3e0edc311a4355fe`, recording the live billing announcement gate pass in the launch checklist and distribution roadmap while preserving final release/plugin/URL approval gates. |
+| Post-merge main CI | ECC GitHub Actions runs `26135974576`, `26136949698`, and `26138015245` completed successfully on `main` for `30f60710d4e0424fc70d9bbdc105009db141d9d8`, `c2471fe5c535310f8a8008c9ed7ea9f6757b33f2`, and `6e25458dbc15cd07cfb7a4e1f0b06f3eda41a043` across lint, coverage, security, validation, and the full OS/package-manager matrix. ECC-Tools main CI runs `26137280847`, `26138403065`, and `26138669148` completed successfully for `72119a1acc6f5a0cd3bb5d90afd6e87fd1fefd05`, `18d80197be779619283e0b37e2952bac53819a07`, and `d3d62df83fa075660fa4530c3e0edc311a4355fe`. |
+| Post-merge local gates | `npm run platform:audit -- --json` returned ready true with 0 PRs, 0 issues, 0 discussion gaps, and 0 dirty blockers; `npm run preview-pack:smoke -- --format json` returned ready true with digest `531328aaaa53` before the May 20 dashboard rollover and `eebb8a66c33e` after adding the May 20 dashboard artifact; `git diff --check HEAD~1..HEAD` was clean. |
+| Linear roadmap sync | Linear ITO-61 comment `467d148a-712a-4777-aad9-95593e9f1739` and ECC Platform Roadmap project comment `7642ee9c-3107-400c-a229-53e2895a8914` record ECC-Tools #89, ECC #2019, the green post-merge CI run, and the earlier internal bearer-token gate; Linear ITO-44 comment `a9297467-208a-41e4-8dbb-35f0dad5fe2b`, ITO-56 comment `5008b70b-cf98-43cd-a8d4-f098ba9b9780`, ITO-61 comment `5ebf0aaf-e2d3-4537-878f-484f49dcf87a`, and project reply `1c74a3d0-f8ca-4306-997e-a37c53d49f97` record the ECC #2020 selected-target announcement-gate sync; a new Linear sync should record ECC-Tools #92/#93 and the live gate pass. |
+| Remaining blocker | Native-payments billing evidence is ready as of the May 20 selected-target gate pass. Repeat KV readback and `billing:announcement-gate -- --select-ready-target` immediately before launch, and keep native-payments copy behind the final release, plugin, live URL, and owner-approval gates. |
+
+## Release And Growth Evidence
+
+| Gate | Command | Result |
+| --- | --- | --- |
+| Release-surface tests | `node tests/docs/ecc2-release-surface.test.js` | 28 passed, 0 failed |
+| Preview-pack smoke | `npm run preview-pack:smoke -- --format json` | Ready true; digest `eebb8a66c33e`; 33 required artifacts; 5 passed, 0 failed |
+| Release approval gate | `npm run release:approval-gate -- --format json` | Expected blocked; digest `ef8f49f727b7`; 4 passed, 2 failed; owner decisions and live URL readbacks remain approval-gated |
+| Operator dashboard | `npm run operator:dashboard -- --write docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-20.md` | Regenerated from the May 20 `main` baseline with platform audit ready true, 0 tracked PRs, 0 tracked issues, 0 discussion gaps, `$1,728/mo` current MRR, `$10,000/mo` target MRR, the release video suite marked current, Linear release-gate sync current, and top actions for plugin publication, notifications, outbound approval, AgentShield, and ECC Tools billing |
+| Supply-chain verification | `npm audit --audit-level=moderate`; `npm audit signatures`; `yarn install --immutable --mode=skip-build` | Current supply-chain refresh found 0 npm vulnerabilities, verified 254 registry signatures and 30 attestations, and accepted the Yarn lock after pinning `@types/node@25.7.0` plus refreshing `brace-expansion` to `5.0.6` / `1.1.14` |
+| Release video suite | `npm run release:video-suite -- --format json --summary` with `ECC_VIDEO_SOURCE_ROOT` and `ECC_VIDEO_RELEASE_SUITE_ROOT` | Ready true; 15/15 source assets present; 13/13 render, timeline, caption, EDL, and segment artifacts present; 12/12 publish-candidate outputs present with zero detected black-frame segments; primary rough render self-eval passed at 144.759 seconds, 1920x1080, 1 audio stream, and 106.78 MB |
+| Focused post-merge regression set | `node tests/hooks/detect-project-worktree.test.js`; `node tests/hooks/observe-subdirectory-detection.test.js`; `node tests/scripts/instinct-cli-projects.test.js`; `node tests/hooks/hooks.test.js` | 10/10, 6/6, 5/5, and 237/237 passed after PR #2009 merged |
+| GateGuard PR #2011 regression | `node tests/hooks/gateguard-fact-force.test.js`; `npm test`; `git diff --check main...HEAD` | 91/91 passed on the PR branch; full local suite passed 2560/2560 before merge; whitespace check passed; focused GateGuard suite passed again on current `main` |
+| Release approval gate PR #2013 validation | `npm test`; `npm run lint`; `git diff --check`; `npm run preview-pack:smoke -- --format json`; `npm run release:approval-gate -- --format json` | 2568/2568 tests passed before merge; lint and whitespace passed; preview pack stayed ready with digest `531328aaaa53`; release approval gate returned the expected blocked exit with digest `ef8f49f727b7` |
+| Full local suite | `node tests/run-all.js` | 2568 passed, 0 failed before PR #2013 merge |
+| PR #1998 CI | GitHub Actions run `26099020341` | Completed successfully for `d500de1e9f11c0446b6a1349bd98b522d31f9125`; all reported checks passed, including lint, validation, security scan, coverage, GitGuardian, CodeRabbit, Cubic, and the macOS/Ubuntu/Windows test matrix |
+| PR #1999 CI | GitHub Actions run `26100148726` | Completed successfully for `90584b6d5e5814bc2ad9a4cd651bebd043de989d`; lint, validation, security scan, coverage, GitGuardian, CodeRabbit, and the macOS/Ubuntu/Windows test matrix passed; Cubic completed neutral and did not block merge |
+| PR #2001 CI | GitHub Actions run `26102500291` | Completed successfully for `8148340ad14eb32c971346f0cb4cb9431ec0f5de`; required checks passed before merge |
+| PR #2002 CI | GitHub Actions run `26103853507` | Completed successfully before merge; required checks passed, Cubic remained non-blocking, and PR #2002 merged into `main` as `c7d662c3c68719e5ef0b5305ca3f6782b3214224` |
+| PR #2004 CI | GitHub Actions run `26105012698` | Completed successfully after rerunning the single failed Windows Node 18 yarn job; required checks passed, Cubic remained non-blocking, and PR #2004 merged into `main` as `ac7434ea8f39166b11e9d06ce64b38c4fb8d9202` |
+| PR #2005 CI | GitHub Actions run `26106321921` | Completed successfully with 37 completed jobs, 0 failed jobs, and PR #2005 merged into `main` as `d6022d6b8dc5ef1393cf18ae40ee58f646f3754e` |
+| PR #2008 CI | GitHub Actions run `26108473648` | Completed successfully across the required matrix before merge; non-blocking Cubic skipped after review |
+| Post-PR #2006 main CI | GitHub Actions run `26109953093` | Completed successfully with 37 completed jobs, 0 failed jobs, and `main` advanced to `98bd517451f38fa0150a53aab4234c2239a47b7e` |
+| PR #2009 CI | GitHub Actions run `26111313938` | Completed successfully with 37 completed jobs, 0 failed jobs after replacing the brittle fake-worktree regression fixture with a real `git worktree add` setup |
+| Post-PR #2009 main CI | GitHub Actions run `26111946778` | Completed successfully with 37 completed jobs, 0 failed jobs, and `main` advanced to `bc519e5b8ed42f26c0a5a611756e04351c323f21` |
+| Post-PR #2011 main CI | GitHub Actions run `26113695068` | Completed successfully with 37 completed jobs, 0 failed jobs, and `main` advanced to `14d88e517b0c56a80c1a6392b1cde2474948d29f` |
+| Post-PR #2013 main CI | GitHub Actions run `26128749863` | Completed successfully with `main` advanced to `9819626459a662773be7d0b1c18d82c1316b8c36` |
+| Post-PR #2019 main CI | GitHub Actions run `26135974576` | Completed successfully with `main` advanced to `30f60710d4e0424fc70d9bbdc105009db141d9d8` |
+| Post-PR #2020 main CI | GitHub Actions run `26136949698` | Completed successfully with `main` advanced to `c2471fe5c535310f8a8008c9ed7ea9f6757b33f2` |
+| ECC-Tools #91 main CI | GitHub Actions run `26137280847` | Completed successfully on ECC-Tools `main` with `72119a1acc6f5a0cd3bb5d90afd6e87fd1fefd05` after the env-file billing gate support merged |
+| ECC-Tools #92 main CI | GitHub Actions run `26138403065` | Completed successfully on ECC-Tools `main` with `18d80197be779619283e0b37e2952bac53819a07` after the operator bearer path merged |
+| ECC-Tools #93 main CI | GitHub Actions run `26138669148` | Completed successfully on ECC-Tools `main` with `d3d62df83fa075660fa4530c3e0edc311a4355fe` after the live billing announcement evidence merged |
+| Linear sync | Linear document `ecc-may-19-post-pr-2002-sync-64cef8f668e0` plus project comment `a6411e3a-8c8e-4a58-adba-687e77d4c543`; late-pass document `ecc-may-19-late-queue-zero-and-release-gate-sync-1c26f65e6b3f` plus project comment `d42bf0e2-7a8e-4934-9f3f-e281498ee805`; May 20 ITO-61 comment `467d148a-712a-4777-aad9-95593e9f1739` plus project comment `7642ee9c-3107-400c-a229-53e2895a8914`; May 20 ITO-44 comment `a9297467-208a-41e4-8dbb-35f0dad5fe2b`, ITO-56 comment `5008b70b-cf98-43cd-a8d4-f098ba9b9780`, ITO-61 comment `5ebf0aaf-e2d3-4537-878f-484f49dcf87a`, and project reply `1c74a3d0-f8ca-4306-997e-a37c53d49f97` | Project and issue lanes record PR #2002 evidence, discussion #2003 routing, owner-approval dashboard gate, and In Progress status for ITO-47, ITO-48, ITO-49, ITO-51, ITO-54, and ITO-56; the late-pass sync attaches PR #2013, ECC-Tools #79, and JARVIS #15/#16 evidence to ITO-44, ITO-50, ITO-54, ITO-56, and ITO-61; the May 20 sync attaches ECC-Tools #89/#90, ECC #2019/#2020 Marketplace Pro selected-target and selected-target announcement-gate evidence, and the remaining env-file/bearer-token gate to ITO-44, ITO-56, ITO-61, and the project |
+| Public-path sanitization | `node scripts/ci/validate-no-personal-paths.js` through local suite and CI | Passed |
+| Markdown and whitespace | `markdownlint` focused release docs plus `git diff --check` before PR #1999 | Passed |
+
+## Product And Positioning Evidence
+
+| Surface | Evidence |
+| --- | --- |
+| Canonical repo identity | Public URLs and release docs now use `https://github.com/affaan-m/ECC` where public links are needed |
+| Release claim | Release notes and launch collateral frame ECC as the harness-native operator system for agentic work, not a Claude-only config pack |
+| Video proof | `video-suite-production.md` gates the local rough render, timeline, captions, source inventory, publish-candidate clip set, self-eval, black-frame QA, and no-private-path publication rules |
+| Growth proof | `partner-sponsor-talks-pack.md` provides approval-gated copy for sponsors, partners, consulting, talks, podcasts, GitHub Discussion, and video CTAs |
+| Owner approval proof | `owner-approval-packet-2026-05-19.md` centralizes release, package, plugin, video, billing, social, and outbound decision gates |
+| Business baseline | Hypergrowth command center and partner pack use `$1,728/mo` current MRR, `$10,000/mo` target MRR, and `$8,272/mo` gap |
+| Operator dashboard | `operator-readiness-dashboard-2026-05-20.md` pulls the growth baseline into the same queue, publication, video, outbound, AgentShield, ECC Tools billing/env-file gate, Linear, and supply-chain control surface |
+| Linear progress proof | Linear project document `ecc-may-19-post-pr-2002-sync-64cef8f668e0` mirrors the post-PR #2002 state and records active lanes for launch materials, AgentShield, ECC Tools deep analysis, observability, and final release publication; Linear document `ecc-may-19-late-queue-zero-and-release-gate-sync-1c26f65e6b3f` adds the PR #2013 approval gate, ECC-Tools #79 redaction hardening, and JARVIS #15/#16 queue/deploy repair evidence; May 20 Linear comments `74dcc101-3be5-4173-be13-62b80d54f569`, `348ea8f5-2a2d-46d9-a0fe-ed99653e7fe5`, `291e2a4b-06e3-4672-a057-cdb141478161`, `b2d35de0-ca49-44cb-982a-ddec229e7691`, `faed69dd-35f5-469d-acb5-ddde6a70d6a1`, `70187c1e-d481-4181-b418-09bd65d54b5e`, `371fc3e4-611f-4d20-a23f-67db1260b418`, `bd06e252-15c1-4256-b667-caa3f64f5968`, `22c2c388-2fd1-4dea-a939-6141f40c9a21`, `a9297467-208a-41e4-8dbb-35f0dad5fe2b`, `5008b70b-cf98-43cd-a8d4-f098ba9b9780`, `5ebf0aaf-e2d3-4537-878f-484f49dcf87a`, and `1c74a3d0-f8ca-4306-997e-a37c53d49f97` add ECC-Tools hosted observability readback evidence, AgentShield adapter evidence, AgentShield Dependabot alert closure, and Marketplace selected-target announcement-gate evidence to ITO-44, ITO-49, ITO-54, ITO-56, ITO-57, ITO-61, and the project |
+
+## Current Publication Blockers
+
+- GitHub prerelease `v2.0.0-rc.1` is still not created in this pass.
+- npm `ecc-universal@2.0.0-rc.1` is still not published to the `next`
+  dist-tag.
+- Claude plugin tag and marketplace propagation remain approval-gated.
+- Codex repo-marketplace distribution is verified by prior evidence, but
+  official Plugin Directory publishing remains blocked on OpenAI submission or
+  listing evidence.
+- ECC Tools billing/native-payments evidence is no longer blocked by the
+  internal bearer-token path or selected-target announcement gate. Repeat
+  `billing:kv-readback -- --select-ready-target --require-ready` and
+  `billing:announcement-gate -- --select-ready-target` immediately before
+  launch, and keep the copy behind the final release, plugin, live URL, and
+  owner-approval gates.
+  ECC-Tools PR #89 (`512bca6`) added `billing:kv-readback --
+  --select-ready-target --require-ready`; its 2026-05-20 production run cleared
+  the old missing-target-state blocker without printing the account login.
+  ECC-Tools PR #90 (`16a5bb3`) added the selected-target official announcement
+  gate, so production preflight no longer needs a raw GitHub login.
+  ECC-Tools PR #91 (`72119a1`) added `--env-file` support for ignored local
+  billing credentials without printing loaded secrets or account logins.
+  ECC-Tools PR #92 (`18d8019`) added the non-breaking operator bearer path, and
+  ECC-Tools PR #93 (`d3d62df`) recorded the live gate pass.
+- Release notes, X, LinkedIn, GitHub release, GitHub Discussion, longform copy,
+  sponsor outreach, partner outreach, consulting copy, conference pitches, and
+  podcast pitches still need final live URLs plus human approval before posting
+  or sending.
+- Discord/community links still need a real invite or bot/guild credential path
+  before public docs should route users there.
+
+## Result
+
+The tracked public PR queue, issue queue, discussion queue, canonical ECC
+identity, release video suite, preview pack, growth outreach packet, per-project
+Claude Code adapter surface, continuous-learning project registry hygiene,
+GateGuard quoted git introspection fix, deterministic release approval gate,
+ECC-Tools billing-announcement redaction hardening, selected-target billing
+readback, selected-target announcement gate, billing gate env-file operator path,
+ECC-Tools hosted observability readback, AgentShield Zed/VS Code adapter coverage,
+AgentShield Dependabot alert closure, and JARVIS security/deploy queue repairs
+are current on May 20, 2026 for ECC `main` through
+`c2471fe5c535310f8a8008c9ed7ea9f6757b33f2`, ECC-Tools `main` through
+`72119a1acc6f5a0cd3bb5d90afd6e87fd1fefd05`, and AgentShield `main` through
+`25d91f0002214c408da4ceaac7def20bad40ca10`. The remaining video work is owner
+approval, upload, and public URL attachment, not render or QA production.
+
+This improves publication readiness but does not replace the approval-gated
+release, package, plugin, billing, Discord, and announcement steps in
+`publication-readiness.md`.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/publication-readiness.md

@@ -0,0 +1,149 @@
+# ECC v2.0.0-rc.1 Publication Readiness
+
+This checklist is the release gate for public publication surfaces. Do not use
+it as evidence by itself. Fill the evidence fields with fresh command output or
+URLs from the exact commit being released.
+
+For the current rc.1 naming decision and package/plugin publication path, see
+[`naming-and-publication-matrix.md`](naming-and-publication-matrix.md).
+For the May 18 release name, package, Claude plugin, Codex plugin, and
+publication-order gate, see
+[`release-name-plugin-publication-checklist-2026-05-18.md`](release-name-plugin-publication-checklist-2026-05-18.md).
+For the assembled rc.1 preview pack boundary, see
+[`preview-pack-manifest.md`](preview-pack-manifest.md).
+For the May 12 dry-run evidence pass, see
+[`publication-evidence-2026-05-12.md`](publication-evidence-2026-05-12.md).
+For the May 13 release-readiness evidence refresh, see
+[`publication-evidence-2026-05-13.md`](publication-evidence-2026-05-13.md).
+For the May 13 post-hardening evidence refresh after PR #1850 and PR #1851, see
+[`publication-evidence-2026-05-13-post-hardening.md`](publication-evidence-2026-05-13-post-hardening.md).
+For the May 15 queue, discussion, Linear roadmap, Mini Shai-Hulud/TanStack
+follow-up, scheduled supply-chain watch, no-lifecycle CI install hardening,
+GitHub Actions cache purge, AgentShield release-verification, billing-gate,
+AgentShield #86 evidence-pack provenance, and `ecc2` current-dir guard evidence
+refresh through PR #1941, see
+[`publication-evidence-2026-05-15.md`](publication-evidence-2026-05-15.md).
+For the May 16 queue cleanup, recsys skill merge, GateGuard issue triage,
+AgentShield #87 plugin-cache runtime-confidence evidence, AgentShield #88
+evidence-pack inspect/readback, AgentShield #89 evidence-pack fleet routing,
+AgentShield #90 fleet review items, AgentShield #91 checksum-backed policy
+export, AgentShield #92 checksum-verified policy promotion, ECC-Tools #76
+fleet-summary consumption, ECC-Tools #77 hosted finding evidence paths,
+ECC-Tools #78 harness policy-route linking, operator dashboard refresh, and
+combined final-gate rerun on current `main`, see
+[`publication-evidence-2026-05-16.md`](publication-evidence-2026-05-16.md).
+For the May 17 queue cleanup, Japanese localization merge, Dependabot
+TypeScript and Node type merges, post-merge ja-JP lint repair, Mini
+Shai-Hulud/TanStack local protection recheck, legacy-tail and Linear progress
+routing, deterministic preview-pack smoke gate, and current operator dashboard
+refresh, see
+[`publication-evidence-2026-05-17.md`](publication-evidence-2026-05-17.md).
+For the May 18 current-head queue, workflow-security/metrics/uncloud merge
+batch, PR #1978 review/closure, Mini Shai-Hulud/TanStack local and home
+protection recheck, npm no-lifecycle install/audit/signature gates,
+AgentShield project scan, AgentShield `840952a` enterprise/IOC evidence mirror,
+release OIDC publishing-scope hardening, workflow normalization, later
+dashboard/publication-readiness refreshes through `67e63e63`, work-items sync,
+Linear progress comments, ITO-46 closure, operator dashboard refresh, and
+current-head CI/security scan success through the May 19 identity, video, and
+growth-pack merge batch, see
+[`publication-evidence-2026-05-19.md`](publication-evidence-2026-05-19.md).
+For the operator-facing prompt-to-artifact readiness dashboard from the same
+May 16 pass, see
+[`operator-readiness-dashboard-2026-05-15.md`](operator-readiness-dashboard-2026-05-15.md).
+For the May 17 operator dashboard refresh, see
+[`operator-readiness-dashboard-2026-05-17.md`](operator-readiness-dashboard-2026-05-17.md).
+For the May 18 operator dashboard refresh, see
+[`operator-readiness-dashboard-2026-05-18.md`](operator-readiness-dashboard-2026-05-18.md).
+
+For the May 19 hypergrowth/operator dashboard, see
+[`operator-readiness-dashboard-2026-05-19.md`](operator-readiness-dashboard-2026-05-19.md).
+The current May 20 Marketplace Pro release-gate operator dashboard is
+[`operator-readiness-dashboard-2026-05-20.md`](operator-readiness-dashboard-2026-05-20.md).
+For the final owner decision sheet across release, npm, plugin, video, billing,
+social, and outbound approvals, see
+[`owner-approval-packet-2026-05-19.md`](owner-approval-packet-2026-05-19.md).
+For the May 26 live/pending release URL ledger after the GitHub prerelease and
+npm `next` readbacks, see
+[`release-url-ledger-2026-05-19.md`](release-url-ledger-2026-05-19.md).
+
+## Release Identity Matrix
+
+| Surface | Expected value | Source of truth | Fresh check | Evidence artifact | Owner | Status |
+| --- | --- | --- | --- | --- | --- | --- |
+| Product name | ECC | `README.md`, plugin manifests, release notes | `rg -n "^# ECC\|displayName.*ECC\|affaan-m/ECC" README.md .codex-plugin/plugin.json docs/releases/2.0.0-rc.1` | `release-name-plugin-publication-checklist-2026-05-18.md` plus `release-url-ledger-2026-05-19.md` | Release owner | Evidence recorded |
+| GitHub repo | `affaan-m/ECC` | Git remote and release URLs | `git remote get-url origin` | `release-url-ledger-2026-05-19.md` | Release owner | Evidence recorded |
+| Git tag | `v2.0.0-rc.1` | GitHub releases | `gh release view v2.0.0-rc.1 --repo affaan-m/ECC` | Live prerelease at <https://github.com/affaan-m/ECC/releases/tag/v2.0.0-rc.1>; prerelease true, draft false | Release owner | Evidence recorded |
+| npm package | `ecc-universal` | `package.json` | `node -p "require('./package.json').name"` | `publication-evidence-2026-05-12.md` | Package owner | Evidence recorded |
+| npm version | `2.0.0-rc.1` | `VERSION`, `package.json`, lockfiles | `node -p "require('./package.json').version"` | `publication-evidence-2026-05-12.md` | Package owner | Evidence recorded |
+| npm dist-tag | `next` for rc, `latest` only for GA | npm registry | `npm view ecc-universal dist-tags --json` | Registry has `latest: 1.10.0` and `next: 2.0.0-rc.1` | Package owner | Evidence recorded |
+| Claude plugin slug | `ecc` / `ecc@ecc` install path | `.claude-plugin/plugin.json`, `.claude-plugin/marketplace.json` | `node tests/hooks/hooks.test.js` | `publication-evidence-2026-05-12.md` | Plugin owner | Evidence recorded |
+| Claude plugin manifest | `2.0.0-rc.1`, no unsupported `agents` or explicit `hooks` fields | `.claude-plugin/plugin.json`, `.claude-plugin/PLUGIN_SCHEMA_NOTES.md` | `claude plugin validate .claude-plugin/plugin.json` | `publication-evidence-2026-05-12.md` | Plugin owner | Evidence recorded |
+| Codex plugin manifest | `2.0.0-rc.1` with shared skill source | `.codex-plugin/plugin.json` | `node tests/docs/ecc2-release-surface.test.js` | `publication-evidence-2026-05-12.md` | Plugin owner | Evidence recorded |
+| Codex repo marketplace | `ecc@2.0.0-rc.1` exposed through `.agents/plugins/marketplace.json` | `.agents/plugins/marketplace.json`, `.codex-plugin/README.md` | `HOME="$(mktemp -d)" codex plugin marketplace add <local-checkout>` | `publication-evidence-2026-05-15.md` | Plugin owner | Repo-marketplace path verified; do not claim official Plugin Directory listing before OpenAI submission evidence |
+| OpenCode package | `ecc-universal` plugin module | `.opencode/package.json`, `.opencode/index.ts` | `npm run build:opencode` | `publication-evidence-2026-05-12.md` | Package owner | Evidence recorded |
+| Agent metadata | `2.0.0-rc.1` | `agent.yaml`, `.agents/plugins/marketplace.json` | `node tests/scripts/catalog.test.js` | `publication-evidence-2026-05-12.md` | Release owner | Evidence recorded |
+| Migration copy | rc.1 upgrade path, not GA claim | `release-notes.md`, `quickstart.md`, `HERMES-SETUP.md` | `npx markdownlint-cli '**/*.md' --ignore node_modules` | `publication-evidence-2026-05-13.md` | Docs owner | Evidence recorded |
+
+## Publication Gates
+
+| Gate | Required evidence | Fresh check | Blocker field | Owner | Status |
+| --- | --- | --- | --- | --- | --- |
+| GitHub release | Tag exists, release notes use final URLs, assets attached if needed | `gh release view v2.0.0-rc.1 --json tagName,url,isPrerelease` | `Ready: v2.0.0-rc.1 prerelease is live; remaining plugin, video, billing, and outbound URLs are still gated` | Release owner | Evidence recorded |
+| npm package | `npm pack --dry-run` has expected files, version matches, rc goes to `next` | `npm pack --dry-run`; `npm view ecc-universal name version dist-tags --json`; `npm view ecc-universal@2.0.0-rc.1 name version dist.tarball dist.integrity time --json` | `Ready: ecc-universal@2.0.0-rc.1 is live on next; latest remains 1.10.0` | Package owner | Evidence recorded |
+| Claude plugin | Manifest validates, marketplace JSON points to public repo, install docs match slug | `claude plugin validate .claude-plugin/plugin.json`; `claude plugin tag .claude-plugin --dry-run`; isolated temp-home install smoke | `Blocker: real tag creation/push requires approval` | Plugin owner | Clean-checkout dry-run and install smoke recorded |
+| Codex plugin | Manifest version matches package and docs, repo marketplace points at the plugin root, and OpenAI's current official Plugin Directory status is recorded | `node tests/docs/ecc2-release-surface.test.js`; `node tests/plugin-manifest.test.js`; `codex plugin marketplace add --help`; temp-home `codex plugin marketplace add <local-checkout>` | `Blocker: official Plugin Directory listing requires OpenAI submission/listing evidence` | Plugin owner | Repo-marketplace distribution verified; official directory pending |
+| OpenCode package | Build output is regenerated from source and package metadata is current | `npm run build:opencode` | `Blocker: none for local build; public distribution still follows npm/plugin release` | Package owner | Evidence recorded |
+| ECC Tools billing reference | Any billing claim links to verified Marketplace/App state | `env -u GITHUB_TOKEN gh repo view ECC-Tools/ECC-Tools --json nameWithOwner,isPrivate,viewerPermission` plus internal `/api/billing/readiness?selectReadyTarget=1` readback using the operator bearer path | `Ready: ECC-Tools #92 main CI and ECC-Tools #93 main CI passed; live selected-target readback returned announcementGate.ready === true on 2026-05-20; repeat before payment announcement` | ECC Tools owner | Billing evidence ready; final copy still waits on release/plugin/live URL approvals |
+| Announcement copy | X, LinkedIn, GitHub release, and longform copy point to live URLs | placeholder-marker scan and `release-url-ledger-2026-05-19.md` | `Blocker: GitHub and npm links are live; remaining plugin, video, billing, and outbound URLs still need approval/readback` | Release owner | URL ledger recorded; final URLs pending |
+| Privileged workflow hardening | Release and maintenance workflows avoid persisted checkout tokens | `node scripts/ci/validate-workflow-security.js` | `Blocker:` | Release owner | Evidence recorded in post-hardening refresh |
+
+## Required Command Evidence
+
+Record the exact commit SHA and command output before any publication action:
+
+| Evidence | Command | Required result | Recorded output |
+| --- | --- | --- | --- |
+| Clean release branch | `git status --short --branch` | On intended release commit; no unrelated files | Current May 20 baseline `c2471fe5c535310f8a8008c9ed7ea9f6757b33f2`: `## main...origin/main`; repeat from the exact final publication commit before release |
+| Preview-pack smoke | `npm run preview-pack:smoke` | Preview pack artifacts, Hermes boundary, final verification command list, and publication blockers pass | `publication-evidence-2026-05-19.md`: ready yes, digest `eebb8a66c33e`, 33 artifacts, 5 passed, 0 failed; repeat in the final strict clean-checkout release pass |
+| Release approval gate | `npm run release:approval-gate -- --format json` | Ready true only after owner decision rows are approved, live release/package/plugin/video/billing URLs are recorded, and launch/outbound copy has no placeholders or private paths | Current May 26 state is intentionally blocked because plugin/video/billing/outbound owner decisions and URL readbacks remain approval-gated |
+| Harness audit | `npm run harness:audit -- --format json` | 80/80 passing | Current release gate: 80/80 across 8 applicable categories, 0 top actions |
+| Adapter scorecard | `npm run harness:adapters -- --check` | PASS | Current release gate: PASS, 11 adapters |
+| Observability readiness | `npm run observability:ready` | 21/21 passing | Current release gate: 21/21, ready true |
+| Release safety gate | `npm run observability:ready -- --format json` | Release Safety category passing with publication readiness, supply-chain, workflow security, package surface, and release-surface evidence | Current release gate keeps Release Safety passing at 3/3; repeat the JSON gate from the exact final release commit |
+| Supply-chain verification | `npm audit --audit-level=moderate`; `npm audit signatures`; `yarn install --immutable --mode=skip-build`; `cd ecc2 && cargo audit -q`; Dependabot alerts; GitGuardian Security Checks | 0 vulnerabilities/alerts, registry signatures verified, package-manager locks accepted, GitGuardian clean | Current supply-chain branch: `npm audit` found 0 vulnerabilities; `npm audit signatures` verified 254 registry signatures and 30 attestations; Yarn immutable install accepted the lock after pinning `@types/node@25.7.0` and moving `brace-expansion` to `5.0.6` / `1.1.14`; PR #2008 CI `26108473648`, post-PR #2006 main CI `26109953093`, PR #2009 CI `26111313938`, and post-PR #2009 main CI `26111946778` completed with 0 failures |
+| Root suite | `node tests/run-all.js` | 0 failures | Current May 19 local suite: 2568 passed, 0 failed before PR #2013 merged; post-PR #2009 focused regressions also passed for worktree detection, observe subdirectory/global fallback, project maintenance CLI, and the hooks suite |
+| Markdown lint | `npx markdownlint-cli '**/*.md' --ignore node_modules` | 0 failures | Current release gate: focused lint passed for `publication-readiness.md`, `publication-evidence-2026-05-19.md`, and `docs/ECC-2.0-GA-ROADMAP.md` |
+| Package surface | `node tests/scripts/npm-publish-surface.test.js` | 0 failures; no Python bytecode in npm tarball | Current release gate: 2/2 passed |
+| Release surface | `node tests/docs/ecc2-release-surface.test.js` | 0 failures | Current release gate: 27/27 passed after refreshing the discussion-count assertion to the post-PR #2005 baseline |
+| Optional Rust surface | `cd ecc2 && cargo test` | 0 failures or explicit deferral | `publication-evidence-2026-05-16.md`: 462/462 passed, existing warnings only |
+| Queue baseline | `node scripts/platform-audit.js --json` across trunk, AgentShield, JARVIS, ECC Tools, and ECC website | Under 20 open PRs and under 20 open issues | Current May 20 baseline after PR #2020: platform audit ready true, 0 open PRs, 0 open issues, 0 discussion gaps, 0 conflicting PRs, and 0 blocking dirty files across tracked repos |
+| Discussion baseline | `node scripts/platform-audit.js --json` and `node scripts/discussion-audit.js --json` | No unmanaged active discussion queue and no answerable Q&A missing an accepted answer | Post-PR #2005 baseline: platform audit sampled 59 trunk discussions, 0 needing maintainer touch, 0 answerable discussions missing accepted answer; `docs/architecture/discussion-response-playbook.md` records response templates and security escalation rules |
+| Linear roadmap | Linear project and issue readback | Detailed roadmap exists with release, security, AgentShield, ECC Tools, legacy, and observability lanes | May 18 Linear comments include ITO-57 `3fe5b2b7-c4fe-401c-a317-b40d72119cb3` and ITO-44 `fb4a4f33-6c2d-421a-bbdb-63cfad3e3ee4`; earlier evidence records the project and 16 issue lanes |
+| Operator readiness dashboard | `npm run operator:dashboard -- --json` | Current queue state mapped to macro-goal deliverables and incomplete gaps | Current May 20 dashboard is refreshed from the post-PR #2020 baseline; platform audit ready true, 0 open PRs, 0 open issues, 0 discussion gaps, 0 dirty files, release video suite current, selected-target billing/env-file path mirrored, and publication gates still approval-gated |
+| Release URL ledger | `docs/releases/2.0.0-rc.1/release-url-ledger-2026-05-19.md` plus placeholder-marker scan | Live links and approval-gated links are separated before announcement copy is posted | Ledger records public repo/docs/GitHub prerelease/npm/OpenAI Codex documentation URLs and blocks plugin/video/billing/social URLs until approval-gated checks pass |
+| Release name and plugin publication checklist | `docs/releases/2.0.0-rc.1/release-name-plugin-publication-checklist-2026-05-18.md` | Name/package/plugin values are frozen, final-release commands are listed, and Claude/Codex publication paths cite current official docs | Checklist keeps `ECC`, `ecc-universal`, and plugin slug `ecc` for rc.1; no npm rename, npm publish, plugin tag, official listing, billing claim, or announcement before final evidence |
+
+## Do Not Publish If
+
+- `main` has unreviewed release-surface changes after the evidence was recorded.
+- `npm view ecc-universal dist-tags --json` contradicts the intended rc/GA tag.
+- Claude plugin validation is unavailable or no clean-checkout install smoke
+  test is recorded for the intended release commit.
+- Release notes or announcement drafts still contain placeholder URLs,
+  `TODO`, `TBD`, private workspace paths, or personal operator references.
+- Billing, Marketplace, or plugin-submission copy claims a live surface before
+  the live URL exists.
+- Stale PR salvage work is mid-flight on the same branch.
+
+## Announcement Order
+
+1. Merge the release-version PR.
+2. Record the required command evidence from the release commit.
+3. Verify the GitHub prerelease readback.
+4. Verify npm still points rc.1 at `next` and not `latest`.
+5. Submit or update plugin marketplace surfaces.
+6. Regenerate the release URL ledger and update release notes with final live
+   URLs.
+7. Publish GitHub release copy.
+8. Publish X, LinkedIn, and longform copy only after the public URLs work.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/quickstart.md

@@ -0,0 +1,79 @@
+# ECC v2.0.0-rc.1 Quickstart
+
+This path is for a new contributor who wants to verify the release surface before touching feature work.
+
+## Clone
+
+```bash
+git clone https://github.com/affaan-m/ECC.git
+cd ECC
+```
+
+Start from a clean checkout. Do not copy private operator state, raw workspace exports, tokens, or local Hermes files into the repo.
+
+## Install
+
+```bash
+npm ci
+```
+
+This installs the Node-based validation and packaging toolchain used by the public release surface.
+
+To install the rc.1 package from npm instead of working from a checkout:
+
+```bash
+npm install ecc-universal@next
+```
+
+`next` currently resolves to `ecc-universal@2.0.0-rc.1`; `latest` remains on
+`1.10.0` during the release-candidate window.
+
+## Verify
+
+```bash
+node tests/run-all.js
+```
+
+Expected result: every test passes with zero failures. For release-specific drift, run the focused check:
+
+```bash
+node tests/docs/ecc2-release-surface.test.js
+```
+
+Then check the local observability surface:
+
+```bash
+npm run observability:ready
+```
+
+This runs the [observability readiness gate](../../architecture/observability-readiness.md)
+for loop status, session traces, harness audit, and ECC2 tool-risk logs.
+
+## First Skill
+
+Read `skills/hermes-imports/SKILL.md` first.
+
+It shows the intended ECC 2.0 pattern:
+
+- take a repeated operator workflow
+- remove credentials, private paths, raw workspace exports, and personal memory
+- keep the durable workflow shape
+- publish the sanitized result as a reusable `SKILL.md`
+
+Do not start by importing a private Hermes workflow wholesale. Start by distilling one reusable skill.
+
+## Switch Harness
+
+Use the same skill source across harnesses:
+
+- Claude Code consumes ECC through the Claude plugin and native hooks.
+- Codex consumes ECC through `AGENTS.md`, `.codex-plugin/plugin.json`, and MCP reference config.
+- OpenCode consumes ECC through the OpenCode package/plugin surface.
+
+The portable unit is still `skills/*/SKILL.md`. Harness-specific files should load or adapt that source, not redefine the workflow.
+
+## Next Docs
+
+- [Hermes setup](../../HERMES-SETUP.md)
+- [Cross-harness architecture](../../architecture/cross-harness.md)
+- [Release notes](release-notes.md)

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/release-name-plugin-publication-checklist-2026-05-18.md

@@ -0,0 +1,120 @@
+# ECC v2.0.0-rc.1 Release Name And Plugin Publication Checklist
+
+Snapshot date: 2026-05-18. Canonical repo decision refreshed 2026-05-19
+after the public repo rename to `affaan-m/ECC`; release/package state refreshed
+2026-05-26 after the GitHub prerelease and npm `next` readbacks succeeded.
+
+This checklist is the operator gate for release naming, package publication,
+and Claude/Codex plugin distribution. It is not a publication action by itself.
+Run it from the exact release commit before creating tags, publishing npm,
+submitting marketplace forms, or posting announcements.
+
+## Fixed rc.1 Decision
+
+Ship `v2.0.0-rc.1` as **ECC**.
+
+- Keep the GitHub repo at `affaan-m/ECC`.
+- Keep the npm package as `ecc-universal`.
+- Keep Claude and Codex plugin slugs as `ecc`.
+- Publish the npm prerelease on the `next` dist-tag, not `latest`.
+- Do not rename the npm package to `ecc` or `@affaan-m/ecc` before rc.1.
+- Treat `affaan-m/ECC` as the canonical public repo for rc.1 and GA release
+  copy.
+
+Reasons:
+
+- `ecc-universal` is the current working install and package surface.
+- `ecc` on npm is occupied by an unrelated elliptic-curve package.
+- `@affaan-m/ecc` is unclaimed on npm, but would require a migration plan.
+- `affaan-m/ECC` is now the live public GitHub repo.
+- Claude and Codex already expose the desired short namespace as `ecc`.
+
+## Current Surface Evidence
+
+| Surface | Current value | Evidence command | Current result | Release action |
+| --- | --- | --- | --- | --- |
+| Git commit | `67e63e63f9bfd074bd6a21bf6bac71f3dfefa58b` | `git rev-parse HEAD` | Recorded from clean `main` before this ITO-46 evidence refresh | Re-run from final release commit |
+| GitHub repo | `affaan-m/ECC` | `git remote get-url origin` | `https://github.com/affaan-m/ECC.git` | Keep for rc.1 and GA |
+| npm package | `ecc-universal@2.0.0-rc.1` local and registry next, `1.10.0` registry latest | `node -p "require('./package.json').name + '@' + require('./package.json').version"` and `npm view ecc-universal name version dist-tags --json` | Local rc.1 ready; registry `next` points to `2.0.0-rc.1`; `latest` remains `1.10.0` | Keep rc.1 on `next`; do not move to `latest` before GA approval |
+| Exact npm short name | `ecc` | `npm view ecc name version description repository.url --json` | Occupied by unrelated `ecc@0.0.2` | Do not use |
+| Scoped npm short name | `@affaan-m/ecc` | `npm view @affaan-m/ecc name version --json` | 404 | Candidate only after migration plan |
+| Claude plugin | `ecc@2.0.0-rc.1` | `claude plugin validate .claude-plugin/plugin.json`; `claude plugin validate .`; `claude plugin tag .claude-plugin --dry-run` | Validation passed on Claude Code `2.1.143`; full plugin validation has one expected root `CLAUDE.md` context warning; dry run would create `ecc--v2.0.0-rc.1` | Run dry-run tag again from the final commit, then tag/push only after approval |
+| Claude marketplace | `.claude-plugin/marketplace.json` | `claude plugin marketplace add --help`; Anthropic plugin marketplace docs | GitHub repo, git URL, remote marketplace JSON, and local path marketplace sources are supported | Verify post-tag marketplace install/update path after final evidence |
+| Codex plugin | `ecc@2.0.0-rc.1` | `node tests/plugin-manifest.test.js`; `codex plugin marketplace add --help`; OpenAI Codex plugin docs | Plugin manifest passed 54/54; local and GitHub-ref repo marketplace smokes passed on Codex CLI `0.131.0` | Use repo marketplace for rc.1; do not claim official directory listing until OpenAI publishing path is available |
+| OpenCode package | `ecc-universal@2.0.0-rc.1` | `node -p "require('./.opencode/package.json').name + '@' + require('./.opencode/package.json').version"` | Matches rc.1 package identity | Follow npm package publication |
+| Billing claim | ECC Tools selected-target billing evidence ready | ECC Tools billing gate and Marketplace account readback | May 20 selected-target readback and live selected-target announcement gate passed with `announcementGateReady: true`; repeat immediately before announcement | Do not announce native payments until final release/plugin/live URL approvals are green |
+
+## Required Gate
+
+Run these checks from the final release commit and paste the exact output into
+a fresh `publication-evidence-YYYY-MM-DD.md` file before release actions:
+
+```bash
+git status --short --branch
+git rev-parse HEAD
+git remote get-url origin
+npm view ecc name version description repository.url --json
+npm view @affaan-m/ecc name version --json
+npm view ecc-universal name version dist-tags --json
+node tests/plugin-manifest.test.js
+node tests/docs/ecc2-release-surface.test.js
+claude plugin validate .claude-plugin/plugin.json
+claude plugin tag .claude-plugin --dry-run
+codex plugin marketplace add --help
+HOME="$(mktemp -d)" codex plugin marketplace add ./
+HOME="$(mktemp -d)" codex plugin marketplace add affaan-m/ECC --ref "$(git rev-parse HEAD)"
+npm pack --dry-run --json
+npm publish --tag next --dry-run
+npm run build:opencode
+npm run preview-pack:smoke
+npm run release:approval-gate -- --format json
+```
+
+If a command is unavailable on the release machine, record the exact error and
+keep the related publication action blocked.
+
+## Publication Order
+
+| Step | Action | Required evidence | Stop condition |
+| --- | --- | --- | --- |
+| 1 | Freeze name and version | Package, Claude plugin, Codex plugin, OpenCode package, `VERSION`, and release docs all say `2.0.0-rc.1` | Any `preview`/`rc.1` mismatch |
+| 2 | Verify clean release branch | `git status --short --branch` shows only the intended release commit and no unrelated drift | Any unexplained dirty file |
+| 3 | Verify package and plugin manifests | `node tests/plugin-manifest.test.js` and `node tests/docs/ecc2-release-surface.test.js` pass | Manifest or release-surface failure |
+| 4 | Dry-run package surface | `npm pack --dry-run --json`; `npm publish --tag next --dry-run` | Missing files, wrong dist-tag, or publish dry-run failure |
+| 5 | Dry-run Claude distribution | `claude plugin validate`; `claude plugin tag .claude-plugin --dry-run`; marketplace source/help evidence | Validation, tag, or install-smoke failure |
+| 6 | Verify Codex repo marketplace | `codex plugin marketplace add --help`; temp-home local and GitHub-ref repo marketplace add smoke; OpenAI official directory status recorded | Missing repo marketplace or unverified official-directory status |
+| 7 | Verify OpenCode package | `npm run build:opencode` | Build failure |
+| 8 | Regenerate release URL ledger | Live and approval-gated URLs separated in `release-url-ledger-YYYY-MM-DD.md` | Placeholder, private URL, or announcement URL drift |
+| 9 | Verify GitHub prerelease | `gh release view v2.0.0-rc.1 --json tagName,url,isPrerelease` | Missing URL or wrong prerelease flag |
+| 10 | Verify npm rc | `npm view ecc-universal version dist-tags --json` shows rc.1 on `next` and latest still on GA/stable | rc.1 lands on `latest` or registry output is unclear |
+| 11 | Publish/plugin-submit | Claude official submission and Codex repo marketplace evidence recorded | Form not submitted, listing not visible, or docs status changed |
+| 12 | Announce | X, LinkedIn, GitHub release, and longform copy use final live URLs | Any final URL is still pending |
+
+## Do Not Proceed
+
+- Do not publish an additional npm build before `npm pack --dry-run --json` is
+  captured from the final release commit.
+- Do not create or push Claude plugin tags before `claude plugin tag
+  .claude-plugin --dry-run` passes from the final release commit.
+- Do not claim an official Codex Plugin Directory listing unless OpenAI
+  documents a public submission path or confirms the plugin has been listed.
+- Do not announce billing, Marketplace, or native payments until ECC Tools live
+  Marketplace account readback returns ready.
+- Do not rename the npm package until rc.1 is published and a migration guide
+  maps old install names to new names.
+- Do not post social copy while any required plugin, video, billing, or
+  outbound URL is still approval-gated.
+
+## External Distribution Sources
+
+- Anthropic Claude Code plugin docs: `https://code.claude.com/docs/en/plugins`
+- Anthropic Claude Code marketplace docs:
+  `https://code.claude.com/docs/en/plugin-marketplaces`
+- OpenAI Codex plugin docs:
+  `https://developers.openai.com/codex/plugins/build#add-a-marketplace-from-the-cli`
+
+As of this snapshot, Anthropic documents self-hosted marketplace distribution
+through GitHub, git URL, remote marketplace JSON, and local path sources.
+OpenAI documents repo/personal marketplace distribution for Codex and describes
+an official Plugin Directory, but ECC has not submitted or received an official
+directory listing in this pass.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/release-notes.md

@@ -0,0 +1,124 @@
+# ECC v2.0.0-rc.1 Release Notes
+
+## Positioning
+
+ECC v2.0.0-rc.1 is the first release-candidate surface for ECC as a cross-harness operating system for agentic work.
+
+Claude Code remains a core target. Codex, OpenCode, Cursor, Gemini, and other harnesses are treated as execution surfaces that can share the same skills, rules, MCP conventions, and operator workflows. ECC is the reusable substrate; Hermes is documented as the operator shell that can sit on top of that layer.
+
+## What Changed
+
+- Added the sanitized Hermes setup guide to the public release story.
+- Added launch collateral in-repo so the release can ship from one reviewed surface.
+- Clarified the split between ECC as the reusable substrate and Hermes as the operator shell.
+- Documented the cross-harness portability model for skills, hooks, MCPs, rules, and instructions.
+- Added a Hermes import playbook for turning local operator patterns into publishable ECC skills.
+- Added Zed as a project-local planning/install target while keeping BYOK and OpenRouter secrets outside ECC-managed project files.
+- Added command-registry coverage, platform audit, discussion audit, operator dashboard, Linear progress readiness, and preview-pack smoke gates.
+- Added a local [observability readiness gate](../../architecture/observability-readiness.md) for loop status, session traces, harness audit, and ECC2 tool-risk logs.
+- Added the public teaser [Itô prediction-market skill pack](ito-prediction-market-skill-pack.md)
+  for read-only basket research, comparison, oracle-style market intelligence,
+  and risk review. Live Itô API access remains gated and separate from ECC
+  Tools billing.
+- Added the rollout-derived optimization skill pack: parallel execution,
+  benchmark loops, data-throughput acceleration, latency-critical systems, and
+  recursive decision ledgers.
+- Refreshed the release-readiness evidence after the May 2026 Mini
+  Shai-Hulud/TanStack campaign follow-up, including full-campaign AgentShield
+  IOC coverage, queue-zero/discussion checks, a detailed Linear roadmap gate,
+  the May 18 operator dashboard snapshot, and a live/pending release URL
+  ledger for announcement gating.
+- Published `ecc-universal@2.0.0-rc.1` to npm on the `next` dist-tag. The
+  `latest` tag remains on `1.10.0` during the rc.1 window.
+
+## Since v1.10.0
+
+The rc.1 surface now includes the main 2.0 direction rather than one isolated
+feature branch:
+
+- cross-harness substrate work for Claude Code, Codex, OpenCode, Cursor,
+  Gemini, Zed, and terminal-only workflows;
+- stronger package and plugin publication surfaces for npm, Claude plugin,
+  Codex repo-marketplace, OpenCode, and agent metadata;
+- operator gates for PRs, issues, discussions, stale legacy work, Linear
+  progress, release evidence, and dashboard repeatability;
+- supply-chain hardening after the Mini Shai-Hulud/TanStack campaign,
+  including IOC scanning, no-lifecycle CI installs, advisory-source refresh,
+  npm audit/signature checks, and user-level AI-tool persistence targets;
+- AgentShield enterprise-roadmap mirrors for package-manager hardening,
+  evidence-pack provenance, policy export, policy promotion, fleet routing,
+  and GitHub Action output telemetry;
+- ECC Tools roadmap mirrors for hosted analysis, fleet-summary consumption,
+  finding evidence paths, harness policy-route linking, hosted promotion judge
+  audit traces, billing announcement preflight, and production Marketplace
+  readback state;
+- documentation expansion, Japanese localization, zh-CN to ja-JP parity
+  repair, and dependency readiness through TypeScript 6 and Node type updates;
+- launch collateral for GitHub release copy, X, LinkedIn, article outline,
+  Telegram/Hermes handoff, demo prompts, partner/sponsor/talk outreach, and
+  the approval-gated launch checklist.
+- gated Itô skill distribution as a public workflow teaser, not a live trading
+  claim or a merge of ECC Tools and Itô ownership.
+- a release URL ledger that separates links which already resolve from links
+  that must wait for the plugin tag/directory, video upload, and ECC Tools
+  billing readback.
+
+## Why This Matters
+
+ECC is no longer only a Claude Code plugin or config bundle.
+
+The system now has a clearer shape:
+
+- reusable skills instead of one-off prompts
+- hooks and tests for workflow discipline
+- MCP-backed access to docs, code, browser automation, and research
+- cross-harness install surfaces for Claude Code, Codex, OpenCode, Cursor, and related tools
+- Hermes as an optional operator shell for chat, cron, handoffs, and daily work routing
+
+## Release Candidate Boundaries
+
+This is a release candidate, not the final GA claim.
+
+What ships in this surface:
+
+- public Hermes setup documentation
+- release notes and launch collateral
+- cross-harness architecture documentation
+- Hermes import guidance for sanitized operator workflows
+- publication-readiness evidence for queue state, discussion state, Linear roadmap coverage, operator dashboard status, and supply-chain follow-up
+- preview-pack smoke evidence proving the public pack is assembled without private Hermes state
+
+What stays local:
+
+- secrets, OAuth tokens, and API keys
+- private workspace exports
+- personal datasets
+- operator-specific automations that have not been sanitized
+- deeper CRM, finance, and Google Workspace playbooks
+
+## Upgrade Motion
+
+1. Follow the [rc.1 quickstart](quickstart.md).
+2. Read the [Hermes setup guide](../../HERMES-SETUP.md).
+3. Review the [cross-harness architecture](../../architecture/cross-harness.md).
+4. Run the [observability readiness gate](../../architecture/observability-readiness.md).
+5. Check the [release URL ledger](release-url-ledger-2026-05-19.md) before
+   using any announcement links.
+6. Start with one workflow lane: engineering, research, content, or outreach.
+7. Import only sanitized operator patterns into ECC skills.
+8. Treat `ecc2/` as an alpha control plane until release packaging and installer
+   behavior is finalized.
+
+## Publication State
+
+The GitHub prerelease and npm `next` package are live:
+
+- GitHub prerelease:
+  <https://github.com/affaan-m/ECC/releases/tag/v2.0.0-rc.1>
+- npm rc package:
+  <https://www.npmjs.com/package/ecc-universal/v/2.0.0-rc.1>
+
+This is still a release candidate, not a GA claim. Remaining public claims stay
+approval-gated until readback exists for the Claude plugin tag/marketplace path,
+Codex repo-marketplace or official Plugin Directory status, video upload URLs,
+ECC Tools billing/native-payments readiness, and final outbound copy.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/release-url-ledger-2026-05-18.md

@@ -0,0 +1,55 @@
+# ECC v2.0.0-rc.1 Release URL Ledger
+
+This ledger separates links that are already public from links that only become
+valid after the approval-gated release, package, plugin, and announcement
+steps. Regenerate it from the final release commit before posting any public
+announcement.
+
+Captured from source snapshot
+`81fca2cea6f1399c52c8faa70f9a17e42f0bd447` on 2026-05-18. The ledger file
+may be committed in a later docs-only refresh after the evidence snapshot it
+describes.
+
+## Live Now
+
+| Surface | URL | Verification |
+| --- | --- | --- |
+| Repository | <https://github.com/affaan-m/everything-claude-code> | `git remote get-url origin` |
+| Evidence source commit | <https://github.com/affaan-m/everything-claude-code/commit/81fca2cea6f1399c52c8faa70f9a17e42f0bd447> | `git rev-parse HEAD` at evidence capture |
+| Release pack folder | <https://github.com/affaan-m/everything-claude-code/tree/main/docs/releases/2.0.0-rc.1> | Release pack evidence captured from `81fca2ce` |
+| Release notes draft | <https://github.com/affaan-m/everything-claude-code/blob/main/docs/releases/2.0.0-rc.1/release-notes.md> | In-tree release copy |
+| Hermes setup guide | <https://github.com/affaan-m/everything-claude-code/blob/main/docs/HERMES-SETUP.md> | In-tree sanitized Hermes guide |
+| May 18 evidence snapshot | <https://github.com/affaan-m/everything-claude-code/blob/main/docs/releases/2.0.0-rc.1/publication-evidence-2026-05-18.md> | Current strongest readiness evidence |
+| May 18 operator dashboard | <https://github.com/affaan-m/everything-claude-code/blob/main/docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-18.md> | Prompt-to-artifact dashboard |
+| Pushed-head CI | <https://github.com/affaan-m/everything-claude-code/actions/runs/26011460500> | CI passed 37/37 jobs for `81fca2ce`, including the supply-chain IOC scan job |
+| Latest Supply-Chain Watch | <https://github.com/affaan-m/everything-claude-code/actions/runs/26010432490> | Supply-Chain Watch passed for `25ac57ac`; rerun from the final release commit before publication |
+| npm package page | <https://www.npmjs.com/package/ecc-universal> | `npm view ecc-universal name version dist-tags --json` returned `latest: 1.10.0`; rc.1 is not published yet |
+| Codex marketplace CLI docs | <https://developers.openai.com/codex/cli/reference#codex-plugin-marketplace> | Official docs list `codex plugin marketplace add` for GitHub shorthand, Git URLs, SSH URLs, and local marketplace roots |
+| Codex official Plugin Directory status | <https://developers.openai.com/codex/plugins/build#publish-official-public-plugins> | Official docs say public Plugin Directory publishing and self-serve management are coming soon |
+
+## Approval-Gated URLs
+
+| Surface | Intended URL or command | Gate before use |
+| --- | --- | --- |
+| GitHub prerelease | <https://github.com/affaan-m/everything-claude-code/releases/tag/v2.0.0-rc.1> | `gh release view v2.0.0-rc.1 --repo affaan-m/everything-claude-code --json tagName,url,isPrerelease` must return the prerelease |
+| npm rc package | <https://www.npmjs.com/package/ecc-universal/v/2.0.0-rc.1> | `npm publish --tag next` approval and post-publish `npm view ecc-universal dist-tags --json` |
+| Claude plugin tag | `claude plugin tag .claude-plugin --dry-run`, then real tag only after approval | Clean release commit and plugin tag/push approval |
+| Codex repo marketplace install | `codex plugin marketplace add affaan-m/everything-claude-code --ref v2.0.0-rc.1` | GitHub tag must exist; official Plugin Directory submission remains separate |
+| ECC Tools native-payments announcement | ECC Tools Marketplace/App URL plus billing readiness readback | Marketplace-managed test account must return `announcementGate.ready === true` |
+| Public announcements | X, LinkedIn, GitHub release, and longform URLs | GitHub release, npm, plugin, and billing URLs must resolve first |
+
+## Pre-Post Check
+
+Run these immediately before publication:
+
+```bash
+git status --short --branch
+gh release view v2.0.0-rc.1 --repo affaan-m/everything-claude-code --json tagName,url,isPrerelease
+npm view ecc-universal name version dist-tags --json
+codex plugin marketplace add --help
+rg -n "TODO|TBD|PLACEHOLDER" docs/releases/2.0.0-rc.1
+npm run preview-pack:smoke
+```
+
+Do not post the social or notification copy until the approval-gated URLs above
+resolve from a clean release commit.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/release-url-ledger-2026-05-19.md

@@ -0,0 +1,57 @@
+# ECC v2.0.0-rc.1 Release URL Ledger
+
+This ledger separates links that are already public from links that only become
+valid after the remaining approval-gated plugin, video, billing, and
+announcement steps. Regenerate it from the final release commit before posting
+any public announcement.
+
+Refreshed on 2026-05-26 after the GitHub prerelease and npm `next` package
+readbacks succeeded. Remaining plugin, video, billing, and outbound surfaces
+must still be checked from the exact release commit before publication.
+
+## Live Now
+
+| Surface | URL | Verification |
+| --- | --- | --- |
+| Repository | <https://github.com/affaan-m/ECC> | `git remote get-url origin` returns `https://github.com/affaan-m/ECC.git` |
+| GitHub prerelease URL | <https://github.com/affaan-m/ECC/releases/tag/v2.0.0-rc.1> | `gh release view v2.0.0-rc.1 --repo affaan-m/ECC --json tagName,url,isPrerelease,isDraft,publishedAt` returned prerelease `true`, draft `false`, published `2026-05-25T18:29:31Z` |
+| Release pack folder | <https://github.com/affaan-m/ECC/tree/main/docs/releases/2.0.0-rc.1> | In-tree release pack |
+| Release notes draft | <https://github.com/affaan-m/ECC/blob/main/docs/releases/2.0.0-rc.1/release-notes.md> | In-tree release copy |
+| Hermes setup guide | <https://github.com/affaan-m/ECC/blob/main/docs/HERMES-SETUP.md> | In-tree sanitized Hermes guide |
+| May 19 evidence snapshot | <https://github.com/affaan-m/ECC/blob/main/docs/releases/2.0.0-rc.1/publication-evidence-2026-05-19.md> | Current strongest identity, video, growth, and CI readiness evidence |
+| May 18 evidence snapshot | <https://github.com/affaan-m/ECC/blob/main/docs/releases/2.0.0-rc.1/publication-evidence-2026-05-18.md> | Previous supply-chain and publication-path readiness evidence |
+| May 18 operator dashboard | <https://github.com/affaan-m/ECC/blob/main/docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-18.md> | Previous prompt-to-artifact dashboard |
+| May 19 operator dashboard | <https://github.com/affaan-m/ECC/blob/main/docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-19.md> | Previous prompt-to-artifact dashboard with hypergrowth, video, and outbound lanes |
+| May 20 operator dashboard | <https://github.com/affaan-m/ECC/blob/main/docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-20.md> | Current prompt-to-artifact dashboard with Marketplace Pro release-gate sync |
+| npm package page | <https://www.npmjs.com/package/ecc-universal> | `npm view ecc-universal name version dist-tags versions --json` returned `latest: 1.10.0`, `next: 2.0.0-rc.1`, and included `2.0.0-rc.1` in `versions` |
+| npm rc package URL | <https://www.npmjs.com/package/ecc-universal/v/2.0.0-rc.1> | `npm view ecc-universal@2.0.0-rc.1 name version dist.tarball dist.integrity time --json` returned version `2.0.0-rc.1`, tarball `https://registry.npmjs.org/ecc-universal/-/ecc-universal-2.0.0-rc.1.tgz`, and published time `2026-05-26T00:36:22.940Z` |
+| Codex marketplace CLI docs | <https://developers.openai.com/codex/cli/reference#codex-plugin-marketplace> | Official docs list `codex plugin marketplace add` for GitHub shorthand, Git URLs, SSH URLs, and local marketplace roots |
+| Codex official Plugin Directory status | <https://developers.openai.com/codex/plugins/build#publish-official-public-plugins> | Official docs say public Plugin Directory publishing and self-serve management are coming soon |
+
+## Approval-Gated URLs
+
+| Surface | Intended URL or command | Gate before use |
+| --- | --- | --- |
+| Claude plugin tag | `claude plugin tag .claude-plugin --dry-run`, then real tag only after approval | Clean release commit and plugin tag/push approval |
+| Codex repo marketplace install | `codex plugin marketplace add affaan-m/ECC --ref v2.0.0-rc.1` | GitHub tag must exist; official Plugin Directory submission remains separate |
+| ECC Tools native-payments announcement | ECC Tools Marketplace/App URL plus selected-target billing readiness readback through the operator bearer path | Marketplace-managed selected target returned `announcementGate.ready === true` on 2026-05-20; repeat immediately before publication |
+| Public announcements | X, LinkedIn, GitHub release, and longform URLs | Remaining plugin, video, and billing URLs must resolve or be explicitly marked blocked; exact outbound copy still needs owner approval |
+
+## Pre-Post Check
+
+Run these immediately before publication:
+
+```bash
+git status --short --branch
+gh release view v2.0.0-rc.1 --repo affaan-m/ECC --json tagName,url,isPrerelease
+npm view ecc-universal name version dist-tags --json
+npm view ecc-universal@2.0.0-rc.1 name version dist.tarball dist.integrity time --json
+codex plugin marketplace add --help
+rg -n "TODO|TBD|PLACEHOLDER" docs/releases/2.0.0-rc.1
+npm run preview-pack:smoke
+npm run release:approval-gate -- --format json
+```
+
+Do not claim plugin propagation, official Codex Plugin Directory listing, video
+upload, ECC Tools billing/native payments, or final outbound readiness until the
+remaining approval-gated URLs above resolve from a clean release commit.

github_code/affaan-m__ECC/docs/releases/2.0.0-rc.1/telegram-handoff.md

@@ -0,0 +1,30 @@
+# Telegram Handoff For Hermes
+
+Send this to Hermes when you want it to help package the launch workflow.
+
+```text
+Use the public ECC release pack in the repo:
+
+- docs/releases/2.0.0-rc.1/release-notes.md
+- docs/releases/2.0.0-rc.1/x-thread.md
+- docs/releases/2.0.0-rc.1/linkedin-post.md
+- docs/releases/2.0.0-rc.1/article-outline.md
+- docs/releases/2.0.0-rc.1/launch-checklist.md
+- docs/releases/2.0.0-rc.1/preview-pack-manifest.md
+- docs/releases/2.0.0-rc.1/publication-evidence-2026-05-17.md
+- docs/releases/2.0.0-rc.1/operator-readiness-dashboard-2026-05-17.md
+- docs/HERMES-SETUP.md
+- docs/architecture/cross-harness.md
+
+Task:
+
+1. Finalize one strong X thread for ECC v2.0.0-rc.1.
+2. Finalize one strong LinkedIn post for ECC v2.0.0-rc.1.
+3. Give me one 30-60 second Hermes x ECC video script and one 15-30 second variant.
+4. Tell me exactly what to record now with screen capture, face camera, and voice lines.
+5. Tell me what Hermes can generate automatically after I record.
+6. Keep every public claim release-candidate framed until live release/npm/plugin URLs exist.
+7. End with a minimal checklist of the assets or logins still needed.
+
+Be decisive. Return final drafts plus a practical recording checklist.
+```