my-cd-webhook/docs/active-context.md

Active context — knowledge routing index

Index of this project's knowledge-base entries. Read an entry only when your current task matches its trigger — never preemptively. When an instruction has been fully implemented and is no longer needed, delete its line. (An ai-context update may re-add it; if it's still done, just delete it again.)

Entries

• Working style — code/tool checklist, math/arithmetic options → ai-context/style/working-style.md
• Repository operations — Gitea project, tea usage, branch/PR flow, remote dev bind addresses, package-manager notes → docs/project-knowledge-base.md
• Gitea workflow — branch flow (main → test → dev → feature) and posting comments/PRs with tea → ai-context/infrastructure/git-instructions.md
• Gitea CI on a rootless-Docker runner — Playwright/Buildx, socket mount errors → ai-context/infrastructure/rootless-docker-gitea-runner.md
• Publishing public releases to a separate GitHub repo → ai-context/infrastructure/gitea-to-github-release.md
• Uploading build artifacts to Cloudflare R2 from CI → ai-context/services/cloudflare-r2.md
• CI success/failure notifications via ntfy → ai-context/services/ntfy.md

This project

• What this repo is, how it is installed, troubleshooting → docs/OPERATIONS.md
• Non-obvious gotchas in this codebase (health endpoint, eval pitfall, importing cd-target) → docs/hints.md
• Design, targets, networking, deployment status → MCP vault, Home IT/Services/CD webhook (fleet deployment).md
• Why this exists, how to add a project, testing without a host → MCP vault, Development/CD webhook development.md
• What a correct domaindingo deploy is — this repo automates it, that note defines it → MCP vault, Development/DomainDingo Development.md
• Shell style for this repo (constants UPPER_SNAKE, locals PascalCase, braced expansions) → MCP vault, Development/Coding conventions.md

Before adding a deploy script to any application repository: don't. Add a target to targets.json here instead.