docs(openspec): archive merged escrow changes and sync escrow specs

[moises-cisneros]

Summary

Versions OpenSpec artifacts of changes that are already merged, so they stop living as untracked files:

• Archive agent-escrow-payment (feat: Agent Escrow and Payment contract on Soroban #55, merged in feat(contracts): add agent escrow and payment contract on Soroban #78). Task 5.1 (ADR-0003 amendment note) stays unchecked: it is tracked in docs(adr): mark ADR-0002 and ADR-0003 as amended by ADR-0005 #103.
• Archive enforce-max-fee-bps (chore(contracts): enforce a hard MAX_FEE_BPS ceiling in the escrow #79, merged in feat: enforce max fee bps (#79) #94).
• Archive address-testnet-deploy-pr-review (merged in chore(contracts): deploy escrow on testnet and document verifiable on-chain evidence #84).
• Add main specs agent-escrow-lifecycle (from the feat: Agent Escrow and Payment contract on Soroban #55 delta) and agent-escrow-administration (already includes the feat: enforce max fee bps (#79) #94 modifications).

Docs only. No code, no generated files.

Not included

• escrow-claimable-ttl-evaluator-guard (fix(contracts): extend Claimable TTL and reject evaluator == provider in escrow #95 is still open, exploration and proposal only).
• hire-pay-endpoint and openspec/config.yaml: they ship with feat(server): hire and pay endpoint with on-chain payment verification #93.

[cloudflare-workers-and-pages]

Deploying puls3 with    Cloudflare Pages

Latest commit:	a7e2d78
Status:	✅  Deploy successful!
Preview URL:	https://a55d90f8.puls3-4lw.pages.dev
Branch Preview URL:	https://docs-openspec-archive-escrow.puls3-4lw.pages.dev

View logs

[TOMOKI977]

Approved. The agent-escrow-administration main spec correctly merges the #55 delta with the #94 changes (MAX_FEE_BPS = 1,000 matches contracts/contracts/escrow/src/lib.rs), and dropping the resolved fee-cap open item makes sense.

Two small follow-ups, non-blocking:

• A8 gained a new scenario ("successful admin change emits event") that isn't in either delta. Fine if intentional, but specs should only carry what a change actually specified, so either note where it came from or drop it.
• agent-escrow-lifecycle still uses ### R1. create_job style headers, while the administration spec uses ### Requirement: A1.. OpenSpec expects ### Requirement:, so openspec validate will likely complain about the lifecycle spec.