fix(marketplace): the generated README links the ready gate's old anchor after #1650
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- developer-experience
Research direction
Open scripts/prepare-marketplace.ts around line 550 and find the generated README link to run-command.md. Update its anchor to #ready-gate, then check the two grep counts in AC-1: the old anchor should occur 0 times and the new link should occur once.
Written by the indexing model from the issue text.
Description
Epic: graph-2026-11-simplify (follow-up of #1650) Tier: mechanical Execution: runner
Problem
#1650 renames the run-command.md heading ### Ready Gate (post-QA second look) to ### Ready Gate, so its anchor becomes #ready-gate. The marketplace README generator still hardcodes the old anchor at scripts/prepare-marketplace.ts:550, so the next generated marketplace README links a section that no longer exists. #1650's AC-4 forbids code edits, so the fix is here.
Acceptance Criteria
- AC-1: The generator links the new anchor. Evidence:
grep -c 'ready-gate-post-qa-second-look' scripts/prepare-marketplace.ts→0, andgrep -c 'run-command.md#ready-gate)' scripts/prepare-marketplace.ts→1
Non-Goals
- Any other marketplace README text.
Done when
scripts/prepare-marketplace.ts links run-command.md#ready-gate, before the 3.0 release (#1657) generates the marketplace README.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 10h 12m
- Merged PRs (30d)
- 78
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sequant-io/sequant
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sequant-io/sequant#1682 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
sequant-io/sequant#1665 ·
Maintainers usually reply within 1 day
-
fix(assess): minimal-flags rule still assumes a ui label adds the test phase (stale after #1649)Open
Difficulty 1/5 1-3 hours Newbie friendliness 87/100
sequant-io/sequant#1662 ·
Maintainers usually reply within 1 day
-
docs(ready): the ready gate's docs drop the second-look claim — describe the qa → loop → qa mechanism and its policy, cite #1344 for what was measuredPossibly taken @admarble claimed this today. Opengraph-2026-11-simplify planned
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sequant-io/sequant#1650 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sequant-io/sequant#1601 ·
Maintainers usually reply within 1 day
All issues in sequant-io/sequant
Similar issues
-
maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
assistant-ui/assistant-ui#10499 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug server-sequentialthinking v2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelcontextprotocol/servers#5526 · 1 comment ·
Maintainers usually reply within 1 day
-
app-server bug CLI
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
cimd: default originBoundFields rejects a cross-origin client_uri, which the CIMD draft forbidsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
better-auth/better-auth#12458 · 1 reaction ·
Maintainers usually reply within 1 day