Filed by the domain:cli execution PM seat (#6024) from a measurement handed back on #15638, using Claude Code.
The finding
Grepping staticPath across all .ts outside node_modules and dist returns exactly four lines: the PluginSchema declaration, and the three reads inside the UI auto-discovery block in hono-plugin.ts's start(). slug has the same shape — zero producers.
So that block — both of its disjuncts, the modern ui one and the legacy ui-plugin one — is:
- exercised by no in-repo plugin,
- covered by no test,
- and serves only externally authored plugins.
It mounts real routes (/slug and /slug/*) for a population that exists entirely outside this repository, with nothing inside the repository that would notice if it stopped working.
Why it is worth a card of its own
This is the reason a careful reader scanning this repo concluded the legacy arm was dead — see #15638, where exactly that happened and the premise had to be falsified by a purpose-built probe driving the real kernel. The code is dead from the inside and live from the outside, and there is currently no artifact in the tree that says so.
That is a coverage gap independent of how #15638 is decided:
A fixture plugin that actually declares type: 'ui' and a staticPath, driven through the real ObjectKernel.use() and HonoServerPlugin.start(), would close it. #15638's probe is a working template — it registered a plugin through the real kernel, drove the real init()/start(), and observed the routes handed to rawApp.get, with a non-UI control proving the harness can produce an empty result.
⛔ This seat is not grading priority or routing.
Provenance
⚠️ Not verified by this seat independently — this is the dev agent's measurement on #15638, relayed, taken against unmodified origin/main 2e357650306. The grep counts should be re-derived before anyone acts on them.
Filed by the
domain:cliexecution PM seat (#6024) from a measurement handed back on #15638, using Claude Code.The finding
Grepping
staticPathacross all.tsoutsidenode_modulesanddistreturns exactly four lines: thePluginSchemadeclaration, and the three reads inside the UI auto-discovery block inhono-plugin.ts'sstart().slughas the same shape — zero producers.So that block — both of its disjuncts, the modern
uione and the legacyui-pluginone — is:It mounts real routes (
/slugand/slug/*) for a population that exists entirely outside this repository, with nothing inside the repository that would notice if it stopped working.Why it is worth a card of its own
This is the reason a careful reader scanning this repo concluded the legacy arm was dead — see #15638, where exactly that happened and the premise had to be falsified by a purpose-built probe driving the real kernel. The code is dead from the inside and live from the outside, and there is currently no artifact in the tree that says so.
That is a coverage gap independent of how #15638 is decided:
plugin-hono-serverstill accepts the legacyui-plugintype thatPluginSchemarefuses — an unreachable arm under ADR-0049 #15638 goes the declare route, this block gains a conversion seam and still has no test;dateRangeresolves on the UTC calendar, not the process-local one (#15825) #16047), the block's inputs change and nothing would catch a regression.A fixture plugin that actually declares
type: 'ui'and astaticPath, driven through the realObjectKernel.use()andHonoServerPlugin.start(), would close it. #15638's probe is a working template — it registered a plugin through the real kernel, drove the realinit()/start(), and observed the routes handed torawApp.get, with a non-UI control proving the harness can produce an empty result.⛔ This seat is not grading priority or routing.
Provenance
origin/main2e357650306. The grep counts should be re-derived before anyone acts on them.