sync-provider-contract-docs: Clarify sync provider contract docs #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "task/sync-provider-contract-docs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Assigned idea
Benchmark authoring specification.
Summary: Update
sync.mdto remove a stale TODO marker and make the provider module contract explicit for model sync maintainers.Task intent: Perform an upstream-facing documentation cleanup in this repo: clarify what sync provider modules are responsible for versus what the centralized runner owns, using the existing
sync.mdmodel sync documentation as the source of truth.Benchmark plan: Construct the task package so the solver works in the repo checkout at the fixed commit and is asked to edit only
sync.md. The prompt should require removing the literalTODO: deleteline and adding or tightening a provider contract section that states provider modules live inpackages/core/src/sync/providers/, export an object satisfyingSyncProvider<SourceModel>, and only fetch, parse, and translate source models while runner-owned behavior remains inpackages/core/src/sync/index.ts.Environment plan: The environment/repo is the unmodified
anomalyco/models.devcheckout atfe7927f2dd5e0a5c576b490af9a69ffc4a7d070b. The task/environment should add only hidden verification assets such astest_outputs.py; no network access, Bun install, or model sync execution is required because the expected upstream change is documentation-only.Verifier plan: Implement
test_outputs.pyto readsync.mdand fail ifTODO: deleteremains, if any file other thansync.mdis changed according togit diff --name-only, or if the document does not include the required provider contract facts:packages/core/src/sync/providers/,SyncProvider<SourceModel>, fetch/parse/translate language, runner-owned file IO or TOML formatting, and bothbase_modelandbase_model_omit.Oracle plan: Create a reference solution patch that edits
sync.mdonly: delete the stale TODO line near the top and add a concise## Provider Modulesor equivalent subsection explaining the provider contract and the boundary withpackages/core/src/sync/index.ts. The oracle can be stored as a golden patch plus the same semantic assertions used bytest_outputs.py.Difficulty plan: Coding agents may over-edit the sync implementation instead of performing the requested documentation change, may remove or rewrite existing command documentation, or may miss subtle contract details such as local
base_model/base_model_omitmetadata handling and runner-owned deletion/reporting behavior.Repo patch scope: Expected upstream edits are limited to
sync.mdonly.Anti-leakage notes: The solver-facing prompt and files must not mention benchmark, harness, Snorkel, Harbor, std-ts, agent, stage, attempt, retry, generated task, or evaluation context.
Approach: Ask for a focused documentation patch: preserve the existing model sync command and runner responsibility sections, remove the stale TODO, and add concrete provider module guidance grounded in the current sync architecture.
Verification: Run
python test_outputs.py; it should inspectsync.mdand usegit diff --name-onlyto confirm the documentation-only patch and required sync-provider contract wording.Risk: Low technical risk because the change is documentation-only; the main risk is making the verifier too dependent on exact prose rather than checking the concrete required facts.
Path rules: task package is tasks/; mutable upstream checkout is tasks//task/environment/repo; benchmark package files are under tasks//task; verifier/container environment belongs under tasks//task/environment; regular and UI verifier logic belongs in task/tests/test_outputs.py and test.sh only runs that file through pytest.
Agent context
Task slug: sync-provider-contract-docs
Branch: task/sync-provider-contract-docs
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.