[dskvr]

Napplets can now report committed advertised intent locations and read runtime-owned history through navigation.report/get. The reference runtime assigns visits, enforces manifest parameter allowlists and revision ordering, and revisits the exact retained entry through a correlated intent delivery to the same live instance.

• Adds core types, NAP and SDK root/subpath APIs, explicit runtime injection, npm/JSR exports, and Vite requirement inference.
• Implements endpoint isolation, retries, rejected-report high-water ordering, retention, traversal timeout, redirects, supersession, late reports, and termination. Browser/CLI conformance hosts bind eligibility to host-verified manifest metadata.
• Updates package/site docs and authoring skills; adds release changesets.

Targets the published NAP-NAVIGATION draft and companion INTENT delivery draft. The maintainer confirmed the companion remains intended despite its closed/unmerged PR. Breaking pre-1.0 change: IntentDelivery.id is required; sender: null identifies shell-originated delivery. Runtime integrations must implement the same draft contract.

Validation: full build (12 tasks), type-check (19 tasks), recursive unit suites (881 passing; 3 existing ignored), JSR exports, 11 skills contracts, and assembled-site crawl (26 URLs) pass. Includes 224 conformance tests and real Chromium manifest-bound navigation coverage. Independent review findings for reset lifetime and sparse-array allocation were fixed with regressions. Pinned AI-slop scan is 98/100 with no code findings; only the unchanged transitive deepmerge low advisory remains, with no fix available.

No external production shell testing, merge, or publication included.

[dskvr]

Merged main into this branch, so the conflicts are gone. It was a plain merge at f28c2fdd with no force-push. Build, type-check, unit suites, the browser navigation round trip and the skills, JSR and maturity checks all pass locally.

The merge needed a few changes beyond the conflict hunks:

• Catalog and docs: navigation now has its catalog entry and docs group, and the intent guidance moved to main's per-domain page.
• Host ceiling and revocation: navigation now honors both. Without this, a narrow host would still serve history, and a replaced document could inherit the old one's. There are new tests for this.
• Existing tests: the navigation shim tests moved to the MessagePort shell. The llm and maturity fixtures now use their own endpoint ids, because the registry here keeps the first binding for an id. Could someone check that's the behavior we want? A narrower handleFrom on a live id is silently ignored.

Mergeable doesn't mean ready to land, though. Both drafts moved on 2026-10-31, after this was built, and the current text contradicts part of what's here:

Draft	Current text	What this PR has
NAP-INTENT (#128 at 74f9bf85)	"No intent delivery identifier is exposed", and intent.deliver "has no request or delivery id"	Required IntentDelivery.id, plus retryIntent and failNavigationDelivery keyed on it
NAP-INTENT	"The runtime MUST NOT fabricate, reserve, or null a sender for this purpose"	sender: null for shell-originated delivery
NAP-NAVIGATION (#126 at 9a4b179e)	"navigation adds no fields to the intent payload or delivery", and revisits settle by location "instead of delivery ids"	NavigationReport.deliveryId and delivery-id settlement

I left all of that as it was, since this was only meant to resolve conflicts. Mind if we reconcile it with the current drafts before merging? The changeset and docs also say this follows the published drafts, so they'd change too. I also haven't checked the new rule that rejects mode with a null location.

Nit: the description says #128 is closed, and apps/docs/naps/navigation.md repeats that, but it's open now.

Not proven: boot.ts ending the endpoint on revoke has no direct test (the equivalent path in attachReferenceShell does), and pnpm test:conformance uses a fixture that doesn't touch navigation.

🤖 Generated with Claude Code