test(docs): align boundary-language gate with existing reusable-workflow paths

Open Beginner friendly
#2,061 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript

Research direction

Start with docs/agent-task-reusable-workflow.md and run npm run test:docs-boundary-language to reproduce the failure. Compare the public path examples with the boundary assertion, then make the docs and assertion agree through one of the two approaches described. Done means the boundary-language test passes on current main.

Written by the indexing model from the issue text.

Description

Problem

npm run test:docs-boundary-language fails on current main because the public docs corpus already contains paths matching /agents\/[a-z0-9._/-]+/i in docs/agent-task-reusable-workflow.md (including agents/example.agent.json and agents/chat).

Expected

The docs and boundary assertion should agree: either replace those public path examples with contract-neutral examples or narrow the assertion to the private path language it intends to reject.

Reproduction

npm run test:docs-boundary-language

This was observed while running the #2060 validation matrix and is unrelated to that provider implementation.

Dominant language
TypeScript
Stars
17
Forks
4
Avg merge
53m
Merged PRs (30d)
114

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Automattic/wp-codebox

All issues in Automattic/wp-codebox

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.