2.9 KiB
The Session Meter on the Web Console
Part of the web console contract (console.md). Your workflow notes give the
exact run to post; read this only if one is refused.
Session meter
The page's top bar shows a meter of how much work this console session has done (green, yellow, red), so the person knows when a fresh session would be sharper. It is advice only and never blocks anything. The console counts launches itself: Plan, Revise plan, Document, Review, Quick task, Init, Init update, Finalize, Git and Changelog score when their session opens, and there is nothing to post for them.
It counts answers itself too: every card the person answers in a send adds to
the skill run's tally when wait hands the send to you, and every 2 answers
score a point, so a long back-and-forth weighs more than a short one. Notes,
Quick questions and buttons such as Stop or the dashboard do not count.
Per-unit work is yours to report, with run in any post:
{ "run": { "event": "implement-phase", "id": "phase-2", "tasks": 9 } }
eventis one ofpathfinder-chart,pathfinder-question(scores nothing now: answers count instead),pathfinder-research,plan,revise-plan,document,implement-phase,implement-review-phase,review,quick-task,init,init-update,finalize,handoff,git,changelog,git-commitsandgit-conflict(Git's own, seenotes/git.md). An unknown event is exit3. Post only the events your notes name: a skill that scores when its session opens (the list above this one) already has its points, and arunfor it scores the same work twice.idnames the unit: a question's file slug,phase-N,map. The same id posted again in the same skill run is ignored, so a repeated post never counts twice. It must be non-empty.tasksgoes only withimplement-phaseandimplement-review-phase: the number of tasks the phase completed (marked[x]; blocked[!]tasks do not count), a whole number from 1 to 999. A built phase scores by its size, one point per 3 tasks rounded up, and Implement + Review one more for the review. Always send it: without it a phase scores a flat 2 (or 3), however big it was. On any other event it is exit3. The console already counts a build's tasks fromheadline.clearedas they are ticked off; the phase'sruntakes that count over with the final score, so it never counts twice.commitsgoes only withgit-commits: how many commits Git just made, a whole number from 1 to 999. A Git run scores one point per 2 commits, rounded down; on any other event it is exit3.- One
runper post. Which events a workflow reports is in its own notes (notes/pathfinder.md,notes/git.md;building.mdfor Implement and for the review run on the page after a build).
run never reaches the page state: post (and open --file) lift it into the
session's ledger.