Automate vendor/mieweb-ui.tgz Rebuild From the vendor/ui Submodule

[Dharp02]

Overview

Started as automation for the vendor/mieweb-ui.tgz rebuild (replacing the manual "pull submodule, rebuild, repack, commit the tarball by hand" workflow from #517). During review it became clear the tarball itself was no longer necessary — the published @mieweb/ui npm package now covers everything this app actually imports — so this PR now removes the tarball/submodule setup entirely and installs @mieweb/ui from the npm registry, plus a batch of unrelated Playwright stabilization fixes picked up along the way.

Changes

@mieweb/ui now installs from npm (^0.7.3) instead of file:vendor/mieweb-ui.tgz.
Removed the now-dead vendor/tarball infrastructure:
vendor/ui submodule (and its .gitmodules entry)
vendor/mieweb-ui.tgz, vendor/.ui-tarball-commit
scripts/build-ui-tarball.mjs (the rebuild automation this PR originally added)
scripts/ensure-ui-build.mjs (older, already-unreferenced leftover from the pre-tarball era)
"setup:ui" script in package.json
Updated stale references to the tarball/submodule in Dockerfile (dropped the COPY vendor/mieweb-ui.tgz steps in both build stages), .github/workflows/pr-preview.yml, .github/dependabot.yml, and vite.config.ts.
Archived the removed setup to .attic/mieweb-ui-tarball/ (tarball, marker file, both build scripts) instead of deleting it outright, with a README covering why it existed and exact steps to restore vendoring if a future feature needs an unreleased @mieweb/ui component.
src/lib/TeamContext.tsx: honor a ?teamId= deep link over the persisted selection so it isn't clobbered by the "pick first available" effect on load.
Playwright stabilization: replaced brittle waitForLoadState('networkidle')/waitForTimeout() calls with explicit waits across several huddle/org specs, switched large-uploads.spec.ts to committed binary fixtures instead of generating images in-page, and added a slow-DDP login retry to TeamsPage.goto().
Why npm instead of the vendored build (see #517 for the full investigation)
Two things previously blocked using the plain npm package:

Unreleased components: vendor/ui had components (Sparkline, KeyboardShortcutsOverlay) not yet on npm. Checked usage — neither is imported anywhere in this app, so this is a non-issue today.
Type duplication: linking file:vendor/ui directly (no workspace) gave the submodule its own node_modules, causing duplicate @types/react and collapsing every @mieweb/ui component's props to any. Installing from the registry avoids this the same way the tarball did — a single, flat install into the shared node_modules.
If a future feature needs an unreleased @mieweb/ui component again, vendoring can be reintroduced at that point — no need to carry the infrastructure in the meantime.

Verification

npm run typecheck — clean
npm run lint — clean
npm run format — clean
npm run test:unit — 138/138 passed
npm run build — succeeds
npm run test (Playwright e2e) — not yet run against this diff
Manually diffed the two @mieweb/ui builds (vendored vs. npm) against every component this app actually imports — only meaningful differences were in Select/Input/Textarea (multi-select, floating labels, required-asterisk styling), none of which this app uses except the required-asterisk, which renders correctly
Browser-tested the Huddle composer (RichEditor via @mieweb/ui/kerebron) specifically for the one behavioral risk identified in review — editing an existing post opens a live Yjs collab room and correctly seeds the post's existing content (no empty-editor regression); toolbar and formatting confirmed working

Out of Scope (for Now)

Migrating to npm/pnpm workspaces (would only matter if vendoring is reintroduced later)
Closes the automation gap described in #517 — the tarball is no longer part of the install path at all, so there's nothing left to automate.

[github-actions]

🗑️ Preview Environment Cleaned Up

The preview container for this PR has been deleted.

[Copilot]

Pull request overview

Automates rebuilding the vendored @mieweb/ui tarball from its submodule revision.

Changes:

• Adds commit-based rebuild detection and streaming output.
• Updates the UI submodule, tarball, marker, and dependency lock.
• Replaces the manual setup:ui command sequence with the script.

Reviewed changes

Copilot reviewed 2 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
scripts/build-ui-tarball.mjs	Implements conditional tarball rebuilding.
package.json	Routes setup:ui through the new script.
package-lock.json	Locks dependencies from the updated tarball.
vendor/.ui-tarball-commit	Records the packaged submodule revision.
vendor/ui	Advances the UI submodule revision.
vendor/mieweb-ui.tgz	Supplies the rebuilt UI package.

Suppressed comments (1)

scripts/build-ui-tarball.mjs:59

• Replacing the tarball alone leaves both node_modules/@mieweb/ui and the tarball integrity/dependency graph in package-lock.json stale. The current lockfile diff shows that a rebuild requires lock updates; on the next submodule change, npm ci can reject the new tarball while a current dev process still consumes the old installed package. Refresh the root installation and lockfile before recording the marker.

renameSync(join(UI_DIR, packedFile), TARBALL);
writeFileSync(MARKER, currentCommit + '\n');

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.