chore(triage): digest — mkit

[christopherwxyz]

Triage digest — mkit — August 1, 2026 23:04 UTC

Needs a milestone call

• deps(mcp): bump body-parser from 2.2.2 to 2.3.0 in /apps/mcp #899 — deps(mcp): bump body-parser from 2.2.2 to 2.3.0 in /apps/mcp — no milestone; 9 sibling Dependabot PRs (ci(actions): bump actions/setup-node from 6.4.0 to 7.0.0 #888, deps(signers): bump the cargo-minor group across 1 directory with 4 updates #889, deps(signers): bump p256 from 0.13.2 to 0.14.0 in /contrib/signers #890, deps(web): bump the npm-minor group in /apps/web with 2 updates #891, deps(mcp): bump the npm-minor group across 1 directory with 4 updates #892, deps(web): bump ox from 0.14.31 to 1.0.3 in /apps/web #893, deps(web): bump waku from 1.0.0-beta.6 to 1.0.0-beta.7 in /apps/web #894, deps(rust): bump p256 from 0.13.2 to 0.14.0 in /rust #896, deps(rust): bump k256 from 0.13.4 to 0.14.0 in /rust #897) already carry "mkit public release (v0.4.0)", but routine dependency bumps aren't an explicit milestone theme, so left unset rather than guessed
• deps(mcp): bump hono from 4.12.25 to 4.12.32 in /apps/mcp #901 — deps(mcp): bump hono from 4.12.25 to 4.12.32 in /apps/mcp — same sibling-precedent ambiguity as deps(mcp): bump body-parser from 2.2.2 to 2.3.0 in /apps/mcp #899
• deps(mcp): bump fast-uri from 3.1.2 to 3.1.4 in /apps/mcp #902 — deps(mcp): bump fast-uri from 3.1.2 to 3.1.4 in /apps/mcp — same sibling-precedent ambiguity as deps(mcp): bump body-parser from 2.2.2 to 2.3.0 in /apps/mcp #899
• ci(actions): bump the actions-minor group across 1 directory with 4 updates #903 — ci(actions): bump the actions-minor group across 1 directory with 4 updates — same sibling-precedent ambiguity as deps(mcp): bump body-parser from 2.2.2 to 2.3.0 in /apps/mcp #899
• deps(rust): bump the cargo-minor group across 1 directory with 11 updates #904 — deps(rust): bump the cargo-minor group across 1 directory with 11 updates — same sibling-precedent ambiguity as deps(mcp): bump body-parser from 2.2.2 to 2.3.0 in /apps/mcp #899

Possible duplicates
None

Stale (30+ days idle)
None (oldest open item is #777, ~20 days since last activity)

Decorated this run
No changes this run. Re-checked the full open backlog (4 issues, 14 PRs) against the prior run (15:05 UTC today, ~8h ago) — no issue or PR was opened, updated, commented on, or relabeled in the interim, so the primary 48h decoration pass again had nothing in scope. Existing decoration remains correct: #204 and #777 both carry the right "post-release improvements" milestone and appropriate labels; #787 (docs-drift report) and this digest are self-maintained and excluded from decoration; the stale label exists (confirmed via direct lookup) and no open item has crossed 30 days idle.

---

Note: GitHub Project #13 ("mkit") placement/status sync was skipped this run, as in the prior run. This session's connected GitHub tooling exposes REST-style issue/PR operations only — no tool for adding items to a Projects v2 board or reading/writing its Status field. This is a tooling limitation, not a judgment call; a session with Projects v2 (GraphQL) access is needed to keep project items in sync.