Skip to content

Harden Mireye campaign resume and failure accounting - #1

Draft
g4nesh wants to merge 1 commit into
mainfrom
agent/fenced-live-campaign-hardening
Draft

g4nesh wants to merge 1 commit into
mainfrom
agent/fenced-live-campaign-hardening

Conversation

@g4nesh

@g4nesh g4nesh commented Aug 7, 2026

Copy link
Copy Markdown
Owner

What changed

  • replace a retired Mireye campaign field with a current stable non-parcel field
  • extend the batch timeout to match observed live response latency
  • add exact prefix-resume planning with recomputed credit ceilings
  • aggregate independent batch, Ask, and geocode failures without automatic retries
  • isolate fingerprints from partially validated batches and add progress/failure summaries
  • raise bounded Ask/geocode concurrency while retaining the 179 requests/minute issue ceiling
  • document the completed field evidence and the explicitly incomplete Ask sweep

Why

Live campaign execution exposed three concrete gaps: response/logistics batches routinely exceeded the former 125-second timeout, an isolated HTTP 500 could discard otherwise valid Ask evidence, and a transient HTTP 502 could terminate the remaining independent field cohorts. The runner now records bounded failures and supports operator-directed continuation without silently replaying billed work.

Impact

The default campaign ceiling remains exactly 47,225 credits. Operators can preview an exact remaining ceiling after skipping a verified prefix of completed batches. Raw field values, answers, addresses, API responses, and credentials remain excluded from reports and source control.

Verification

  • npm run verify
  • 36/36 unit and API tests passed
  • strict TypeScript and ESLint passed
  • production Vite/server build passed
  • high-severity npm audit found zero vulnerabilities
  • git diff --check passed
  • staged JWT/private-key/GitHub-token and internal-artifact scans passed
  • local Docker is unavailable; GitHub Actions remains the authoritative Node 24/container verification

Claim boundary

Across bounded attempts, all 36 core field cohorts validated successfully at least once and the configured nine-point perimeter passed. The latest uninterrupted Ask milestone was 60/175 with 59 valid cited answers and one failure. The sweep did not finish, so this change makes no full-pass Ask reliability claim and commits no incomplete aggregate report.

Replace the retired campaign field, raise the live batch timeout, and add exact prefix-resume credit planning. Aggregate independent batch, Ask, and geocode failures without automatic retries, isolate partial fingerprints, and report bounded progress with controlled concurrency. Document the claim-bounded live observations and cover full and partial resume ceilings in campaign tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant