Complete reviewed Wiki memory workflow - #12
Merged
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
Why
The Wiki stored reviewed documents but did not reliably reuse them during later work. Plain lexical
matching also missed Korean requests for English guidance, while generic terms caused false
positives. Post-task observations had no matched no-memory control, so they could not separate
memory effects from task or model variance.
The host now owns deterministic retrieval, task binding, control generation, and evaluation. Model
execution remains provider-neutral and works with manual or subscription-based runners without an
API dependency.
Validation
pnpm check