Architectural Invariant Design: Capacitor 7 Background Runner Watchdog Execution Barrier & State Checkpointing
Capacitor 7 Background Runner Watchdog Execution Barrier & State Checkpointing defines an industrial-grade behavioral standard for mobile engineering. Mandates cooperative cancellation barriers, atomic state checkpointing, and deterministic time budgets for Capacitor 7 Background Runner tasks. Prevents fatal OS watchdog termination (iOS 0x8badf00d kills and Android WorkManager eviction) and non-deterministic state corruption across native-to-web isolate boundaries. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.
Hazard Analysis: What Breaks Without This Rule
The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:
| Failure Mode | AI Symptom (The Anti-Pattern) | Severity | Production Impact & Remedy |
|---|---|---|---|
| AI Hallucination & Deprecation Drift | Unbounded Async Worker Loops Causing Native Watchdog Thread Eviction and Corrupted Storage State | Critical | Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository. |
| Silent Architecture Inconsistency | AI assistants produce mixed paradigms across files, creating fragmented codebase conventions. | Medium | Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails. |
Step-by-Step Production Directives
Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:
Engineers MUST ALWAYS enforce a defensive execution budget (maximum 20-25 seconds on iOS BGAppRefreshTask) that preempts the native OS watchdog timer limit.
Engineers MUST ALWAYS enforce a defensive execution budget (maximum 20-25 seconds on iOS BGAppRefreshTask) that preempts the native OS watchdog timer limit.
Engineers MUST ALWAYS thread an AbortSignal through every asynchronous operation (I/O, network requests, CapacitorKV operations) executed inside the background isolate.
Engineers MUST ALWAYS thread an AbortSignal through every asynchronous operation (I/O, network requests, CapacitorKV operations) executed inside the background isolate.
Engineers MUST NOT execute unbounded 'while' loops or un-batched chunked jobs without checking cancellation tokens between iterations.
Engineers MUST NOT execute unbounded 'while' loops or un-batched chunked jobs without checking cancellation tokens between iterations.
Engineers MUST atomically checkpoint transactional worker state (e.g., last processed ID, cursor, sync timestamp) using transactional key-value or SQLite writes after each processed batch.
Engineers MUST atomically checkpoint transactional worker state (e.g., last processed ID, cursor, sync timestamp) using transactional key-value or SQLite writes after each processed batch.
Services MUST catch AbortError exceptions specifically to persist an in-flight resume state and gracefully return an exit status instead of letting promises hang.
Services MUST catch AbortError exceptions specifically to persist an in-flight resume state and gracefully return an exit status instead of letting promises hang.
Workers NEVER assume network availability or complete execution windows
Workers NEVER assume network availability or complete execution windows; tasks must be idempotently resumable upon the next invocation.
Frequently Asked Technical Questions
Common questions developers face when configuring AI coding assistants for this stack:
Q:Why is Capacitor 7 Background Runner Watchdog Execution Barrier & State Checkpointing critical for AI coding assistants?
Mandates cooperative cancellation barriers, atomic state checkpointing, and deterministic time budgets for Capacitor 7 Background Runner tasks. Prevents fatal OS watchdog termination (iOS 0x8badf00d kills and Android WorkManager eviction) and non-deterministic state corruption across native-to-web isolate boundaries. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.
Q:How does adopting this rule prevent AI hallucinations?
This rule explicitly declares what the AI must avoid (Unbounded Async Worker Loops Causing Native Watchdog Thread Eviction and Corrupted Storage State) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.
Q:Which AI coding environments are supported?
This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).
Q:Can I combine this rule with other technology stacks?
Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.