Skip to content

Unify ci error entry#38

Open
david30907d wants to merge 4 commits into
mainfrom
unify-ci-error-entry
Open

Unify ci error entry#38
david30907d wants to merge 4 commits into
mainfrom
unify-ci-error-entry

Conversation

@david30907d

Copy link
Copy Markdown
Member

Summary

<1-2 sentences: what changed and why>

Changes

Test Plan

  • pnpm verify passes locally
  • <App-specific verification, for example pnpm --filter @zapengine/frontend test:unit>
  • <Manual verification, if any>

Risk

<What could break? Include affected services and blast radius.>

Rollback

Checklist

  • Followed conventions in the relevant CLAUDE.md files
  • Updated .env.example if added env-var references
  • If touching strategy or signal code: ran pnpm --filter @zapengine/analytics-engine test:strategy-snapshot:fast
  • If touching cross-service contracts: confirmed pnpm contracts check covers the change

taiiiiiiiiiiii and others added 4 commits June 17, 2026 10:14
…ants

Make "read .ai-verify/result.json -> logs/<job>.log" the single error entry
for the local opencode /goal fix loop, regardless of which verify variant or
skill is used.

- Add scripts/ci-run-lib.sh; route all six verify-*.sh through it so ci,
  parallel, changed, staged, branch and package all emit the same
  .ai-verify/result.json + per-job logs.
- Fix set -e dead code in verify-changed/staged (FAILED + log pointer now
  print); drop dead RESULT_FILE in verify-branch; add turbo --summarize to
  affected gates.
- Give each .agents/skills sub-skill a "Where the error already is" entry
  block (5 point into .ai-verify; coverage/security flagged as exceptions);
  fix the CLAUDE.md AI-fix-loop step that referenced a nonexistent per-step log.
- lint-staged: run ruff format on .py to match CI's ruff format --check.
- Delete orphan .husky/test-surface-expander.md.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…un_logged helper

Remove the test-hygiene scanner subsystem — never wired into CI, package.json,
turbo, or husky: scripts/test-hygiene.ts, root test-scanner.js, .ai/test-hygiene.md,
and 8 source-manifest.{test,spec}.ts scaffolds (comment-only imports, zero real
coverage). Zero residual references remain.

design-tokens' only test was its manifest; add a minimal vitest.config.ts with
passWithNoTests so test:ci stays green with an empty suite. Reword two comments
that referenced the deleted manifest (landing-page/knip.ts, types/vitest.config.ts).

Extract the duplicated set +e -> turbo -> record block from verify-changed/staged/
branch into cirun_run_logged() in ci-run-lib.sh (the source of the prior dead-code
bug). TURBO_SCM_* passed via env prefix.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This root-level stylesheet was never imported anywhere — not by any
src/ entry, public/ HTML, next.config.ts, or vercel.json, and it is not
copied into the static export (out/). It also carried ~100 hardcoded
swatches built around an off-brand purple gradient (#667eea / #764ba2),
neither of which exists in packages/design-tokens. The live styles are
src/app/{globals,landing}.css + pitch/pitch.css, which consume the
design-tokens CSS variables (brand accent tan #d4c5a3).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Remove verify subcommands with no real consumer, leaving ci/changed/branch/
parallel/deploy. Drop verify-local.sh, verify-staged.sh, verify-package.sh:
- staged is a strict subset of changed, zero machine consumers, not in the docs
- local (bare default) and package are superseded by changed/parallel

Bare `pnpm verify` now defaults to `parallel` (the documented full local gate
before opening a PR) instead of the removed `local`. Scrub the now-stale
references in CLAUDE.md, the monorepo-ci-debugging skill, and ci-run-lib.sh.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 17, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
zap-engine-frontend Ready Ready Preview, Comment Jun 17, 2026 6:03am
zap-engine-landing-page Ready Ready Preview, Comment Jun 17, 2026 6:03am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants