other-transaction-workflowlisted

# Other Transaction Workflow Coordinate the bundled skills. Do not replace their OT logic, artifact specifications, approval gates, or validators. Runtime requirements: the bundled OT Project Description and OT Cost Analysis skills, Python 3.10+, `uvx`, and document and spreadsheet artifact support. Pricing requires the bundled BLS OEWS and GSA CALC+ MCP servers; travel also requires GSA Per Diem. ## Required-capability hard stop Apply this before mode selection or any remaining cost analysis when the request states that a required pricing capability is missing, unauthenticated, unavailable, or schema-incompatible. 1. Stop the cost analysis immediately. Do not continue with an available pricing server, a partial comparison, a substituted source, or an improvised public API. 2. Identify the failed server, required operation, failure class, and corrective action. 3. Preserve every approved milestone, authority fact, contribution treatment, cost input, and pending decision already captured. 4. State that work resumes from that preserved state only after the failed capability is restored or the `ot-cost-analysis` skill accepts user-provided authoritative data through its documented path. 5. End without offering to continue a supported portion of the cost analysis. ## Operating rules 1. Preserve user and Agreements Officer authority. Never originate an authority, participant-status, successful-completion, cost-share, price-reasonableness, or follow-on eligibility determinat