feat(edge-pricing): evaluate a canonical Deno-compatible pricing source for edge patches

[pitimon]

Problem

Five Deno edge patches embed the same pricing table. The current synchronization test catches drift only after multiple manual edits. The code already records the desired shared-source direction, but deployment/bundling compatibility has not been proven.

Phase 1: feasibility/design spike

• Determine whether the edge deployment supports a shared Deno-compatible module/import or a build-time generated artifact.
• Verify the deployment/versioning contract and inspect deployed or bundled artifacts, not only local compilation.
• Record the smallest compatible approach and rollback path.

Implementation acceptance criteria (only after feasibility passes)

• All five functions consume one canonical Deno-compatible pricing artifact, or a generated artifact with equivalent single-source ownership.
• No Node-only dependency, runtime network fetch, credential, or source-precedence change is introduced.
• Alias handling, zero pricing, and cost calculations remain unchanged.
• Tests prove each endpoint uses the same artifact and retain model-level pricing regressions.
• Deployment/package validation covers every affected edge function.

Out of scope

• Replacing the core src/LiteLLM pricing engine.
• Adding automatic external pricing synchronization.
• Bundling this work with the 2026-08-31 Sonnet 5 cutoff remediation.

[pitimon]

Closing as moot. PR #76 (fdf5b59, decommission the InsForge cloud backend) deleted the entire dashboard/edge-patches/ directory, so the "5 Deno edge patches embed the same pricing table" this issue set out to unify no longer exist in this fork.

Verified on main:

$ ls dashboard/edge-patches
ls: dashboard/edge-patches: No such file or directory

If a canonical Deno pricing source is ever needed again, it would be a fresh design against whatever edge surface exists at that time — not this issue.