Instagram clone test: wire the run matrix (baseline vs anti-laziness)

[suleimansh]

Part of #290. Depends on the spec + rubric (#292).

Codify the runs in vikejs/compare-ai-generations instead of ad-hoc manual sessions, so results are reproducible and come with the bench HTML report. Work happens in that repo; this issue tracks it here.

• Add an instagram spec to the catalog, generated from the Instagram clone test: define the spec + grading rubric #292 checklist.
• Profiles = prompt variants:
  1. bare "build an Instagram clone" (baseline, expected to produce a minimal PoC)
  2. baseline + the anti-laziness boost (https://gist.github.com/brillout/8cf6b2b3b4708d0a4cac192b87cfb97c)
  3. later, once Dogfooding: publish the vike-* extension packages to npm (unblocks --compose-extensions) #291 lands: baseline + compose-extensions framing (build on vike-auth + vike-data instead of hand-rolling), so we can measure prompts vs extensions separately
• Runs go through the bench CLI sandboxed (sbx or Docker), same model for every cell.

[suleimansh]

Built the spec + treatments and verified them against the real loadCatalog/composeTasks: new instagram spec (the #292 checklist as the judge's requirements) + baseline/boost prompt profiles (boost = bare ask + the anti-laziness push). Composes to baseline+boost only, boost extends baseline verbatim, dog-instagram untouched.

Couldn't open it on compare-ai-generations directly: forking is disabled there and I'm read-only. Staged the ready-to-apply patch + notes in gemstack PR #296. To land it, enable forking or add me (suleimansh) as a collaborator on compare-ai-generations and I'll push, or apply the patch (one git apply). compose is held for #291.

[suleimansh]

@brillout one ask to unblock this: compare-ai-generations has forking disabled and I'm read-only, so I can't push the branch or open the PR. Could you either enable forking or add me (suleimansh) as a collaborator? Then I'll push the ready commit. The change is done and verified, staged as a patch in #296.

[brillout]

The repo is now public and you should now be able to push directly to it. (Push direclty to a new branch, instead of forking: we might need to make it private again if Joel has a put a private key inside it.)