Repository navigation
feat(evolve-kernel): surface per-iteration retrospectives in the detail page - #41
Merged
myrfy001 merged 1 commit intoOct 19, 2026
Conversation
…il page
Every iteration writes a short prose retrospective (what the LLM tried, what
it measured, what to do next), and the server already serves it at
/iterations/{n}/retrospective. But nothing in the WebUI ever fetched it:
ok-runtime-api.js exported getRetrospective() and no component imported it,
so the one human-readable artifact of a run was unreachable from the page.
Wire it up the same way the sibling plugins (calc-value,
gen-infer-framework) do: rows in the Iteration Progress table open a
retrospective modal, and a new "Retro" column marks which iterations
actually wrote one.
The backend reader is reused unchanged, so this is confined to the plugin's
static/ dir plus a contract test pinning the read_retrospective /
read_iterations fields the modal and marker depend on.
Co-Authored-By: deepseek-flash <deepseek-ai@claude-code-best.win>
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
2 participants
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.
Every iteration writes a short prose retrospective (what the LLM tried, what it measured, what to do next), and the server already serves it at /iterations/{n}/retrospective. But nothing in the WebUI ever fetched it: ok-runtime-api.js exported getRetrospective() and no component imported it, so the one human-readable artifact of a run was unreachable from the page.
Wire it up the same way the sibling plugins (calc-value, gen-infer-framework) do: rows in the Iteration Progress table open a retrospective modal, and a new "Retro" column marks which iterations actually wrote one.
The backend reader is reused unchanged, so this is confined to the plugin's static/ dir plus a contract test pinning the read_retrospective / read_iterations fields the modal and marker depend on.