Repository navigation
v3.7.0
v3.7.0
dewey init now keeps its scaffolded commands and agents up to date. Before this release, init only created missing files, so a repo kept whatever slash commands and agent definitions it was first given. Re-running it now refreshes the files Dewey owns and leaves the ones you've customized alone. This release also closes a shell-injection gap in the scaffolded agents' bash permissions.
Upgrading
Run dewey init once in each repo that uses Dewey. Files scaffolded before this release have no version marker:
- A file identical to the current template gets its marker added, and from then on it's updated automatically.
- Any other file is treated as customized and kept as is. That includes a file that is out of date but that you never edited, because without a marker Dewey can't tell it apart from an edited one.
To bring an out-of-date or edited file onto the managed path, delete it and run dewey init again.
Highlights
dewey init refreshes the scaffolds it owns (#214, closes #213)
Dewey now owns 12 scaffolded files: the nine dewey-* slash commands, the curator and distiller agents, and the dewey-distill.yml.example workflow template. Each ends with a dewey:scaffold <version> sha256:<digest> marker. On re-run, dewey init:
- updates a file you haven't touched to the current template
- keeps a file you've edited, byte for byte, and logs
skip (customized). A broken marker, a pre-marker file whose content differs from the current template, and a symlink are treated the same way. - creates any file that's missing
Your own files are still written only once and never overwritten: the .uf/dewey/ config, dcp.jsonc and .gitignore (missing entries are still appended).
Behavior change: if dewey init can't write a scaffold file, it now fails and names the path, instead of warning and carrying on. In a read-only checkout or in CI, an unwritable .github/workflows/ directory now stops init.
Scaffolded agents can't chain shell commands (#217, closes #215)
The curator and distiller agents' permission.bash maps now end with denies for the seven terminal metacharacters (>, <, |, ;, &, $(, and backtick). Because the last matching rule wins, an allowed command prefix can no longer be extended with redirection, pipes, command chaining or command substitution. This matches the convention used by the Unbound Force personas.
Known limitations
These are from the #214 review and are minor:
skip (customized)is logged for every kind of preserved file, so an edited file, a broken marker and a symlink look the same in the output.- Under a restrictive umask, refreshing a file can widen its permissions to
0644. - An interrupted refresh can leave a hidden
.dewey-scaffold-*temp file behind.