InfraBench

nplus1 × Zendo

Published attempt

0.82 · Partial reward

v9m-rl-learnability-tp8 via opencode

Attempt scoring

Weighted checks

  • Failed
    core engine and unrelated capabilities are unchanged
    Reward weight 4%
  • Passed
    web-ag resolves web and renders its managed helper
    Reward weight 4%
  • Passed
    web-ag pins ag-charts-community
    Reward weight 1%
  • Passed
    web-ag pins ag-charts-enterprise
    Reward weight 1%
  • Passed
    web-ag pins ag-charts-react
    Reward weight 1%
  • Passed
    web-ag pins ag-grid-community
    Reward weight 1%
  • Passed
    web-ag pins ag-grid-enterprise
    Reward weight 1%
  • Passed
    web-ag pins ag-grid-react
    Reward weight 1%
  • Passed
    client entrypoint configures both AG license managers
    Reward weight 8%
  • Passed
    AG modules register exactly once across a client reload
    Reward weight 8%
  • Passed
    standalone AG exposes the browser license env
    Reward weight 3%
  • Passed
    standalone AG documents the managed client setup
    Reward weight 2%
  • Passed
    web-ag contributes through a web-owned client seam
    Reward weight 2%
  • Passed
    web-posthog contributes through the shared client seam
    Reward weight 4%
  • Passed
    standalone PostHog behavior is preserved
    Reward weight 4%
  • Passed
    standalone PostHog contains no AG output
    Reward weight 2%
  • Passed
    AG and PostHog execute together in plugin order 1
    Reward weight 6%
  • Passed
    AG and PostHog execute together in plugin order 2
    Reward weight 6%
  • Failed
    web-ag and infra establish one shared input map
    Reward weight 4%
  • Failed
    combined env map is stable in plugin order 1
    Reward weight 2%
  • Failed
    combined env map is stable in plugin order 2
    Reward weight 2%
  • Passed
    web-ag and infra classify the license for Vercel
    Reward weight 2%
  • Passed
    Vercel env behavior is stable in plugin order 1
    Reward weight 3%
  • Passed
    Vercel env behavior is stable in plugin order 2
    Reward weight 3%
  • Failed
    web-ag and infra expose the license through local env
    Reward weight 3%
  • Failed
    local env preserves AG and Google in plugin order 1
    Reward weight 2%
  • Failed
    local env preserves AG and Google in plugin order 2
    Reward weight 2%
  • Passed
    plain web and infra contain no AG-specific output
    Reward weight 6%
  • Passed
    repeated apply is byte-for-byte idempotent
    Reward weight 2%
  • Passed
    apply preserves project-owned package keys
    Reward weight 3%
  • Passed
    removing web-ag preserves PostHog and shared instrumentation
    Reward weight 6%
  • Passed
    repository smoke and downstream lint coverage include web-ag
    Reward weight 3%

The official reward is authoritative; verifier hard gates can override the visible sum of checks.

Agent input

Instruction

# Add composable AG Grid and AG Charts Enterprise support to n1x

Introduce a `web-ag` capability that requires `web` and adds the following
packages to generated web applications:

- `ag-charts-community`, `ag-charts-enterprise`, and `ag-charts-react` at
  `14.0.0`.
- `ag-grid-community`, `ag-grid-enterprise`, and `ag-grid-react` at `36.0.0`.

The capability must provide managed client setup that reads
`NEXT_PUBLIC_AG_GRID_LICENSE_KEY`, applies it to both AG Grid Enterprise and AG
Charts Enterprise when configured, and registers
`AllEnterpriseModule.with(AgChartsEnterpriseModule)` exactly once, including
across development reloads.

Make the Next.js client instrumentation entrypoint composable. The `web`
capability should own a generic marker-based entrypoint, while `web-posthog` and
`web-ag` contribute their own initialization through it. PostHog must continue
to work when selected alone, and both capabilities must work together in either
requested plugin order. Keep the concrete PostHog and AG setup in their managed
`web/src/_lib` modules rather than duplicating it in the entrypoint or feature
components.

Add the browser-visible license value to the normal generated web environment
workflow. When `infra` is selected, accept it through
`TF_VAR_web_secret_env_values`, expose it through `just web env`, and pass it to
Vercel. Ignore blank values in that map. Vercel entries whose names start with
`NEXT_PUBLIC_` are public and should be marked non-sensitive; other composed
values remain sensitive. Preserve the existing Google-auth secret-map and local
environment behavior while introducing this generic composition seam.

Keep the capability isolated and lifecycle-safe:

- `web-ag` must work without `infra`.
- Projects that do not select `web-ag` must not gain AG dependencies, license
  declarations, setup code, or guidance.
- Repeated apply operations must be idempotent.
- Removing `web-ag` must clean its managed helper, environment declaration,
  guidance, and instrumentation contribution without removing PostHog or the
  shared instrumentation entrypoint.

Implement this through n1x's existing declarative plugin actions. The core
engine and unrelated capabilities should not need changes. The existing shared
`web` plugin manifest, client-instrumentation template, and Vercel template are
in scope, as are the `web-posthog` capability and `web-auth` manifest, where
needed to establish the shared seams and preserve their behavior.

Update generated guidance, downstream lint coverage, and smoke coverage.