Skip to content

chore: protect api and list it in the org profile - #8

Merged
BackStacked merged 1 commit into
mainfrom
claude/graphql-backend-fa2c1c
Oct 14, 2026
Merged

BackStacked merged 1 commit into
mainfrom
claude/graphql-backend-fa2c1c

Conversation

@BackStacked

Copy link
Copy Markdown
Contributor

What and why

Before: protect-repos.mjs did not know the new api repo, so running it would not require ci there. The org profile still listed api as "coming soon" and said PDFs use REST.

After: CHECKS includes api: ["ci"]. The profile links the api (mgpl-diagnostics/api#1) and says everything goes through the one GraphQL endpoint, PDFs included. llms-full.txt is regenerated.

Running node scripts/protect-repos.mjs api needs an org owner; it is step 1 of the api's docs/LOCAL-AGENT-BRIEF.md.

Type

  • Bug fix
  • Feature
  • Test data (ranges, units, prices)
  • Docs
  • Refactor / tooling

Checklist

  • On a branch (not main)
  • Docs updated (profile, llms-full.txt)
  • No real patient data, contact details or signatures

🤖 Generated with Claude Code

https://claude.ai/code/session_01BA5Vx77ihDsLiZpyg5duJV


Generated by Claude Code

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BA5Vx77ihDsLiZpyg5duJV
@BackStacked
BackStacked merged commit 0e8a3d6 into main Oct 14, 2026
@BackStacked
BackStacked deleted the claude/graphql-backend-fa2c1c branch October 14, 2026 21:01
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