Seeder automatically generating model's relationship methods?

I have a Filament app and whenever I run the seeder, it generates unwanted relationship methods in models.

Here are the two models:

<?php

namespace Eclipse\Core\Models;

use Eclipse\Core\Database\Factories\SiteFactory;
use Eclipse\Core\Models\User\Role;
use Illuminate\Database\Eloquent\Factories\HasFactory;
use Illuminate\Database\Eloquent\Model;
use Illuminate\Database\Eloquent\Relations\HasMany;

class Site extends Model
{
    use HasFactory;

    /**
     * The attributes that are mass assignable.
     *
     * @var array<int, string>
     */
    protected $fillable = ['domain', 'name', 'is_active', 'is_secure'];

    /**
     * Get the attributes that should be cast.
     *
     * @return array<string, string>
     */
    protected function casts(): array
    {
        return [
            'created_at' => 'datetime',
            'updated_at' => 'datetime',
            'is_active' => 'boolean',
            'is_secure' => 'boolean',
        ];
    }

    protected static function newFactory(): SiteFactory
    {
        return SiteFactory::new();
    }

}

<?php

namespace Eclipse\Cms\Models;

use Eclipse\Cms\Enums\SectionType;
use Illuminate\Database\Eloquent\Relations\BelongsTo;
use Eclipse\Cms\Factories\SectionFactory;
use Illuminate\Database\Eloquent\Factories\HasFactory;
use Illuminate\Database\Eloquent\Model;
use Illuminate\Database\Eloquent\SoftDeletes;

class Section extends Model
{
    use HasFactory, SoftDeletes;

    protected $table = 'cms_sections';

    protected $casts = [
        'type' => SectionType::class,
    ];

    public function getFillable()
    {
        $attr = [
            'name',
            'type',
        ];

        if (config('eclipse-cms.tenancy.enabled')) {
            $attr[] = config('eclipse-cms.tenancy.foreign_key');
        }

        return $attr;
    }

    protected static function newFactory(): SectionFactory
    {
        return SectionFactory::new();
    }

}

This is the migration:

<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;

return new class extends Migration
{
    public function up(): void
    {
        Schema::create('cms_sections', function (Blueprint $table) {
            $table->id();
            $table->string('type');

            if (config('eclipse-cms.tenancy.enabled')) {
                $table->foreignId('site_id')
                    ->constrained('sites', 'id')
                    ->cascadeOnUpdate()
                    ->cascadeOnDelete();
//                $table->unsignedBigInteger('site_id')->nullable();

            }

            $table->string('name');
            $table->timestamps();
            $table->softDeletes();
        });
    }

    public function down(): void
    {
        Schema::dropIfExists('cms_sections');
    }
};

Now, when running php artisan migrate:fresh, there are no problems. But when running php artisan migrate:fresh --seed, the two model classes are changed. They each automatically get the relationship method:

Site:

    /** @return HasMany<\Eclipse\Cms\Models\Section, self> */
    public function sections(): HasMany
    {
        return $this->hasMany(\Eclipse\Cms\Models\Section::class);
    }

Section:

    /** @return BelongsTo<\Eclipse\Core\Models\Site, self> */
    public function site(): BelongsTo
    {
        return $this->belongsTo(\Eclipse\Core\Models\Site::class);
    }

This is not desirable, since the Site class/table is parent to almost every other model, to allow multi-tenancy separation. Also it's mostly non-sensical and unpractical (e.g. there's no way you'd ever access logs with $site->logs()).

I've tested a clean Laravel 12 app and it does not do this, so I must have added a package that's causing this. I've already excluded PhpStorm and Laravel Idea plugin (same happens without them).

Before I go any deeper, has anyone come across such a thing? LLM muchachos are not helping.

PS: Forgot to mention, in the migration, even if I use the commented line instead of the proper foreign ID spec, it still generates the methods, as long as the column name is "site_id", but if I use "site", the methods are not generated. That is wild :)