portolan@0.1.0

Minor Changes

• 73d5ef5: First release of portolan, a format for describing UI flows so that one context can resolve them and a fresh context can build them without re-deriving intent.

  The YAML flow spec is the source of truth. Diagrams, tables, path enumerations and Gherkin scenarios are rendered from it and never hand-authored. The format says what the user experiences — where they can be, what they can do, what can happen to them, what they are told — and contains nothing about how any of it is implemented.

  Eight verbs ship:

  • portolan lint — validate against the FS-* rules
  • portolan render — regenerate the human-view Markdown (with --check for CI)
  • portolan demo — build a self-contained interactive HTML page
  • portolan handoff — build the bundle a fresh context implements from
  • portolan export — desugar the core to XState JSON or SCXML
  • portolan diff — what changed in the core since a git ref (with FS-035 version-bump gate)
  • portolan paths — every route through the machine, as list, JSON or Gherkin
  • portolan new — write a skeleton that lints clean
  • portolan skills — list or install the two agent skills

  Two example flows ship: delegate-registration (resolved, clean) and connection (resolved, clean, reconciled with a real implementation). Two agent skills ship: portolan-author and portolan-implement.