[codex] Milestone 9 checkpoint - #4
Draft
OneLastStop529 wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This checkpoint closes out Milestone 9 by making the CLI follow a single Redis-backed runtime model and documenting that path clearly.
Changes in this PR:
worker,enqueue,result, anddlqto Redis-backed state for normal CLI usagemake installand repo-local zsh completion support for thetaskforgecommandtaskforge result -idresolve a unique task ID prefixbin/and.direnv/Why
The project previously supported Redis-backed multi-process execution, but the default CLI path still led users into isolated in-memory behavior. That created ambiguity around the intended runtime model and made the out-of-the-box flow harder to use.
This checkpoint makes Redis the default CLI path, keeps explicit in-memory escape hatches for demo and test flows, and tightens the local developer ergonomics around install and completion.
Validation
env GOCACHE=/tmp/taskforge-gocache go test ./...Notes
direnvmutatingFPATH.taskforge result -id <prefix>now requires the prefix to resolve uniquely; ambiguous prefixes return an error.