Week of Mon 25 – Sun 31 May 2026
Summary
A three-day active week (Tue 26 – Thu 28 May). The main themes were automation, architecture clarity, and Hermes infrastructure. The GitHub issue-to-PR autocode pipeline was wired up end-to-end using Claude Code Action and Z.ai. Two long-running ambiguities were resolved: why Remote Control doesn’t work with local proxies, and whether all-backend-first is the right build order for the Django/Next.js SaaS (it isn’t). On Wednesday, GitHub Actions mechanics were deepened (GITHUB_OUTPUT, Python webhooks, Projects V2). On Thursday, focus shifted to Hermes Docker profile migration — a new reference note was created documenting the full copy workflow.
Topics Covered
| Topic | Days Active | Note |
|---|---|---|
| GitHub Actions autocode (issue → PR via Claude Code Action + Z.ai) | Tue 26, Wed 27, Thu 28 | github-actions-guide |
| Claude Code Remote Control — API keys vs OAuth identity layer | Tue 26 | claude-code-remote-control |
| Vertical slice development — solo dev build order | Tue 26 | vertical-slice-solo-dev |
| Vuexy Next.js / Django SaaS project — build order confirmed | Tue 26 | vuexy-nextjs-frontend |
| Hermes Docker profile management | Thu 28 | hermes-docker-profile-management |
Key Decisions This Week
- Autocode workflow: Use
anthropics/claude-code-action@v1with Z.ai proxy (glm-4.5-airfor haiku,glm-5.1for sonnet/opus). Label flow:autocode→in-progress→in-review. Secret needed:ANTHROPIC_AUTH_TOKEN. - Remote Control with proxy: Not possible to use Remote Control when inference is routed through a local proxy. Session registration requires
claude.aiOAuth — inference-only API keys are architecturally insufficient. - Build order for Django/Next.js SaaS: Vertical slices confirmed as correct. All-backend-first fails for solo devs because it removes the parallelism that makes it rational for teams. Existing Jira plan already uses vertical slices — no changes needed.
- Hermes profile migration: Copy the entire profile folder (not individual files) from the Docker volume mount — simpler and safer. Full folder captures memories, conversations, and settings together.
- GitHub Actions data flow: Use
$GITHUB_OUTPUT+ stepid:for passing values between steps; replacecurlwebhooks with Python scripts for any conditional logic before firing.
Open Tasks Carried Into Next Week
- Create GitHub labels:
autocode,in-progress,in-review— from github-actions-guide - Add
ANTHROPIC_AUTH_TOKENsecret to GitHub repo — from github-actions-guide - Run Phase 1 Vuexy audit in Claude Code (the 12
claude-docs/prompt) — from vuexy-nextjs-frontend - Paste Lead agent prompt to kick off User Management Phase 4 (T068–T088) — from vuexy-nextjs-frontend
- Download Vuexy Next.js into
frontend/— from vuexy-nextjs-frontend - Create
CLAUDE.mdat repo root — from vuexy-nextjs-frontend - Run the Hermes profile copy on target Docker host and verify — from hermes-agent-orchestration
- Decide on first GitHub Action type for Hermes and continue conversation — from hermes-agent-orchestration
- Verify splator@gmail.com sign-in alert (May 25 Google notification)
- Send W22 weekly Gmail draft (ID: r-3780450707307232022)
Insights Promoted to Evergreen
- api-keys-vs-oauth-identity-layer — API keys are inference-only; OAuth establishes the identity+session layer that Remote Control and Channels require