Economics optional-to-core transition

Pin one full immutable target SHA and VERSION; read its manifest/workflows/config and this guide. Economics is now standard for every selected adapter. The manifest expands its exact command set; there are still four formal roles. Standalone analysis defaults to Coordinator scope, while task-bound analysis preserves the active role/authority/return. Daily remains explicitly opt-in.

Before any connected write compare receiver before-images to the verified previous immutable source/receipt and target. The core group is economics workflow, numeric directory/report template, manifest/config registration and selected adapter entries/managed blocks. Classify each absent, package-owned, project-selected compatible, custom or ambiguous. Classify shared Daily dependencies once. Preserve all original task JSONL/revisions, reports, local selected Daily forms and neighbours.

Fresh install uses the clean config template merged with actual project settings and all manifest rows for selected adapters; it never installs Daily discovery or copies upstream live project state. Update/repair includes economics by default, including equal-version transition/re-entry. Merge missing workflow/cache defaults without resetting project/build/scope/owner choices. A compatible chosen dated card is preserved with actual hash/epoch; no quote/schema migration rewrites history.

An old optional install has .tfw/extensions/economics/ or optional discovery entries. Verify each against its actual prior source. The old canonical path may become the thin compatibility bridge; Codex/Antigravity targets become the standard manifest entry. Claude/Cursor use canonical command copies. Retire a redundant .claude/skills/tfw-economics/SKILL.md only after its package ownership, preserved before-image and replacement command are verified under current update authority. Unresolved/custom old canonical or entry refuses the whole dependent core write before mutation; preserve it and route the actual missing choice. Never install a competing algorithm, silently delete a custom alias or claim a preserved custom file equals upstream. Independent unrelated groups may proceed. Use existing content-addressed preservation/update receipts, not a new registry.

The legacy extension installation/entries are compatibility guidance only, excluded from ordinary default payload copying; they never opt into Daily. Custom shared numeric dependencies stop every dependent group. Leave the actual public home cache and task-owned used price copies untouched during framework install/update; agent acquisition uses the common quote contract separately.

Apply only authorized rows from one pinned tree. Verify all selected manifest sources/targets, managed blocks, canonical resolution, preserved before-image hashes, selected config registration, source/copy parity and second-run no diff. Refusal leaves the dependent before-image unchanged. Report exact SHA/VERSION, applied/preserved/retired/refused paths and remaining authority in the existing result/receipt. Filesystem parity is not native behavior; each unavailable host stays unproved. No production update/publication or owner result acceptance follows from this guide.