Skip to content

Lightflow v0.6.0

Choose a tag to compare

@cedricbellet cedricbellet released this 19 Oct 13:13
· 18 commits to main since this release

Lightflow v0.6.0

Closes #20 and the remaining actionable items of #21 (2, 4, 6). Also two internal refactors with no behaviour change beyond those listed.

Visualizer (#20)

  • A PENDING stamp now reads "Started." on the timeline (only COMPLETED says "Executed successfully."); a stage with no stamp yet keeps a grey PENDING badge, distinct from a started one.
  • Trace cards show only the first line of a stamp message; the inspector shows the full text.
  • Opening the inspector no longer overlaps the Timeline / Payload / Raw views (right padding equal to the drawer width at each breakpoint).
  • Status rendering refactored: the JS sets data-status on three role classes (stage-card, status-badge, status-dot) and one CSS block owns every status colour, the PAUSED pulse, the SKIPPED dashed look and the selected outline. Deliberate differences from 0.5.x: the status border wins over the kind border on finished cards (a failed polling stage shows rose, not sky), the inspector badge is status-coloured, and passport status text is HTML-escaped in attributes.

Manifest: secret_keys (#21 item 6)

  • New optional secret_keys: [..] list on the workflow. Listed payload keys are shown as *** in status --verbose, the dry-run payload echo and the generated visualizer HTML. The passport file keeps the real values so resume works; the state directory is created 0700.

CLI (#21 item 4)

  • --json / --format=json were silently accepted and ignored; they are now rejected like any other unknown flag.

Docs (#21 item 2)

  • skills/create_lightflows/SKILL.md gains "1b. Starting From an Existing SKILL.md": how to classify an existing skill's steps into stages, gates and polls, with a worked YAML example. README points to it under "Authoring Your Own Workflow".

Internal

  • add_stamp() helper replaces 44 copies of the four-line stamp boilerplate in the engine.
  • Gate instructions stay neutral: they say what to do and what payload to resume with, never who must decide.

All 132 standalone tests pass. The Google3 and standalone editions remain in AST lockstep.