Task candidate: Express acceptsCharsets flexible input formats

[Jordak]

Parent

Related to #10.

Current behavior / design

As of this issue being written, this candidate was recorded in the retired local task-candidate backlog and is being migrated to GitHub Issues as the task-candidate source of truth. No Agent Eval Lab task bundle, reference artifact, reference verification artifact, or Codex smoke trial exists for it yet.

Candidate notes

• Repository: https://github.com/expressjs/express
• Upstream PR: fix: enhance req.acceptsCharsets method expressjs/express#6088
• Candidate start commit: 8cb53ea5c3329032a1db47be019b717d8350fb0e
• Candidate reference commit inspected: 285e19dc3b6c53099f196396ffc7e769fb9555a5
• Candidate category: JavaScript API behavior
• Why interesting: compact JavaScript library task with behavior and tests.
• Risks / checks: no linked upstream issue was found during initial curation; clarify intended behavior from the PR body and tests before promoting.

Why change

The starter suite needs more varied realistic tasks before broader capability reporting. This candidate would add compact JavaScript API behavior coverage.

What to build

Triage whether this candidate should become a publishable task. If it is promoted, the eventual implementation issue should create a task bundle with pinned repo and commit, deterministic graders, a verified reference artifact, generated task card, and one fair Codex smoke trial.

Acceptance criteria

• Decide whether to promote, defer, or reject this candidate.
• If promoting, ensure the issue has enough detail to become ready-for-agent: expected behavior, grader strategy, setup constraints, and stop conditions for suspicious or resource-heavy setup.
• If deferring or rejecting, comment with the reason.

Blocked by

None - can start immediately.

[Jordak]

Triaged after source inspection. This is not a good Agent Eval Lab task candidate as currently framed.

At the candidate start commit, req.acceptsCharsets already forwarded varargs and inherited array support through accepts@2.0.0. A grader for multiple string arguments or array input would already pass before the reference commit. A grader for a single comma-separated offered charset string would fail against the upstream reference commit too. The inspected reference commit appears to be docs/style plus a redundant test, not a deterministic user-visible behavior fix.

Closing as wontfix for this candidate. If we later want this surface, it should be a new custom task explicitly scoped to implementing comma-separated offered charset support with our own reviewed reference artifact, not a reproduction of expressjs/express#6088.

[Jordak]

Closed as wontfix for this candidate. The upstream PR does not provide a deterministic behavior change suitable for our task format; see the triage comment above for the source-inspection details.