cgagentharness-gotchas

Documents session-tested traps and wrong fixes for CG-agent-harness development workflows.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/cgfixit/CG-agent-harness --skill cgagentharness-gotchas-cgfixit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cgagentharness-gotchas
Source: https://github.com/cgfixit/CG-agent-harness/tree/main/.claude/skills/cgagentharness-gotchas
Command: npx skills add https://github.com/cgfixit/CG-agent-harness --skill cgagentharness-gotchas-cgfixit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributors to the CG-agent-harness repository repeatedly hit the same non-obvious traps: tests that look green for the wrong reason, cleanup PRs that break architectural invariants, and CI flakes that get misattributed to unrelated diffs. This Skill captures 19 session-tested failure patterns with their symptoms, wrong fixes, and correct fixes so you avoid repeating them. ## Core Features & Use Cases - Symptom-to-fix mapping: Each gotcha lists the observable symptom, the tempting wrong fix, the correct fix, and evidence pointers to files like INVARIANTS.md, AGENTS.md, and tests/invariant_guard.rs. - Invariant protection: Covers architectural boundaries such as the server/agentic separation (I6), intentional boundary duplication, verbatim CSRF placeholders, and write-gate contracts that must never be loosened. - CI and tooling traps: Documents clippy toolchain skew on Macs, Chrome acceptance flakes (issue #43), ephemeral port races, github.paginate result shape changes, and release dispatch collisions. - Use Case: Before debugging a hanging test or a red CI job on this repo, load this Skill to check whether the failure matches a known trap — for example, serve exiting 0 on port-in-use, or a push not re-triggering the Codex review. ## Quick Start Load the cgagentharness-gotchas skill before running install, verify, packaging, or debugging tasks on the CG-agent-harness repository.

Frequently Asked Questions about cgagentharness-gotchas

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a failing test in CG-agent-harness?▼

Check whether the failure matches a known trap first: scrypt dev-build slowness, clippy toolchain skew on Macs, or tests asserting developer API keys. Each gotcha lists the symptom, the wrong fix to avoid, and the correct fix with evidence files.

Why does the CG-agent-harness CI fail intermittently on Chrome acceptance tests?▼

Chrome chat-browser acceptance flakes are a known class tracked in issue #43 around unreliable Chrome startup. Treat them as flakes with retry and quarantine tracking rather than weakening assertions or deleting the job.

Can I deduplicate constants shared between server and agentic modules?▼

No. Duplicated constants like RUN_ID_PATTERN and timeout values are intentional boundary copies protected by invariant I6. Keep the duplication and the sync tests green instead of sharing modules across the boundary.

Why does setting enabled to "true" in YAML not turn on a write gate?▼

Quoted YAML strings like "true" are treated as OFF for every gate in this repo. Only unquoted YAML booleans arm a gate, and that parser contract is load-bearing and must not be loosened.

Does pushing a fix re-trigger the Codex review on a pull request?▼

No. Codex reviews trigger on open for review, marking a draft ready, or an explicit @codex review comment, not on pushes. After pushing fixes, comment @codex review and verify the reviewed commit SHA matches your head.

What are the limitations of this gotchas skill?▼

It is repository guidance for CG-agent-harness only, not a runtime /api/skills plugin, and canonical contracts still live in AGENTS.md and INVARIANTS.md. It documents known traps but does not replace reading those source files.