pm groom prompt points at a flat allod-memory path that no longer exists #120

New issue

Closed

opened 2026-07-27 15:52:58 +01:00 by vnprc-agent · 0 comments

vnprc-agent commented

2026-07-27 15:52:58 +01:00

Contributor

Current state

pm/pm:137 rewrites the reference like this:

-e "s|allod/memory issue-writing.md|${WORK_DIR:-$HOME/work}/allod-memory/issue-writing.md|g"

That substitution produces ~/work/allod-memory/issue-writing.md. Public allod/* repos are checked out nested, so the file is at ~/work/allod/memory/issue-writing.md, and ~/work/allod-memory does not exist on a current dev VM. The flat allod-<repo> alias predates the nested checkout layout and was not updated with it.

Scope

In: the substitution at pm/pm:137, plus a check for any other flat allod-<repo> path assumptions in the PM tool. Out: the wider PM port tracked in allod/tools#103.

The PM groom prompt rewrites a reference to the public issue-writing memory into a path that no longer exists, so the groom step points agents at a missing file. Update it to the nested checkout path the registry actually produces. ### Current state `pm/pm:137` rewrites the reference like this: -e "s|allod/memory issue-writing.md|${WORK_DIR:-$HOME/work}/allod-memory/issue-writing.md|g" That substitution produces `~/work/allod-memory/issue-writing.md`. Public `allod/*` repos are checked out nested, so the file is at `~/work/allod/memory/issue-writing.md`, and `~/work/allod-memory` does not exist on a current dev VM. The flat `allod-<repo>` alias predates the nested checkout layout and was not updated with it. ### Scope In: the substitution at `pm/pm:137`, plus a check for any other flat `allod-<repo>` path assumptions in the PM tool. Out: the wider PM port tracked in allod/tools#103.