Skip to content

Claude/wcjbt build continue d46mqk#38

Merged
MartinMontero merged 3 commits into
mainfrom
claude/wcjbt-build-continue-d46mqk
Jun 30, 2026
Merged

Claude/wcjbt build continue d46mqk#38
MartinMontero merged 3 commits into
mainfrom
claude/wcjbt-build-continue-d46mqk

Conversation

@MartinMontero

Copy link
Copy Markdown
Owner

What does this PR do?

Type of change

  • New catalog entry
  • Fix/update to an existing entry
  • New or updated recipe
  • Build flow / docs
  • Enforcement engine / tooling
  • Other

Required checks

The enforcement engine is blocking. CI runs all of this on your PR, but please
confirm you ran it locally too.

  • npm run check passes (schema validation)
  • npm run enforce passes (three-layer exclusion policy + recipe contract)
  • npm test passes (if you touched the enforcement engine)
  • npm run build succeeds

For catalog entries

  • license_spdx is a valid SPDX id read from the primary source, not guessed
  • license_source_url + license_source_commit_sha pin the license to a commit
    (or the entry is under_review with a reason)
  • what_it_does reads in plain language a non-developer could follow
  • The tool is not owned by Meta, OpenAI, or xAI (or it uses a
    provider-agnostic recipe)

For recipes

  • Targets a catalog entry marked provider_agnostic: true
  • Every excluded LLM provider appears in must_not_be_one_of
  • Verification steps block the excluded providers' endpoints

claude added 2 commits June 30, 2026 00:37
The CONTEXT7_API_KEY entry only said "move to environment settings". Expand it
so a future session doesn't re-chase the misleading `fetch failed`:

- Key is injected into the MCP subprocess, not the interactive shell (verified
  2026-06-30: unset in the web shell, absent from ~/.bashrc, server still
  started) — confirm it lives in durable env settings.
- context7.com egress is denied by this web environment's network policy (agent
  proxy returns 403 on CONNECT), surfaced as `TypeError: fetch failed`. Not a
  key/auth problem. Allowlist context7.com to use it in web sessions; it already
  works locally. Don't run `npx ctx7 setup` (would risk inlining the key).

Also bump the Last updated date.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015LBcWvcrpL1GY4qFNGhfq2
This project is wecanjustbuildthings.dev only. Remove the leftover name of a
separate project from the ROADMAP Workers Builds entry and the Cloudflare
account note, keeping just the actionable intent: the Workers Builds API token
must be wecanjustbuildthings-owned and non-expiring, and other projects'
tokens/resources stay out of this one.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015LBcWvcrpL1GY4qFNGhfq2
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 30, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
wecanjustbuildthings e3c1c72 Commit Preview URL

Branch Preview URL
Jun 30 2026, 01:24 AM

Both credentials were verified this session, so move them out of Blocked/watch
into Done:
- CLI/agent token resolves to the correct account; KV/D1/deployment reads succeed.
- Workers Builds build token verified end-to-end — a push to main produced a
  fresh production deployment, proving the deploy credential is correctly scoped.

Only the Context7 key/egress item remains on the watch list.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015LBcWvcrpL1GY4qFNGhfq2
@MartinMontero
MartinMontero merged commit 4f24f33 into main Jun 30, 2026
14 checks passed
@MartinMontero
MartinMontero deleted the claude/wcjbt-build-continue-d46mqk branch June 30, 2026 01:32
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