memory: fold session lessons on codex liveness, untracked flake files, and merge duplicates #58
No reviewers
Labels
No labels
blocked
bug
decision
duplicate
enhancement
help wanted
invalid
landed?
question
ready-to-merge
stale
wontfix
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
allod/memory!58
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/session-memory-lessons"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Five lessons from this week's sessions move from private per-session notes into the public topic files they belong to. Nothing changes for a running machine: this is workflow memory only. What changes for the next session: the list-models skill explains that codex's trusted-directory refusal looks like an unavailable model when the probe runs outside a git repo; the runner notes in dev-plans say a scripted codex call needs stdin closed, how to kill one safely, and what one liveness check looks like per runner; the delegation skill gains a single liveness check about a minute after launching a scripted call, stated without naming any runner, as its limits require; the Nix notes gain that a flake build sees only tracked files; and the git workflow gains a check for the same fact bound twice after merging master into a PR branch, whose ledger sighting is retired because the rule now lives in a topic file. What proves it: the tracked memory-budget hook passes, and the added lines carry no host, user, or absolute path. If any line is wrong, revert the file.
Refs allod/secrets#22
Risk
R0. Docs only.
Validation
.hooks/memory-budget --worktree: exit 0 on both commits.