remove-stale-history-export: Remove stale history-file export #2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "task/remove-stale-history-export"
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: Create a deterministic package-metadata cleanup task based on the changelog note that the
agent-sh/agent/history-filesubpath export is stale because its source was deleted.Task intent: Ask the solver to make the package public export map stop advertising the deleted history-file subpath while preserving all other valid exports.
Benchmark plan: Construct the task from the fixed repository commit, then seed a minimal regression by adding back only the stale history-file subpath export in
package.json. The solver-facing prompt should cite the changelog behavior and ask for the package metadata to match it. The expected fix is to remove the stale export entry, not to recreate the deleted source file or change documentation.Environment plan: environment/repo: checkout
guanyilun/agent-shat9b15bc6a8506601b9904148f043dd7436924a0a5with Node.js/npm available for package metadata inspection. environment/task: addtest_outputs.pyoutside the upstream source patch area and seed the regression inpackage.json; do not require network access during verification.Verifier plan:
test_outputs.pyshould parsepackage.jsonand assert thatexportshas no key equal to./agent/history-file, no export target string containingagent/history-fileorhistory-file, and that unrelated export keys remain present compared with the seeded fixture. It should fail if the solver adds a replacement source file for the deleted subpath instead of removing the export.Oracle plan: The oracle solution is a one-file metadata edit: remove the stale
./agent/history-fileexport entry frompackage.jsonand leave the rest of the export map unchanged. The current upstream commit can serve as the reference for the absence of that subpath.Difficulty plan: Coding systems may overfit to the import path and recreate a deleted module, edit only
CHANGELOG.md, or miss nested export target strings in a package export object. The task is small but requires understanding package subpath exports and preserving surrounding manifest structure exactly.Repo patch scope: Expected upstream edit scope is
package.jsononly, specifically the packageexportsmap entry for the deleted history-file subpath. Do not broaden the fix into source directories or documentation.Anti-leakage notes: Do not expose solver-facing benchmark, harness, Snorkel, Harbor, std-ts, stage, attempt, retry, generated task, or evaluation context. Avoid the word agent except when the literal upstream package or import path requires it.
Approach: Seed the stale export, provide a concise upstream-style prompt about removing a deleted public subpath, and verify the manifest rather than relying on a broad test suite.
Verification: Run
python test_outputs.pyfrom the task root. The verifier must inspectpackage.jsondirectly and report whether the stale history-file export has been removed without adding a replacement deleted-path source file.Risk: The main risk is that the actual manifest shape may differ from a simple string export; write the verifier to handle string, array, and object export target forms recursively.
Path rules: task package is tasks/; mutable upstream checkout is tasks//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: remove-stale-history-export
Branch: task/remove-stale-history-export
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.