Skip to content

[Feature] Publish a portable reviewed source baseline for the existing ProgramBench harness #299

Description

@rajesh-ms

Outcome

Dependent benchmark fixes target a maintainer-reviewable immutable source commit containing the existing R4 harness, remote adapter, unlimited-budget support and sanitized synthetic fixtures, rather than code available only on one machine.

Observed behavior

Original base is b2523964e7576cafc00e84a51e1044f55826dea7. R4 used an uncommitted 618-file local snapshot, archive SHA-256 6ce23a6e8eb433a4965001a566c4198f7b40140d691003d1e44707a833dacb1b. Capability/ProgramBench helpers, Python tests and registrations are absent from that base; tracked core/web files also contain local remote-adapter/unlimited-budget changes. The later completion observer is an output-only helper outside the source archive.

Expected behavior

Curate the required existing changes into an accessible portable baseline. Preserve the measured archive and old receipts unchanged. Local files/archive hashes must not be presented as public Git commits.

Reproduction and evidence

Check out the original base and compare availability against the sanitized source-hook manifest. Full findings: #296 (comment); overview: #296. Historical local test results are context, not validation of the eventual published commit.

Acceptance criteria

  • Inventory and review the exact local change set, source hashes, runtime/licensing prerequisites and portable configuration; provide the reviewed source branch delivered by the source-intake issue and the exact resulting commit SHA recorded in source-intake acceptance evidence accessible to downstream workers.
  • Exclude personal paths, secrets/provider configuration, candidates, held-out bodies and raw traces. Publish sanitized metadata and synthetic fixtures; do not upload the raw archive blindly.
  • Port required helpers/tests and the completion observer to repository-owned paths. The proposed tools/capability_completion_observer.py must not depend on a historical PID/private output file.
  • Preserve Unlimited -1, zero provider-free checkpoint and null/default finite semantics where applicable, plus cost/loop/tenant/Corp/requester authority and cancellation safety.
  • Run exact contributor gates and targeted harness/remote-adapter/unlimited-budget tests on the final commit; distinguish reused historical runtime evidence from new checks.
  • An independent reviewer confirms the available immutable baseline and source mapping; local archive presence alone does not close this issue.

Dependencies

Blocked by #298.

Aligned with #164, #53 and #166. Preserve their distinct scope and existing recovery/authority contracts. Review PR #294 before touching verifier behavior.
This serialization prevents the source intake from overwriting the preceding core handoff/deadline fixes. The source publication remains a prerequisite for benchmark-specific work.

Governed delivery contract

  • Source repository: All-The-Vibes/ecorp.
  • Source base: original commit above plus the preserved local snapshot; curator selects the current main/authorized parent and records the resulting exact commit.
  • Write scope: only the named capability/ProgramBench helpers and corresponding tests; remote adapter crates/crony-runner/src/adapter/codex_remote.rs and required adapter wiring; token-budget domain/protocol/runner/server/store/CLI/web changes; migration 0042_unlimited_token_budgets.sql and manifest; portable synthetic capability fixtures; associated architecture/unlimited/ProgramBench docs. Curator must turn this inventory into an exact allowlist before dispatch. Exclude output/**, private configuration, candidate worktrees and held-out data.
  • Provider/strategy and budgets: curate explicit native harness/model/strategy and unlimited tokens (-1), using the qualified native runtime, 10,000,000 microusd ($10) per implementation mission, subject to existing requester/Corp limits, no inherited 20-minute benchmark cutoff; one initial task attempt, scoped work and native cost/loop/stop controls; report insufficient authority rather than extend it; coding execution requires native Factory eligibility, a durable claim and the reviewed source package.
  • Allowed tools: source intake/portability edits and declared checks in an isolated worktree; no unrelated uncommitted work or R4 modifications.
  • Persisted verifier: final-checkout contributor gates, targeted adapter/budget/observer tests and required owned full-stack evidence; independent source review.
  • Publication: reviewed source PR or explicitly linked coherent intake slices, ending in one immutable downstream baseline; no merge, auto-merge or deployment authority.

Harness-native-first and boundaries

Retain thin adapters around the pinned native Codex and ProgramBench APIs; inspect supported session, permission, artifact and verification capabilities before changing mechanisms. S packages/reconciles the existing baseline; the six functional improvements belong in their own issues. Missing prerequisites or excessive scope remain explicit blockers rather than an excuse to sweep in the whole workspace.

Validation

Run node tools/check_migrations.mjs, cargo fmt --check, cargo clippy --workspace --all-targets -- -D warnings, cargo test --workspace, pnpm build:web, pnpm lint:web, plus targeted capability/packaging/remote-adapter/unlimited-budget checks. Historical 177 capability, 21 packaging and nine journal tests are not final-commit claims. Record exact commands, counts, source/environment hashes, failures and hosted-CI status.

Findings attachment

The full sanitized investigation, controls, quantitative findings, source-provenance hashes and TF-01–16 acceptance matrix are attached inline in #296. This issue includes its relevant observations above. No private local path is required to read the findings.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dark-factoryGoverned issue-to-mission-to-pull-request automationevalsEvaluation and real-world verificationpriority:p1Important after the critical pathstatus:blockedCannot progress without an external dependencytype:featureNew product capability

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions