docs(agents): reference skip-marker policy from workflow.md

Cross-link the new Skip-Marker Policy section in
conductor/workflow.md into AGENTS.md's "Critical Anti-Patterns"
list. The pattern is: agent hits a pre-existing failure, marks
it skip, moves on; suite rots; user has to track down each one
later. The full policy lives in workflow.md (with the 4-question
review checklist). AGENTS.md gets a one-line pointer so the
rule is at the top of every agent's context.

Rule applies in-session: when the fix is reachable within
~30 min of investigation, FIX IT INSTEAD of skipping.

AGENTS.md

@@ -32,6 +32,7 @@ For understanding, using, and maintaining the tool, see `docs/Readme.md` and the
 - Do not read full files >50 lines without first using `py_get_skeleton` or `get_file_summary`
 - Do not modify the tech stack without updating `conductor/tech-stack.md` first
 - Do not skip TDD - write failing tests before implementation
+- Do not use `@pytest.mark.skip` as an excuse to AVOID fixing the underlying bug. Skip markers are documentation of known failures; the failure must be addressed with priority in-session when feasible. See `conductor/workflow.md` "Skip-Marker Policy" for the full policy and review checklist.
 - Do not batch commits - commit per-task for atomic rollback
 - Do not add comments to source code; documentation lives in `/docs`
 - Do not use `set_file_slice` for multi-line content; it's literal line replacement by design (see `conductor/edit_workflow.md`)