pansy

50 Commits 9 Branches 0 Tags

2 Commits

Include renames

Author	SHA1	Message	Date
steveandClaude Opus 4.8	653f381c4b	Document the agent env vars; make keeping docs true a standing rule Build image / build-and-push (push) Successful in 6s Details README's config table gained OLLAMA_CLOUD_API_KEY and PANSY_AGENT_MODEL, marked as read once the assistant lands (#56) so the table describes what the binary does rather than what it will do. Both are already set in Komodo. Also fixed the Compose example, which still said "# PANSY_OIDC_ISSUER: ... once auth (#5) lands" — auth landed a long time ago. That is exactly the kind of rot this commit is trying to prevent, so it seemed worth fixing in the same breath: the snippet now shows the OIDC vars people actually need to set. CLAUDE.md now carries the rule explicitly. README updates go in the SAME commit as the change that needs them — the env var table and the compose snippet are the two things people copy, so they hurt most when stale. DESIGN.md tracks real architecture changes. Examples must run. And when you touch a file, check the comments around your change are still true, because a stale comment is worse than none: the next reader believes it. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_01H3zbym8Doka2d7D48maSgZ	2026-07-21 00:55:06 -04:00
steveandClaude Opus 4.8	1716362981	Add CLAUDE.md and a prominent vibe-coded disclosure in the README Build image / build-and-push (push) Canceled after 11s Details pansy is written by an LLM with a human directing. That belongs near the top of the README, not in a footnote — someone deciding whether to self-host this and point it at their own data should know before they decide, not after. The disclosure says what it actually means in practice (less scrutiny than a hand-written project, read the code, back up the database) rather than a vague "AI-assisted" hedge. CLAUDE.md collects the operational details that otherwise get rediscovered every session: GOWORK=off, the store/service/api seam and why rules go in the middle layer, the two unit scales, version-guarded writes, ErrNotFound-as-existence-mask, the branch/Gadfly/merge/deploy loop, and the env var names that aren't guessable. It also makes the disclosure a standing rule: if the README is ever rewritten, that section survives the rewrite, and the only acceptable edit is a clearer one. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_01H3zbym8Doka2d7D48maSgZ	2026-07-21 00:50:37 -04:00

Author

SHA1

Message

Date

steveandClaude Opus 4.8

653f381c4b

Document the agent env vars; make keeping docs true a standing rule

Build image / build-and-push (push) Successful in 6s

Details

README's config table gained OLLAMA_CLOUD_API_KEY and PANSY_AGENT_MODEL, marked
as read once the assistant lands (#56) so the table describes what the binary
does rather than what it will do. Both are already set in Komodo.

Also fixed the Compose example, which still said "# PANSY_OIDC_ISSUER: ... once
auth (#5) lands" — auth landed a long time ago. That is exactly the kind of rot
this commit is trying to prevent, so it seemed worth fixing in the same breath:
the snippet now shows the OIDC vars people actually need to set.

CLAUDE.md now carries the rule explicitly. README updates go in the SAME commit
as the change that needs them — the env var table and the compose snippet are
the two things people copy, so they hurt most when stale. DESIGN.md tracks real
architecture changes. Examples must run. And when you touch a file, check the
comments around your change are still true, because a stale comment is worse
than none: the next reader believes it.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01H3zbym8Doka2d7D48maSgZ

2026-07-21 00:55:06 -04:00

steveandClaude Opus 4.8

1716362981

Add CLAUDE.md and a prominent vibe-coded disclosure in the README

Build image / build-and-push (push) Canceled after 11s

Details

pansy is written by an LLM with a human directing. That belongs near the top of
the README, not in a footnote — someone deciding whether to self-host this and
point it at their own data should know before they decide, not after. The
disclosure says what it actually means in practice (less scrutiny than a
hand-written project, read the code, back up the database) rather than a vague
"AI-assisted" hedge.

CLAUDE.md collects the operational details that otherwise get rediscovered every
session: GOWORK=off, the store/service/api seam and why rules go in the middle
layer, the two unit scales, version-guarded writes, ErrNotFound-as-existence-mask,
the branch/Gadfly/merge/deploy loop, and the env var names that aren't guessable.
It also makes the disclosure a standing rule: if the README is ever rewritten,
that section survives the rewrite, and the only acceptable edit is a clearer one.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01H3zbym8Doka2d7D48maSgZ

2026-07-21 00:50:37 -04:00