JS-019: no CLI/verb dispatch — bind `DOGIsProjector` / `DOGProjectorDog`

Now: OPEN
Sev: LOW

uri.parse (URILexer) is bound, but the verb/projector vocabulary isn't: a JS extension can't tell a projector scheme from a verb, nor which dog serves it. Method: Issues.

Input

Context

js/uri.cpp binds URILexer only; the DOG dispatch table is opaque to JS (verified: grep DOGIsProjector in js/ → none).
dog/DOG.h:302 DOGIsProjector(u8cs), :306 DOGProjectorDog(u8cs), :362 DOGParseURI(urip, u8csc) exist — bindable leaves.
Surfaced by the be status review: status: resolves to sniff via this table; a JS tool wanting the same routing must reach it.

Goals

Expose projector classification and (ideally) scheme-aware parsing.

Constraints

Pure marshalling; schemes/dogs cross as JS strings.
CLIParse (full argv→cli) is heavier — scope this ticket to the URI/projector helpers; defer CLIParse if wanted (JS-015 covers argv).

WIP

Design decisions

(open) dog.isProjector(scheme) -> bool, dog.projectorDog(scheme) -> string|undefined, and uri.parseDog(text) over DOGParseURI (scheme-aware vs the bare URILexer).

TODOs

Repro-first: dog.projectorDog("status") === "sniff"; dog.isProjector("get") === false.
Bind the DOG leaves.

2026-07-10 revision: still OPEN — DOG projector leaves still unbound in the live jab runtime; grep isProjector|projectorDog|DOGIsProjector|DOGParseURI over jab .cpp/.hpp = 0 hits
uri.cpp:153-156 binds only parse/make/esc/unesc (URILexer), NOT DOGParseURI; API.md has no projector mention; dog/ leaves are LIVE so the work persists

Blockers

None.

Outcome

(pending)