Recall
gstack’s Memorable recall now works in read-only repos you opt in
gstack now lets Memorable recall run in a read-only repo, one remote at a time, with a new memorable set command. It stays off by default, and deny always wins.
Veto
A corrupt policy store no longer switches the recall veto off
Before this, a truncated policy file read as no policy at all, so recall ran in every repo, deny included, and the store got reset. Now a damaged store skips recall and stays untouched.
Origins
A rewritten origin URL no longer dodges a deny
The recall hook now checks every origin URL a repo has. A rewrite to another host, or a second origin URL, no longer slips a denied repo past the veto.
Windows
On Windows, the browse terminal agent stops respawning every 60 seconds
On Windows, with Bun installed through npm, the browse terminal agent respawned every 60 seconds and flashed a console. It now runs the real Bun executable, and so does cookie import.
Next
If any repo is set to deny, I would upgrade now
docs/memorable-workflow-memory.mdRecall in a read-only repoCHANGELOG.mdgarrytan/gstack · 1.91.193.0 and 1.91.194.0If you set any repo to deny, I would upgrade now, because a corrupt policy file let recall run there anyway. The opt-in steps are in the Memorable workflow doc.
