[brunokktro]

Re-pins agent-dashboard from 8b52af6e to 9fe26a82 for the 3.3.1 release.

What changed in the app

The dashboard reopens on the tab you were using. Inside KiroCrew an app page is an ordinary lazy React Router element, so moving to another app or Crew function unmounts it and returning mounts a fresh iframe at /. The Logs, Board or Console tab in use was lost on every excursion. The app now records its own path and restores it when it next boots at /. A deep link, or a reload while on a page, is never overridden, and a stored path that is not a live route is ignored rather than trusted.

No manifest surface changed: same ui.entry, same backend.entryPoint, same declared permissions and skills. Only source.ref moves in this catalog entry.

What I verified

• The pinned ref is the release head, and carries what the store bakes from. 9fe26a82 is the head of the app's release branch, generated by its own bin/make-release on top of main 09c1f2f8. Reading the tree at that ref: app.json reports version 3.3.1, and server.py, ui/dist/index.mjs and frontend/dist/index.html are all present. bin/init-ecosystem is 100755, so the installer stays executable.
• The app's release scan ran on the exact tree being pinned, with its positive control first: positive control: 15 classes detected, then release scan: CLEAN over 220 files. The publisher re-read every blob SHA after the write and reported ALL MATCH.
• The app's suite and build are green at that ref: 9 unit tests pass, oxlint reports 0 warnings and 0 errors, and tsc -b && vite build completes clean.
• Behaviour checked in a real browser against the built bundle, not only in unit tests: booting at / with /logs remembered lands on /logs; deep-linking to /health while /logs is remembered stays on /health; and a forged stored value (//evil.example.com) is ignored, leaving the page on / on the same origin.
• This repository's gate, on this change: pytest tests/ -q gives 522 passed; tools/validate.py gives OK: catalog is valid (3 warning(s)), and I confirmed those 3 warnings are pre-existing by running it on the unmodified file, where they are identical and all concern other apps; tools/format.py reports already normalized.
• The diff is one line. Byte-level check: 37 bytes change at a single offset, total file length unchanged, the old ref gone and the new one present exactly once, the JSON still parses and still holds 30 apps. Verified against the fork's main that catalog/official-registry.json is the only path that differs.