docs: the pitch for humans, the when-to-use section, and a fresh screenshot set (issue #175) - #180
Merged
Merged
Conversation
…enshot set (issue #175) The last insights slice: both READMEs now open with what this is, why, and when to use it, for a reader who has never run an agent, and the images catch up with the shipped surface. - Root README: the lead paragraph answers the context-free reader (an agent working while nobody watches, no surprise bills, no keys to the machine); a new 'When to use it' section gives four concrete recurring-loop scenarios and names the one case plain pi already covers; a design/observe/tune paragraph frames triggers+skills, the graph, and insights as one loop-engineering cycle and links the three docs; the insights page gets its screenshot in that section. The panel and graph sections gain the new facts (four cost tables, schedule and spend on trigger rows, /dispatch insights html), and the plain-commands list finally names graph and insights. - admin/README (the npm-facing console page): same lead promise, the costs/graph bullets updated, a new one-page-for-both-questions bullet with the insights screenshot. - Images: costs-view.svg footer says [f] table and the PNG is re-rendered at its exact prior dimensions (1803x1097, scale 2.68303571); graph-view.png regenerated from a demo model so it shows the observed edge recency and the honesty counters (2480x1600, the prior dimensions); NEW insights-view.png from a populated insights.html. Changed images bump to ?v=0.11.0. Both READMEs keep the no-dash-punctuation rule. Specs UNCHANGED, checked: this slice states what earlier slices shipped and changes no behaviour. Suite green in the CI posture: 2224 tests, 0 skipped, live Valkey. Signed-off-by: Rob Boerman <robboerman@live.nl>
This was referenced Aug 12, 2026
edgehero
added a commit
that referenced
this pull request
Aug 12, 2026
Ships the insights consolidation: issues #175 and #181, PRs #176-#180 and #182-#184. - admin 0.8.0: insights is the ONE analytics surface. Bare /dispatch insights (and the panel's i key) writes and opens the self-contained page: budget dials with used-vs-cap facts and the worker's own states, plan verdicts, daily + cumulative + per-flow spend charts, the four breakdowns, and the trigger/flow topology with schedule tips and spend badges. insights whatif is the estimator. The COSTS and GRAPH views and the costs/graph subcommands are REMOVED; the cost-fold correctness fixes (requested-window proration, flowKey, other/other, truncated-ledger counter) and the byTrigger/byRepo/ dailyByFlow folds ride along. dispatch_costs is unchanged. - worker 0.3.0 and receiver 0.2.1 are unchanged since v0.10.0 and their publishes skip. - Image ?v= tags normalized to this release's version. Suite green in the CI posture: 2192 tests, 0 skipped, live Valkey. Signed-off-by: Rob Boerman <robboerman@live.nl>
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
1 participant
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.
The last slice of #175: both READMEs now open with what pi-dispatch is, why, and when to use it, written for a reader who has never run a coding agent, and the screenshot set catches up with the shipped surface.
What
/dispatch insights html), and the plain-commands list finally namesgraphandinsights.costs-view.svgfooter now says[f] tableand its PNG is re-rendered at the exact prior dimensions (1803x1097);graph-view.pngregenerated from a demo model so it shows the observed-edge recency and the honesty counters (2480x1600, the prior dimensions); NEWdocs/images/insights-view.pngfrom a populated insights.html. Changed images bump to?v=0.11.0.Both READMEs keep the no-dash-punctuation rule. Specs UNCHANGED, checked: this slice states what the earlier slices shipped and changes no behaviour. Suite green in the CI posture (2224 tests, 0 skipped, live Valkey).