spec: V26, initial Bitcode commercialization w full late-Engi reformation

Promote V26 as the first fully active Bitcode commercial canon.

  V26 is the repository-wide commercialization reform from late-Engi source into Bitcode: Protocol, Exchange, Terminal, admitted interfaces, retained packages, persistence, prompts, inference, proof
  surfaces, and the demonstration-protocol reference now read as one Bitcode system. The active canonical pointer is `BITCODE_SPEC.txt -> V26`, with SPEC, DELTA, NOTES, PARITY, QA, and PROVEN documents
  aligned around the closed V26 state.

  Close the V26 gate sequence end to end:
  - First gate: move the preserved protocol runtime into `protocol-demonstration`, remove the standalone demo-primary posture, and mount the preserved Bitcode shell through app-owned `/application` and
  API routes.
  - Second gate: refit the application into the Bitcode Terminal architecture with activity, transactions, conversations, auxillaries, give/need actions, repository anchoring, selected activity detail,
  shell bridges, and route-owned query state.
  - Third gate: reform the public website, docs entry, shell chrome, nav, footer, and public copy into Bitcode product surfaces instead of Engi/marketing residue.
  - Fourth gate: reopen and close retained-system convergence with explicit proof over conversations, runs/pipelines, persistence/schema, prompts, inference records, retained packages, APIs, and
  compatible execution carriers.
  - Fifth gate: close the minimum-functional Terminal/Exchange baseline, source-to-shares flow, Need review before fit search, AssetPack execution, Finish-delivered PR Shippables, wallet/repository
  readiness, MCP/API/ChatGPT App write-admission, and broad retained-system reform.
  - Sixth gate: elevate the baseline into a minimal viable product across activity, transactions, conversations, auxillaries, Exchange, Terminal, Protocol, Proofs, API, MCP, and admitted app surfaces.
  - Seventh gate: refine the system into a commercially credible testnet launch posture while keeping V27+ tokenomics, V28+ Exchange expansion, and later external-interface depth explicitly scoped
  forward.
  - Eighth gate: close whole-repository provation through prompt-space completeness, retained-package admissibility, system-reform admissibility, whole-repository production satisfaction, and total V26
  closure proof.

  Reform the core product model:
  - Treat Exchange as the durable state, activity, persistence, proof, API, and market-reading layer.
  - Treat Terminal as the primary operator interface over Exchange state.
  - Treat Protocol as the proof contract and rulebook implemented commercially by the retained repository.
  - Treat Auxillaries as readiness/configuration surfaces for identity, repositories, wallets, interfaces, and `$BTD`.
  - Treat MCP, API, ChatGPT App, GitHub, webhooks, storage, and provider integrations as admitted connected interfaces, not parallel Exchange owners.

  Complete the major language and ownership reform:
  - Replace old deliverable-pipeline meaning with Need-satisfying AssetPack execution.
  - Preserve `shippables` only as the V26 Finish-delivered GitHub PR delivery mechanism over stored AssetPack evidence.
  - Separate AssetPack synthesis artifacts, written assets, stored evidence, delivery mechanisms, and Exchange-readable activity.
  - Remove or repurpose deprecated/legacy Engi concepts rather than retaining them as product semantics.
  - Keep compatibility names only where bounded by storage, migration, generated schema, raw PromptPart, or explicit compatibility-carrier rules.

  Close the commercial interface baseline:
  - `/application` is the primary Terminal route.
  - `/exchange` renders the Exchange activity search table, master activity ledger, and selected activity detail instead of redirecting home.
  - Public nav, footer, docs, and shell state point Exchange to `/exchange`.
  - Exchange route preserves route-owned selection/query state, auto-selects the first activity when needed, and renders read-only activity detail without Terminal runtime write controls.
  - Deployment can expose Exchange by setting `NEXT_PUBLIC_DISABLE_EXCHANGE_LINK=false` and, for QA/testnet posture, `NEXT_PUBLIC_BITCODE_ENV=testnet`.

  Record the V26 proof state:
  - Generated proof families accept spec-family inputs, canonical inputs, conversations continuity, runs/pipelines totality, persistence/schema totality, prompt-system totality, inference implementation
  records, fourth-gate reclosure, fifth-gate closure, sixth-gate MVP closure, seventh-gate commercial testnet launch, prompt-space completeness, retained-package admissibility, system-reform
  admissibility, whole-repository production satisfaction, and total V26 closure.
  - `BITCODE_SPEC_V26_PROVEN.md` reports `fullyProven: true`, `v26PromotionReady: true`, and `v26TotalClosurePassed: true`.

  V26 is now closed as active Bitcode canon: the demonstration-protocol remains the reference implementation lineage, and the commercial repository is promoted as the first minimum viable Bitcode product
  implementation.

Author: geraldarthurdavis