Implement mandatory fair DAG work queues with Claim-scoped effects - #66024

Motivation

Independent agentic workflows need one durable way to prioritize eligible work, share assignment opportunities fairly, and recover without losing ownership or repeating unsafe writes. This PR implements the mandatory fair DAG queue described by the specification; it is no longer specification-only.

Implementation

• Scheduling, ownership, observations and recovery share the sole causal work-queue.jsonl authority. Native Go and JavaScript engines use one closed version-3 contract and exact integer scheduling; the Go CLI does not depend on Node.
• FIFO-like defaults, weighted/strict priority, accounting-key fairness, fresh CAS retry selection and bounded fair-prefix packing produce immutable compatible assignments. Each assignment is an object containing a claims array. Charges count durable Claims, including failed launches—not CPU time or successful completions.
• Work, Issue and Pull Request DAG vertices support atomic admission, fresh typed observations and verified Result barriers. Completion alone cannot release successors.
• Approved workers bind to the exact repository/workflow/revision/principal and attempt 1. One sender is fenced before launch; uncertainty retains reservations until definitive nonlaunch or exact termination.
• Built-in, custom/deferred, prepared code/tree, GraphQL/REST, native asset, persistent-memory and queue-control paths retain original Claim attribution. Mixed outcomes settle independently, with private native delivery readback. Queue-disabled paths preserve ordinary behavior; an existing private Claim frame cannot escape scope by changing ambient flags.
• Compiler/MCP/operator/explain/trace/reporting surfaces, read-only observers, memory restoration, current-only transition guidance, a major changeset, Temporal/HPC research and diagrams are wired. Earlier file-by-file review and scratch cleanup are retained; resolved main-merge lock backups were removed. /.queue-validation-cache/ is ignored.

flowchart LR
    Ready["Work Results and observed Issue/PR milestones"] --> Fair["Priority and fair-share selection"]
    Fair --> Log[("Durable Claims in work-queue.jsonl")]
    Log --> Assignment["Immutable compatible assignment"]
    Assignment --> Worker["Authenticated attempt-1 worker"]
    Worker --> Scoped["Independent Claim-scoped effects"]
    Scoped --> Results["Verified Results release DAG successors"]

Documentation and formal review

The onboarding Policy previously violated the mandatory empty-key weight and six runtime resource limits. Its template now uses "": 1, default producer entitlement and supported ceilings; a test feeds the actual example to the real policy validator. Documentation distinguishes assignment objects from Claim arrays, hard limits from tunable proposals, historical evidence from current-source captures, and bounded models from runtime refinement. Four missing ESLint rule-table links are restored and automatically checked.

The original 60-configuration review record remains unchanged. The separate refinement and checkpoint-recovery record records the current 61 configurations: 16 exhausted positive searches, 34 exact negative controls, nine exact guarded witnesses and two unfinished searches. FairDAGGitHub now exhausts 1,055,182 distinct states at depth 20 in 8m39s, with zero states remaining and its original bounds, constraints and safety conjuncts retained. TLC fingerprint assumptions are recorded, not presented as mathematical certainty.

Evaluation refinements retain phase guards and exact default-selection algebra. A deterministic projection is uniquely derived from the transaction log on every transition and independently checked by complete replay; it has no separate authority. Five original/revised union-graph comparisons and two exact mutation controls passed. The default batch graph remains 13,662 distinct states at depth 20. Eighteen new seeded simulations emitted 309 sampled states, and nine guarded witness traces matched. Model/configuration/tool identities remain bound to the evidence after the latest main merge; these comparisons are not TLAPS certificates or native runtime refinement proofs.

WorkQueue and QueueOrdering remain unfinished, not passes. Both successfully restored complete pinned local TLC checkpoints and continued for another 1,200 seconds. Their latest progress is respectively 38,640,894 distinct states with 7,079,332 queued, and 51,756,372 with 23,003,758 queued. These are actual continuations, not sums of independent searches; checkpoint restoration can precede the last interrupted progress report. Portable checkpoint archives remain unvalidated. Earlier nominal 1,800-second searches actually ran about 2,226–2,227 seconds; both requested and measured times are retained.

The ESLint factory model and executable comparison exhaust six bounded graphs (31,730 distinct states), checks nine negative controls/seven witnesses, and independently replays/tamper-checks 16 traces. Parent validation confirms all 22 expected model verdicts and six comparison/mutation tests. Actual probes cover 66 registered/configured/documented rules, CJS/non-test coverage, warning-only exit-zero behavior, Claim authority and collector per-Claim bounds. Installed Policy/producers/profiles and complete protected native readback remain assumptions. There is no automatic miner→refiner→monster DAG; quality bars and the monster's three-total-assignment instruction remain prompt obligations rather than global runtime guarantees.

Validation and evidence

