fix: update interactive-auth API snapshot for banner customization

[antfubot]

Summary

CI on main was failing (unit-test) because the chore: update api snapshot commit that followed feat(auth): enhance interactive auth banner customization and integration didn't include the intentional breaking API-shape change to devframe/recipes/interactive-auth's dts snapshot — only a trailing-newline diff landed for it.

Changes

• Regenerates tests/__snapshots__/tsnapi/devframe/recipes/interactive-auth.snapshot.d.ts (via TSNAPI_ALLOW_BREAKING=1 vitest -u) to match the already-merged createAuthBanner / AuthBannerFunction / CreateAuthBannerOptions API surface.

Verification

• pnpm build && pnpm test — all green (128 test files, 1457 passed)
• pnpm typecheck — passes
• pnpm lint — passes

---

Created with the help of an agent.

[coldtea-pr-lens]

◈ PR Lens

🟢 +0 new · 🟠 ~1 changed · 🔴 -0 removed · 0 flows · 1 file · commit b411f14

Architecture

1 component touched across 3 lanes.

Open full size

Data flow

No data-flow sequence changed in this PR.

Drill down

Devframe Core Engine — 1 component

🟡 CHANGED Single-Tool Instance Shell

Hosts devframe instance recipes, lifecycle, and interactive auth helpers

• tests/__snapshots__/tsnapi/devframe/recipes/interactive-auth.snapshot.d.ts:5-35

View

• Architecture lens
• Data flow lens
• Expand every detail
• Show unchanged neighbours

Tip

Show unchanged neighbours lists the components this change did not touch alongside the ones it did, so the drill-down shows what the changed code sits next to.

🪧 More tips

• Run PR Lens on your own machine: npx skills add coldteadotai/pr-lens installs the agent skill. Then tell your coding agent: "Diagram the change you just made with PR Lens and attach it to the pull request."
• Draw a diff before it is even a pull request: npx @coldtea/pr-lens-cli analyze --base origin/main reads the diff with your own model key, and npx @coldtea/pr-lens-cli render .pr-lens/graph.json draws the same lenses on your machine.
• The boxes under View are live. Tick Architecture lens or Data flow lens to choose which diagrams appear, or Expand every detail to open every drill-down at once. The comment redraws in place a few seconds later.
• GitHub will not let you zoom an image in a comment. The link under each diagram opens it full size on a page of its own, where you can.
• The CLI's render picks up .github/pr-lens.yml automatically and applies your corrections (renames, exclusions, lane pins) at draw time.
• Would you rather run it from CI on a key of your own? Add .github/workflows/pr-lens.yml with coldteadotai/pr-lens/packages/action@v0 and a model key in your repository secrets, say GEMINI_API_KEY. The Action asks Gemini by default, or OpenAI and any endpoint speaking /chat/completions through its provider input.
• PR Lens is free for open source. A star on the repository is what keeps it going.
• Push a new commit and the whole comment re-renders for the new head. An older run never overwrites a newer one, so a slow render cannot put a stale diagram back.
• The diagrams follow your GitHub theme, so dark mode gets the dark render and light mode the light one, and the moving dots show this pull request's data in motion.

---

◈ Rendered by PR Lens · crafted with ❤️ by the Coldtea team · Come say hi on Discord

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
devframe	Building	Preview	Sep 4, 2026 5:26am UTC