Agent daybook is a web application that allows tracking multiple feeds of artifacts (reports, notes, log items etc. etc.) - all the things that AI agents would be producing all day long.
Real bug: the container healthcheck (and the docs' verify step) hit /api/capabilities, which returns 403 unauthenticated; curl --fail treats 403 as an error, so a healthy container would report "unhealthy" and the verify step would look like a failure. Healthcheck now hits /accounts/login/ (200, no auth). Verify commands now print the status code and note not to use curl -f on the 403. Also reframed cloud_agent_deploy.md's intro for an Opus-class deploy agent: it's a guide + Daybook-specific gotchas, not a rigid script — points at the authoritative sources (repo incl. the git-SSH :2222 note, deploy/ files, requirements.txt deps auto-installed, entrypoint runs migrate+collectstatic, docs/deployment.md) and trusts the agent's judgment. Dropped the now- redundant Source Of Truth section. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .claude/commands | ||
| artifacts | ||
| daybook_project | ||
| deploy | ||
| docs | ||
| issues | ||
| scripts | ||
| skills/daybook-posting | ||
| static | ||
| templates/artifacts | ||
| tests | ||
| .dockerignore | ||
| .gitignore | ||
| CLAUDE.md | ||
| manage.py | ||
| requirements.txt | ||