Technical Evaluation

Architecture fit

The package is a Laravel/Filament "kit" that composes third-party Filament plugins (hoceineel/filament-quick-action-dock, anselmokossa/filament-sentinel, mike-bronner/laravel-model-caching) plus its own kit:* artisan tooling and published assets. v0.51.2 keeps that shape: no new abstractions, one behavioural fix and three dependency bumps.
The notable architectural change is vendoring an upstream JS bundle: the kit now serves its own copy of the dock script at public/js/kit/quick-action-dock.js, produced by patching a single measurement (window.innerHeight → documentElement.clientHeight) in the upstream bundle, wired via DockDeAtalhos::servirScriptCorrigido(). That is a fork-by-copy, and it is the main thing a TPM should track.

Integration feasibility

Low effort: "Nada a instalar nem migrar." composer update plus kit:update (to lay down the patched script) plus the kit's test suite. No schema changes, no config keys, no API changes.
The PSR-4 fixture fix (#170) removes 12 does not comply with psr-4 warnings from composer install --optimize-autoloader, which is a real DX/CI-noise win for anyone installing the kit.

Technical risk

Vendored bundle drift (medium). The corrected script is a snapshot of an upstream bundle. It goes stale silently as a functional matter; the kit's mitigation is a test that flags the copy as outdated with a regeneration command. That works only if the suite is run after every composer update of the dock package — a process dependency, not a technical guarantee. Upstream issues/PRs HoceineEl/filament-quick-action-dock#2 and #3 exist, so the exit path is: upstream fix lands → delete the vendored copy.
Published vendor views/translations (low, but declared debt). The sentinel 1.3.0 views/translations are re-published raw and never edited. The release notes explicitly acknowledge these copies could be dropped in favour of the package's own, but kit:update will not delete them from already-updated projects, so removing them later becomes a breaking change. Worth logging as a future upgrade cost.
Pre-1.0 semver. At 0.51.x, the 1.2.1 → 1.3.0 sentinel bump is a minor and carries a user-facing behaviour change (403 page now distinguishes "you have the page permission but were refused elsewhere"). Low blast radius, but it changes copy users read.
Asset caching. A shipped JS file in public/js/kit/ needs cache-busting/versioning, otherwise the fix may appear not to work behind a CDN or browser cache.

Key questions

Is the patched script committed to the repo, generated at install, or regenerated only on kit:update? What happens on a fresh clone without kit:update?
Does the drift test compare content/hash against the installed upstream bundle, and does CI run it automatically after dependency updates?
What is the cache-busting strategy for public/js/kit/*?
What PHP/Laravel/Filament version ranges does 0.51.2 support, and is there a published BC/deprecation policy ahead of 1.0?
When is the upstream dock fix expected, so the vendored copy can be retired?

Integration Approach

Stack fit

Standard Composer-installed Laravel package with publishable assets, views and translations, plus kit:* artisan commands. No runtime services, no queue or storage requirements added by this release.
Blade/Livewire-based Filament stack is untouched; the fix is confined to client-side positioning logic.

Migration path

None required. Treat as a drop-in patch: composer update, then kit:update to materialise the corrected public/js/kit/quick-action-dock.js, then rebuild/clear caches (php artisan optimize:clear, view:clear) so the republished sentinel views and translations take effect.
Existing projects retain their previously published sentinel views/translations; the re-publish only affects what a fresh install/update writes. Nothing is deleted.

Compatibility

The dependency bumps (laravel-model-caching 13.2.0, playwright 1.64.1, filament-sentinel 1.3.0) are non-major and appear constraint-compatible. Confirm the kit's own composer constraints are permissive enough that projects pinned to sentinel ~1.2 do not get silently held back or forced up.
playwright is dev/test-only; no production footprint.

Sequencing

Upgrade in a non-production branch; run composer update with --optimize-autoloader to confirm the PSR-4 warnings are gone.
Run kit:update, then the kit suite — it should pass and report the copied dock script as current.
Manually verify the dock on desktop Chrome (the reported innerHeight 867 vs visible 780 case), including resize and a Livewire poll, plus one mobile viewport for regression.
Verify the sentinel 403 page copy change is acceptable to stakeholders who own user-facing messaging.
Deploy; purge CDN/asset cache for public/js/kit/.
Add a standing checklist item: after any composer update touching the dock package, re-run the kit suite and regenerate the script if flagged.

Maintenance

New recurring obligation: track the vendored dock bundle. Owners must re-run the kit suite after upstream dock releases and regenerate the copy when flagged. Budget a small recurring line item until the upstream PRs land.
Growing "published-then-orphaned" surface (12 raw sentinel view/translation copies) that cannot be cleaned up automatically. Plan a coordinated removal at a future major/minor with an explicit upgrade note.

Support

Net positive: the dock bug presented as an intermittent "button appears then slides off-screen" complaint that was hard to reproduce and often dismissed as cosmetic; the release documents a reproducible cause and a spec at wikis/specs/fix/dock-altura-do-viewport/. Support can now point to a known issue and a fix version.
Sentinel 1.3.0's clearer 403 messaging reduces permission-misconfiguration tickets ("I have the permission but still get 403").

Scaling

No impact. The change is front-end positioning and asset serving; no new I/O, queries or jobs. The laravel-model-caching minor bump warrants a sanity check on cache invalidation behaviour in high-read paths, but 13.1 → 13.2 is not expected to change semantics.

Failure modes

Stale vendored script after an upstream dock bump → regression reappears with no error raised, unless the suite runs. Highest-likelihood failure.
Browser/CDN cache serving the old bundled JS → fix looks ineffective; user reports continue post-deploy.
kit:update not run on an upgrade → project keeps the original upstream script; fix absent.
Missing/unpublished public/js/kit/ in a fresh clone or CI artefact build → dock JS 404s, dock renders unpositioned.
Sentinel view copies diverging from upstream 1.3.0 if anyone edits them despite the "never edit" convention.

Ramp-up

Low for developers: no new APIs, one command, plain PHP/Laravel conventions.
For TPM/ops: the only concept worth onboarding is the vendored-bundle lifecycle (why the copy exists, where it lives, how it is regenerated, when it gets deleted). One paragraph in the runbook plus a CI check covers it.
Overall verdict: safe, low-risk patch that fixes a real desktop UI defect; recommend adopting, with the vendored-script follow-up tracked as an owned item rather than an implicit one.