• Latest main 303b4028106137af47924a4bc079b8d3fdd8884c is merged in 179a891db0; generated conflicts in daily-choice-test, eslint-refiner and windows-grower were regenerated from merged sources. All 328 workflows compile and isolated drift checking passes. Refinement evidence and synchronized documentation are published in ef75172f34; the remote head matches the clean local tree.
• The merged final test gate ran 2,323 setup-JavaScript tests in 56 files: 2,322 passed and the real multi-repository repo-memory race fixture exceeded its 10-second deadline. The isolated unchanged fixture also reproduced the timeout; it passed in approximately 11 seconds with a diagnostic longer deadline. A fixture-local 30-second budget preserves all assertions and production retry behavior; all 109 repo-memory tests subsequently pass.
• Impacted Go tests, build, TypeScript typecheck, standard Go lint, JavaScript/shell lint and schema freshness passed. Pre-merge custom-lint diagnostics came from nine files byte-identical to main that the old merge-base calculation included. After committing the merge, the normal no-test gate passed change-scoped custom lint and full workflow drift. The initial failed aggregate invocations remain failed records; completed components and corrected/rechecked failures are reported separately without repeating Go unit tests or claiming global custom lint is clean.
• The earlier SDK project-view type error is fixed without casts. Genuine TypeScript 7.0.2 typecheck and 36 project tests cover validated layout literals and endpoint-derived request typing. The earlier merge's component capture passed 2,122 setup-JavaScript tests in 52 files.
• Earlier comprehensive safe-output review passed 3,206 tests/86 files with eight skips, and its disabled collector differential matched 24/24 baseline cases. Those captures predate the latest main merge; they are not a fresh full-suite run.
• Earlier native capture passed 286 conformance cases/50 operating checks with 136 hashes stable during that capture. Safe-output changes invalidate current-source identity; these are historical evidence, not current release qualification. Mocked contention and local measurements are not hosted SLOs.
• Generated contract drift passes. Earlier pinned TypeSpec 1.16.0 supported-subset comparison covers all 41 schemas, not arbitrary schema/runtime equivalence. Existing @types/node 26.6.3 remains because the approved feed lacks pinned 26.6.4; pins/TLS settings were not weakened.

Static compilation review from the earlier main merge

The following records the earlier generated-manifest review, not a new audit of every latest-main change. It is not comprehensive security sign-off or live credential-isolation verification. No secret values or repository secret resources were created/changed.

New per-workflow references were ANTHROPIC_API_KEY, CODEX_API_KEY, GEMINI_API_KEY, OPENAI_API_KEY, GH_AW_DEFAULT_OTLP_ENDPOINT, GH_AW_DEFAULT_OTLP_HEADERS, GH_AW_GITHUB_MCP_SERVER_TOKEN, GH_AW_GITHUB_TOKEN and GITHUB_TOKEN. Provider references support upstream model routing; flagged smoke launch commands explicitly exclude provider keys from the agent environment. OTLP references support configured telemetry; GitHub references support trusted automation/MCP. The reusable caller explicitly forwards declared secrets, including Anthropic for its Claude target, rather than secrets: inherit; caller permissions reflect the called jobs. These uses were consistent with that merge's sources, but deployment token scopes, telemetry destinations, live host boundaries and secret handling still require human verification.

Removed per-workflow references comprised ANTHROPIC_API_KEY, CODEX_API_KEY, OPENAI_API_KEY, COPILOT_GITHUB_TOKEN, GH_AW_CI_TRIGGER_TOKEN, GH_AW_DEFAULT_OTLP_ENDPOINT, GH_AW_DEFAULT_OTLP_HEADERS, GH_AW_GITHUB_MCP_SERVER_TOKEN, GH_AW_GITHUB_TOKEN, GITHUB_TOKEN, and the Grafana/Sentry endpoint/authorization pairs. These removals arose from upstream dev configuration changes and the obsolete ruflo-backed-task deletion; they do not delete secrets from GitHub.

New action references used existing standard pinned implementations: actions/cache/{restore,save}@55cc8345863c7cc4c66a329aec7e433d2d1c52a9, actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1, actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c, actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3, actions/setup-node@820762786026740c76f36085b0efc47a31fe5020, and actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a. Five standard-action references disappeared with the obsolete workflow; no new third-party action repository was introduced in that review. Their placement matched setup/cache/artifact/trusted-script purposes; remote implementation/signature audits are not asserted.

That merge moved AWF agent/API-proxy/CLI-proxy/squid images from 0.28.37 to digest-pinned 0.28.44. Existing MCP-gateway/node images were reused; some previous GitHub-MCP and Alpine-node references disappeared. Xberg moved from digest-pinned latest to digest-pinned 1.3.6. Pins prevent mutable tag resolution, but remote image contents/signatures and runtime behavior were not audited and remain flagged for human review. The ai-moderator redirect to githubnext/agentics/workflows/ai-moderator.md@main was pre-existing and unchanged, not a newly approved redirect.

Remaining release obligations

The complete formal/refinement suite is not passed. Partial/daily searches do not accumulate proof. Local results do not establish host/runtime refinement, CPU-time fairness, deployment SLOs or atomic/exactly-once effects.

Automated queue-branch writer-restriction verification/provisioning remains user-deferred and unimplemented. Workflow administrator bootstrap is unsupported; explicit authenticated operator/trusted-host initialization is required. Live immutable-SHA dispatch and the pinned run-details response remain unverified. Earlier fleet security sign-off remains incomplete; no approval is inferred from its interrupted review. No remote workflow was manually triggered.

See the implementation coverage and release checklist.

✨ PR Review Safe Output Test - Run 37789661275

network:
  allowed:
    - defaults
    - "clients2.google.com"

💥 [THE END] — Illustrated by Smoke Claude · claude · sonnet46 · 63 AIC · ⌖ 7.4 AIC · ⊞ 853 · ◷
_{Comment /smoke-claude to run again}