Moves statifier_router to 0.10.0

[johnnyt]

What

The reference host moves to statifier_router 0.10.0, the published release after 0.9.2.

• mix.exs: {:statifier_router, "~> 0.10.0"}, with a dated comment in the form the line's earlier moves use.
• mix.lock: mix deps.update statifier_router (only that package) changed exactly one line, the statifier_router entry: version 0.9.2 to 0.10.0, new inner and outer checksums. Its own requirements are unchanged (broadway ~> 1.3, ecto_sql ~> 3.14, predicator ~> 9.4, statifier ~> 2.10, statifier_persistence ~> 0.18, telemetry ~> 1.0, uxid ~> 2.0), and no other lock line moved:

-  "statifier_router": {:hex, :statifier_router, "0.9.2", "d3aaf1e0...", [:mix], [...], "hexpm", "692ab408..."},
+  "statifier_router": {:hex, :statifier_router, "0.10.0", "a584aa95...", [:mix], [...], "hexpm", "22cb23b6..."},

• test/statifier_examples/mix_deps_test.exs: the router pin test asserts ~> 0.10.0 and a 0.10. lock entry.
• docs/guides/basichttp-front.md, docs/guides/first-workflow.md, docs/guides/first-workflow-routed.md: each pins table names 0.10.0, since each says it lists what mix.exs requires and mix.lock resolves. The floor sentence in the BasicHTTP guide now says 0.10.0 is the floor because it is the published release mix.exs requires, and 0.9.2 was the first release that ran on this SQLite database. Each "moving" section gets one paragraph saying the move needed nothing.

What the host meets

Nothing here needs more than 0.9.2. From the router's 0.10.0 changelog:

• :around_delivery is a new opt-in option. No configuration here sets it, so it wraps nothing.
• On Postgres a reap batch is one array statement again. This app runs SQLite, which keeps the IN (...) list, and the routed recipe's reaped step counts the same rows.
• The location token no longer appears in the router's own debug query log on the statements that bind it. The hold desk's moduledoc is not changed here.

No migration version is added.

Provenance

• test/statifier_examples/routed_workflow_test.exs changes one token. The routed recipe's first printed line names the loaded router version, and the test matched the prefix statifier_router 0.9.. With 0.10.0 loaded it went red on that line alone, and every later line matched. It now matches 0.10., as the move to 0.9.2 did with 0.6.. The bump forced this edit; the bead's file list did not name it.

Gate

Full mix quality on this tree (the commit's tree is byte-identical to the tree the run went green on, with the repo's gate lock and one machine slot held continuously from the run through the commit):

✓ Format: No changes needed (416ms)
✓ Compile: dev + test compiled (warnings as errors) (2.1s)
○ Doctor: skipped (:doctor not installed)
○ Docs: skipped (opt-in; set docs: [enabled: :auto] in .quality.exs)
○ Doc links: skipped (opt-in; set doc_links: [enabled: :auto] in .quality.exs)
○ Sobelow: skipped (:sobelow not installed)
○ Gettext: skipped (no .po files outside the source locale)
✓ Dependencies: No unused dependencies (436ms)
✓ Credo: No issues (2.1s)
✓ Dialyzer: No warnings (PLT built this run) (63.8s)
✓ Tests: 661 of 661 passed, 84.7% coverage (65.5s)

✓ All quality checks passed!

Sabotage: I pointed the pin test's lock assertion back at "0.9. and left mix.lock alone. the statifier_router dep is the Hex requirement went red on the =~ assertion against the resolved 0.10.0 entry. I restored the file from a copy (byte-equal).

Refs: se-6ld8