[dependabot]

Bumps github.com/grokify/pidl from 0.6.0 to 0.8.0.

Release notes

Sourced from github.com/grokify/pidl's releases.

v0.8.0

Release Notes: v0.8.0

Full Changelog: grokify/pidl@v0.7.0...v0.8.0

v0.7.0

Release Notes: v0.7.0

Full Changelog: grokify/pidl@v0.6.0...v0.7.0

Changelog

Sourced from github.com/grokify/pidl's changelog.

[v0.8.0] - 2026-10-19

Highlights

• Walkthrough viewer: pidl generate -f viewer writes one self-contained HTML page that steps through each scenario, highlighting the active roles and message, with the scenario's introduction, each step's narrative, and presentation controls
• Flow examples: a step can carry an illustrative HTTP request, response and decoded tokens with a cited source, shown in the viewer with signed headers marked and checked claims highlighted
• The AAuth draft-11 example is fully worked: every step of the five access modes and their shared steps has a narrative and an example, with one consistent set of keys, tokens and timestamps

Added

• Flow example field with source, draft or derived kind, request, response, decoded tokens and note, plus validation and JSON Schema (063bba5)
• JSON Schema definitions for flow examples (482e9e2)
• Protocol.Walkthrough: scenarios with fragments expanded, each step's example, security references and written location, and findings attached by location (9df7563)
• walkthrough-json output format with analyzer findings attached (SEC016 left out by default) (da956e3)
• viewer output format: a self-contained HTML walkthrough viewer embedded in the binary, with a CI check that the embedded build is current (d9399f3)
• Walkthrough viewer app in viewer/ (Vite, React, TypeScript): sequence diagram with fragment bands, stepping by keys, buttons and URL hash, request, response and token panels, 16:9 presentation stage, and light and dark themes (40e631e)
• AAuth examples for every step of the five access modes and the agent token, person token and consent fragments, including the web app agent bootstrap (3b294fa)
• Scenario introductions and step narratives for the AAuth example (6380348)

Fixed

• For documents with scenarios, analyzer flow rules reported locations as indexes into the flattened protocol; they now report the written scenario flow (9df7563)

Documentation

• Walkthrough Viewer guide, Flow Examples section in the specification, and the walkthrough-json and viewer formats in the CLI reference and README (684540b)

[v0.7.0] - 2026-10-19

Highlights

• Scenarios: one PIDL file holds a protocol's roles and an ordered list of journeys, with shared fragments drawn as labeled boxes in every sequence format
• Consistent ordering: roles, scenarios and steps follow the file's order in every diagram, table and outline, so decks and guides built from one file agree
• Overview outputs: roles-by-scenario matrix, token table, and an ordered outline (Markdown and JSON) for guides and slide decks
• Token verification fields and analyzer rules that follow each token through a scenario, demonstrated on a new AAuth draft-11 example
• D2 sequence diagrams now render as sequence diagrams: messages are edges, responses are dashed in the flow direction, and labels are quoted so punctuation cannot break compilation
• Unit test coverage raised from 73.5% to 89.5%: the CLI is now driven through a testable run() function, every SVG format has golden-file tests, and most library packages sit between 89% and 96%

Added

• Scenario type, include steps and fragments, with ordering helpers (HasScenarios, ScenarioByID, ScenarioIDs, EntityIndex, OrderEntities) (0eed0b9)
• Scenario validation: unique IDs, participants in entity order and covering used entities, include targets that are fragments, no include cycles, and scenario paths in error messages (88cef72)
• Protocol.Scenario(id, ProjectOptions) projects one scenario into a single-flow protocol, with fragments collapsed or expanded (b7c9902)
• JSON Schema support for scenarios and include steps (8e6e63d)
• --scenario on generate, simulate, debug and analyze, and Protocol.Flatten (46ca05e)
• PlantUML, Mermaid, D2 and SVG draw include steps as labeled boxes across the fragment's participants; --expand inlines them (851dbb7)
• generate --all-scenarios -o <dir> writes NN-<id><ext> per scenario in file order; --include-fragments adds fragments (3ba2c56)
• pidl scenarios lists scenarios in output order as a table or JSON (fae3af7)
• scenario-matrix format: roles by scenario, marking direct and fragment-only participation (7e39963)
• Token verified_by and claims, and flow security signed_by, issues and verifies (c9fedb5)

... (truncated)

Commits

• 7d6d851 Merge pull request #9 from grokify/release/v0.8.0
• 148e80f docs(release): date v0.8.0 and add it to the releases index
• f362b86 chore: bump CLI version to 0.8.0
• 291228c Merge pull request #8 from grokify/feat/viewer
• f88d2ed docs(specs): mark walkthrough phase 4 items complete
• 25516f9 docs(release): add v0.8.0 changelog entries and release notes
• 440e3e2 fix(viewer): remove protocol-specific wording
• 5ab40f2 fix(viewer): keep fragment titles clear of step labels
• 6440279 fix(viewer): show the whole scenario introduction
• 17c991f fix(viewer): always load fresh walkthrough data in development
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #33.