The daily GPT grind
Go to file
2025-12-28 22:29:02 +00:00
SCRATCH Create quick reference for DNS fix needed in next session 2025-12-20 23:10:20 +00:00
ANTI_DRIFT_GUARDRAIL.md Add Enforcement Note (Dec 28) - portal code must remove CSRF/cookies/Pterodactyl/APIv1 before merge 2025-12-28 22:29:02 +00:00
ANTI_DRIFT.md Add Auth & Portal Drift Guardrails - forbidden APIv1/Pterodactyl/CSRF/cookie patterns, enforce Portal→JWT→APIv2 flow 2025-12-28 22:28:40 +00:00
CONSTRAINTS.md Add Authentication Constraints section - APIv2 stateless JWT, no CSRF, no cookies, forbidden patterns 2025-12-28 22:27:49 +00:00
OPEN_THREADS.md Add Portal Migration to APIv2 Auth thread - legacy assumptions, blocking items, open questions 2025-12-28 22:27:24 +00:00
README.md Add explicit execution continuity statement to README 2025-12-14 00:29:38 +00:00
SESSION_LOG.md Add Dec 28 session - APIv2 Auth + Portal Alignment verification and decisions 2025-12-28 22:26:41 +00:00
SESSION_START.md Update session start - subtraction-first mindset 2025-12-28 00:16:08 +00:00
UPSTREAMS.md Add Authentication Ownership section - Portal/APIv2 responsibilities and explicit non-responsibilities 2025-12-28 22:28:12 +00:00

zlh-grind

GPT Execution Workspace for ZeroLagHub

This repository is dedicated exclusively to GPT-driven implementation work. It exists to capture execution context, day-to-day grind notes, and concrete changes made during development.

This repository exists to preserve execution continuity across long-running development work.

Assistant Prompt

You are údar. In this repo you act as the execution assistant: implement, verify, and log work. Keep continuity by reading SESSION_LOG.md, OPEN_THREADS.md, and UPSTREAMS.md. Do not make architecture decisions here; defer to canonical docs in jester/knowledge-base.

What This Repo Is For

  • Daily GPT work logs
  • Session handovers
  • Implementation notes and scratchpads
  • Tracking what was changed, when, and why

What This Repo Is NOT

  • Architecture decisions
  • Cross-project source of truth
  • Product or strategy documentation

All canonical architecture, decisions, and references live in: jester/knowledge-base

Working Rules

  • This repo may be messy, iterative, and practical
  • Prefer clarity over polish
  • Reference canonical docs instead of duplicating them

If it happened during hands-on GPT execution, it belongs here.