[brunokktro]

Re-pins agent-dashboard from 9fe26a82 to 90d102fb for release 3.3.2.

User-visible changes

• The KiroCrew wrapper retries backend discovery for up to 15 seconds after an app update, so a transient restart no longer leaves a stale 502 screen.
• Returning to Logs restores the exact selected .log file from a strictly validated ?file= query.
• A detached idle shell still expires after 15 minutes, while a foreground command or agent remains alive for up to 8 hours and reattaches to the same PTY.

No manifest capability changed: the same UI entry, backend entry point, permissions and skill remain declared. Only source.ref changes in this catalog.

Verified

• Source commit: d4c44b392dd66f752229df6714d937be17fadef5.
• Release commit: 90d102fbf4eafcfda2a0b26898e59bfcd83400d6.
• Tag v3.3.2 resolves to the source commit and was not moved after creation.
• The exact release tree contains 223 files, including frontend/dist/index.html and ui/dist/index.mjs.
• Release scanner positive control detected all 15 classes; tree and archive scan returned CLEAN; remote bundle verification returned ALL MATCH.
• Agent Dashboard backend: 132 tests passed and Ruff passed.
• Frontend: 11 tests passed, Oxlint reported zero warnings/errors, and the production build passed.
• KiroCrew wrapper: 4 tests passed and the production build passed.
• User-facing validation in KiroCrew 0.8.0.9: returning to the app reopened Logs, a real agent turn finished while detached, and the same Console session returned with [reattached].
• KiroCrewApps: 522 tests passed with the declared tools/requirements.txt; tools/validate.py returned OK with the same three pre-existing warnings; tools/format.py reported already normalized.
• The catalog branch matches current upstream main except for this one release-pin replacement.

[brunokktro]

Superseded by #57. This branch inherited the fork main ancestry from before the previous catalog updates, so GitHub attributed unrelated upstream changes to this PR even though the final file content was correct. #57 starts at the current upstream main commit and has the intended one-file, one-line pin replacement.