chore: rename package to relaticle/ink (v2.0.0 breaking)

[ManukMinasyan]

Summary

Pure namespace + branding rename of the package from manukminasyan/filament-blog to relaticle/ink. No behavior changes — every public model method, component API, MCP tool, route name, table schema, and config key value stays identical.

This unblocks relaticle/ink showing up on Packagist and lets Relaticle (the only known consumer) stop importing from a personal vendor namespace.

What changed

Before	After
manukminasyan/filament-blog	relaticle/ink
ManukMinasyan\FilamentBlog\	Relaticle\Ink\
FilamentBlogServiceProvider	InkServiceProvider
FilamentBlogPlugin	InkPlugin
config/filament-blog.php	config/ink.php
config('filament-blog.X')	config('ink.X')
<x-blog::post-card> etc.	<x-ink::post-card> etc.
view('blog::pages.show')	view('ink::pages.show')
--tag=filament-blog-{config,views,migrations,translations}	--tag=ink-*
Package description	"Filament-native content publishing for blog, docs, and AI-citable articles."

Added keywords, homepage, and support fields to composer.json.

What did NOT change

• Database tables: blog_posts, blog_categories, blog_tags, blog_post_tag — no data migration required
• Route names: blog.index, blog.show, blog.category, blog.preview, blog.feed, blog.tag — public API contract preserved
• URL prefix default: still /blog (configurable via config('ink.prefix'))
• All public model methods, component APIs, MCP tool signatures, and Blade component props

Diff stats

83 files changed, 492 insertions(+), 375 deletions(-) — mostly mechanical sed across src/, resources/, database/, tests/, and docs/.

Migration (for downstream apps)

composer remove manukminasyan/filament-blog
composer require relaticle/ink:^2.0

See UPGRADING.md for the consumer-side sed recipe.

Test plan

• All 23 package Pest tests pass locally
• vendor/bin/pint --test passes
• No ManukMinasyan / FilamentBlog references in src/, resources/, config/, database/, tests/, routes/, composer.json, README.md, docs/content/, CHANGELOG.md
• CI green
• Tag v2.0.0 after merge
• Register relaticle/ink on Packagist
• Mark manukminasyan/filament-blog as replaces: relaticle/ink on Packagist (or abandon with replacement pointer)

Followups (not in this PR)

• Update Relaticle's composer.json and namespace usages — separate PR #211 against relaticle/relaticle main
• Rebase in-flight v1.5.0 listing-SEO / FAQ / HowTo schema work onto the renamed main → release as v2.1.0

[Copilot]

Pull request overview

Mechanical namespace + branding rename of the package from manukminasyan/filament-blog to relaticle/ink. Service provider, plugin, view namespace, Blade component prefix, config file, and publish tags all renamed. Database tables, route names, and the /blog URL prefix are intentionally preserved for compatibility.

Changes:

• Renamed PHP namespace, service provider, plugin, config file, view namespace, and Blade component prefix throughout src/, resources/, database/, tests/, routes/, composer.json.
• Added UPGRADING.md and CHANGELOG.md 2.0.0 entry; updated composer.json metadata (keywords/homepage/support).
• Updated docs site (README, docs/) to point at the new repo URL and use the new namespace/component examples.

Reviewed changes

Copilot reviewed 82 out of 83 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
composer.json	Renamed package, namespace, provider; added keywords/homepage/support.
config/ink.php	New config file replacing config/filament-blog.php (imports App\Models\User directly — fragile).
routes/web.php	Updated controller import & config key; fallback prefix incorrectly changed to 'ink'.
src/InkServiceProvider.php	Renamed class; $name and $viewNamespace changed.
src/InkPlugin.php	Renamed class and resource discovery FQN.
src/Models/*.php, src/Enums/PostStatus.php	Namespace + factory imports updated; config keys swapped.
src/Filament/Resources/**/*.php	Namespace updates; directory('blog') → directory('ink') for uploads (silent breaking change).
src/Mcp/Tools/*.php	Namespace updates only.
src/Components/*.php, src/Http/Controllers/BlogController.php, src/BlogSitemapGenerator.php	Namespace + view name + config key updates.
resources/views/**/*.blade.php	<x-blog::*> → <x-ink::*>, config('filament-blog.*') → config('ink.*').
database/factories/*.php	Namespace + config key updates.
tests/**/*.php	Namespace, provider, and config key updates.
README.md, CHANGELOG.md, UPGRADING.md	Branding/usage docs updated; v2.0.0 entry + upgrade recipe added.
docs/**	Namespace, repo URL, publish tags refreshed (docs/app.config.ts partially updated — owner & titles still reference old name).

Comments suppressed due to low confidence (2)

docs/app.config.ts:15

• docs/app.config.ts was only partially updated as part of the rename: repo is now ink, but owner is still ManukMinasyan, and the docus.title/seo.title/description strings still say "Filament Blog". The github edit links will resolve to https://github.com/ManukMinasyan/ink, which is not the repo. Update owner to relaticle and refresh the title/description strings for consistency with the new branding.

export default defineAppConfig({
    docus: {
        title: 'Filament Blog',
        description: 'Headless blog package for Filament with SEO, MCP tools, and publishable components.',
    },
    seo: {
        title: 'Filament Blog',
        description: 'Headless blog package for Filament with SEO, MCP tools, and publishable components.',
    },
    github: {
        repo: 'ink',
        owner: 'ManukMinasyan',
        edit: true,
        rootDir: 'docs'
    },

src/InkServiceProvider.php:15

• The $name static property changed from 'filament-blog' to 'ink'. spatie/laravel-package-tools uses this to derive the migration filename prefix (e.g. create_filament-blog_table.php → create_ink_table.php) and other publish artifacts. If any existing installs have already published migrations under the old name, or if any test fixtures/CI rely on the old prefix, this rename could cause migration conflicts or duplicate runs. Worth verifying the package has no database/migrations/create_filament-blog_table.php style files left behind, and noting the migration tag rename in UPGRADING.md (already done) is sufficient.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.