Nova Route Viewer Laravel Package

Product Decisions This Supports

• Upgrade sequencing for admin tooling: The 0.1.0 release hard-drops Laravel 10 and below, PHP < 8.2, and Nova 4 and below. This gives the team a concrete, dated forcing function to confirm our Laravel 11 / Nova 5 baseline before pulling the package forward — it belongs on the platform-upgrade checklist, not in a solo feature branch.
• Build vs. buy for internal route introspection: This remains a thin Nova card that surfaces php artisan route:list data inside the admin panel. The 0.1.0 version bump does not add product capability, so the build-vs-buy calculus is unchanged: adopt if engineers/ops routinely inspect routes through Nova, build only if we need bespoke filtering, auth-aware masking, or audit trails.
• Roadmap de-prioritization: No new features landed — only environment floors plus CI. There is no reason to schedule product or UX work around this package; treat it as infrastructure hygiene.
• Risk/roadmap input on Nova dependency: Because the package tracks Nova major versions with a hard break, every Nova upgrade now implies validating or replacing this tool. PM should record it as a pinned dependency with an owner, since an abandoned release cadence would strand us at a single Nova version.
• CI signal as a trust indicator: The addition of CI modestly raises confidence in maintenance quality, which slightly favors keeping it rather than replacing it with a homegrown card.

When to Consider This Package

Adopt when all of these hold:

• We are already on (or committed to) Laravel 11+, PHP 8.2+, and Nova 5+ — 0.1.0 is incompatible with anything older, with no compatibility shim or LTS branch.
• The team actually uses Nova as the operational surface for debugging and support, so route visibility has real day-to-day value.
• We accept a small, single-maintainer dependency whose major-version support follows Nova's lead.

Look elsewhere or build in-house when:

• We are mid-migration on Laravel or Nova. Upgrade Nova and this package together; do not attempt to stage them separately, since 0.1.0 will not install on Nova 4.
• We still run PHP 8.1 anywhere in the fleet — this release is a hard blocker and would require either a runtime upgrade or pinning to the 0.0.x line (which we should treat as unmaintained going forward).
• Route data is sensitive and must be role-scoped or withheld from the Nova panel; a raw route viewer may over-expose internal endpoint structure to non-engineering admin users.
• We need guaranteed maintenance SLAs — single-maintainer packages are a poor fit for that requirement.

How to Pitch It (Stakeholders)

For executives: This is a small internal engineering convenience tool for our admin panel, not a customer-facing component. Version 0.1.0 doesn't add features — it raises the technical floor to Laravel 11, PHP 8.2, and Nova 5, and adds automated testing. The practical consequence is a dependency that must move in lockstep with our platform upgrades. Low cost, low risk, no product impact; the only action item is sequencing it into the pending Laravel/Nova upgrade rather than letting it break the build mid-sprint.

For engineering: 0.1.0 is a breaking release: PHP 8.2+, Laravel 11+, Nova 5+ are now mandatory, with CI added. There is no functional change. Confirm your local and CI runtimes meet the new floors before bumping, upgrade Nova and this package in the same change, and note that staying on 0.0.x means staying unsupported. If the Nova coupling becomes a recurring tax, flag it and we'll evaluate an in-house route card instead.