Fin Codex Laravel Package

Product Decisions This Supports

• Build vs. buy for admin-side knowledge base / documentation surfaces. fin-codex provides an article list with a Files tab and nested relation managers inside Filament. If your roadmap includes an internal or customer-facing "codex," docs, or article library living in the admin panel, this is a candidate to adopt instead of building tabbed article/file CRUD from scratch.
• Filament upgrade timing. The release explicitly tracks Filament 4.15 and 5.10 behavior changes (record resolution during Livewire hydration) and keeps compatibility from Filament 4.12.6 upward. That makes it a dependency to factor into your Filament upgrade tickets rather than a blocker you discover mid-upgrade.
• Vendor maintenance signal for procurement. A patch release that fixes a real interaction bug — rather than only bumping version constraints — plus a test suite rewritten to assert plugin-owned IDs instead of Filament's private markup, indicates the maintainer is investing in durability across Filament releases. Useful input to a "is this package safe to depend on" decision.
• Scope validation for feature requests. If your product needs tab-persistent state across Livewire updates in Filament resource pages, this release shows the pattern is now handled inside the package; you can defer building custom tab/schema logic yourself.

When to Consider This Package

Consider it when:

• You are building on Filament 4.12.6+ or Filament 5.x and want article/document management with file attachments and relation managers without authoring the schema and tab behavior yourself.
• You need the specific Files tab on an article list pattern, or a nested file component inside a Filament resource page, and you want the active-tab rendering handled for you.
• You value a maintainer who tests against multiple Filament minors and avoids asserting Filament's private markup — a proxy for surviving future Filament patch releases.
• You can accept a pre-1.0 dependency (v0.5.6) where minor versions may still carry behavioral or test-level churn.

Look elsewhere when:

• You need a stable 1.0+ API contract or a formal deprecation policy before adopting.
• You are not on Filament, or you are pinned to Filament versions below 4.12.6 — the compatibility envelope described here does not cover you.
• You require commercial support, SLAs, or a security disclosure process; nothing in this release indicates those exist.
• Your need is a general-purpose CMS or documentation platform rather than an in-admin article/file surface — the scope of this package is narrow by design.

How to Pitch It (Stakeholders)

For executives: fin-codex is a small, actively maintained Filament plugin that supplies an article library with file attachments inside the admin panel. Version 0.5.6 is a maintenance release: it fixes a tab-switching defect introduced by recent Filament upgrades and hardens the test suite so it no longer depends on Filament's internal HTML. The practical effect is that upgrading Filament is less likely to break this surface, and the maintainer is visibly keeping pace. It remains pre-1.0, so treat it as a low-cost accelerator rather than a long-term platform commitment.

For engineering: The fix is substantive, not cosmetic. Filament 4.15/5.10 began resolving resource records during every Livewire hydration, which built and cached the page schema before the tab update applied — causing the Files tab to render the previous tab's table. The package now keeps both the table and nested file component in the schema and resolves visibility at render time, which is the correct pattern for tab-dependent schemas. The test change is equally relevant to us: assertions moved off Filament's private markup (section persistence keys, tab strip wrappers, inactive panel wrappers) onto fin-codex-owned IDs, tab panel content presence, and mounted relation manager identity. That means the suite should hold from Filament 4.12.6 through current 5.x. Recommended action: pin to v0.5.6 or later, add a Filament-upgrade checklist item to re-run this package's suite, and avoid depending on any of its pre-1.0 internals in our own code.