feat(20c): journal writing — per-issue log files in .profile #86

New issue

Closed

opened 2026-04-01 06:32:42 +00:00 by dev-bot · 1 comment

dev-bot commented

2026-04-01 06:32:42 +00:00

Collaborator

Parent

Part of #20 — agent .profile repo.

What to do

After each dev-agent session, write a journal entry to the agent .profile repo:

File path: .profile/journal/issue-<number>.md
Append to existing file if the agent has worked on this issue before
Each entry should include:
- Timestamp (UTC)
- Issue title
- Outcome: PR created / PR updated / blocked / no_push / error
- Branch name and PR number (if applicable)
- Brief summary of what was done (1-3 lines)
Commit and push to .profile repo after writing

Example entry

## 2026-04-01 14:32 UTC

**Issue:** #59 SECURITY: Replace eval usage with safer alternatives
**Outcome:** PR created (#63)
**Branch:** fix/issue-59
**Summary:** Replaced eval with source-after-validate pattern in lib/env.sh.
Used associative arrays in issue-lifecycle.sh instead of dynamic variable names.

Where to hook

The journal write should happen at the end of dev/dev-agent.sh (or lib/formula-session.sh), after the session completes — regardless of outcome. Failed sessions are valuable journal entries too.

Verification

After dev-qwen works on an issue, dev-qwen/.profile/journal/issue-<N>.md exists
Multiple sessions on same issue append to same file
Journal is pushed to Forgejo (visible in web UI)

Dependencies

Depends on #85 (formula loading from .profile — ensures .profile clone/cache is available).

## Parent Part of #20 — agent .profile repo. ## What to do After each dev-agent session, write a journal entry to the agent `.profile` repo: 1. File path: `.profile/journal/issue-<number>.md` 2. Append to existing file if the agent has worked on this issue before 3. Each entry should include: - Timestamp (UTC) - Issue title - Outcome: PR created / PR updated / blocked / no_push / error - Branch name and PR number (if applicable) - Brief summary of what was done (1-3 lines) 4. Commit and push to `.profile` repo after writing ### Example entry ```markdown ## 2026-04-01 14:32 UTC **Issue:** #59 SECURITY: Replace eval usage with safer alternatives **Outcome:** PR created (#63) **Branch:** fix/issue-59 **Summary:** Replaced eval with source-after-validate pattern in lib/env.sh. Used associative arrays in issue-lifecycle.sh instead of dynamic variable names. ``` ## Where to hook The journal write should happen at the end of `dev/dev-agent.sh` (or `lib/formula-session.sh`), after the session completes — regardless of outcome. Failed sessions are valuable journal entries too. ## Verification - After dev-qwen works on an issue, `dev-qwen/.profile/journal/issue-<N>.md` exists - Multiple sessions on same issue append to same file - Journal is pushed to Forgejo (visible in web UI) ## Dependencies Depends on #85 (formula loading from .profile — ensures .profile clone/cache is available).

dev-bot added the

backlog

label 2026-04-01 06:32:42 +00:00

~~dev-bot referenced this issue 2026-04-01 06:33:04 +00:00~~

feat(20f): journal digestion formula — condense old journals into lessons learned #89

dev-bot referenced this issue

2026-04-01 06:33:04 +00:00

feat(20g): migrate all remaining agents to .profile + remove ops repo journal dirs #90

dev-bot referenced this issue

2026-04-01 06:33:04 +00:00

feat: agent .profile repo — formula snapshot + journal per agent instance #20

dev-bot referenced this issue

2026-04-01 08:15:53 +00:00

feat: generic journal aspect — post-session reflection + lessons-learned context injection #97

dev-bot commented

2026-04-01 08:18:33 +00:00

Author

Collaborator

Superseded by #97 (generic journal aspect in lib/formula-session.sh). Journal writing is now a cross-cutting concern in the shared library, not dev-agent-specific.

dev-bot closed this issue

2026-04-01 08:18:33 +00:00