docs: ENGAGE unknown-delete and droppedIds
docs: record ENGAGE sync guards for stray deletes - An Eagle delete for a period DEMI does not hold is ignored. - Comment fallback by eagleId takes only readable ENGAGE rows. - Date formats the ingest accepts. - Superseded last attempts, early failures and repair messages in sync-out retries; move detection before the first send. - The reconcile skipped bucket.
docs: update ENGAGE ingest codes, sync-out retries - 409 is STALE_PUSH only; 422 and 500 codes, zone-less UTC dates, required metURL. - syncVersion replaces engagePushedAt as the sync-out version. - The worker parks the last failure in the poison queue itself. - Project moves, create guards, 180 s claim lease. - Drop SYNC_OUT_MAX_ATTEMPTS, EAGLE_KC_ISSUER and demiMissingInEngage; name the ENGAGE_API_BASE and DEMI_ENGAGE_PRINCIPALS bicep params.
docs: add ADR-014 and ENGAGE sync-out ENGAGE flows to DEMI, then to Eagle through eagle-api's HTTP API. Add ADR-014, the ENGAGE rows reference, the sync-out section, the ingest contract and the demi-sync-out client. Drop the statements that nothing writes to Eagle.