Update for framework 0.7 and Tempest 3

[mikield]

Summary

The skeleton could not boot. Depends on Tempcord/framework#8; constraint is tempcord/framework: ^0.7.

Verified by installing the framework and running ./tempcord boot --register — the application boots, registers, reports Command "ping" listened. and opens the gateway.

Version constraints

	was	now
php	^8.2	^8.5 — what the framework requires
tempcord/framework	dev-master	^0.7
phpunit/phpunit	^10.0	^13.0
phpstan/phpstan	^1.10	^2.1
pestphp/pest	^2.0	removed

Pest is dropped rather than upgraded: it pins phpunit ^10, so it cannot sit beside the ^13 the framework tests against, and nothing here uses it.

Tempest 3 breakages

LogConfig became an interface. log.config.php was doing new LogConfig(...), so the application died instantiating an interface before anything else ran. It now builds a MultipleChannelsLogConfig.

phpunit.xml pointed at the 10.5 schema and set requireCoverageMetadata="true", which fails on a skeleton whose test directories are empty.

A real bug in the example command

->setFlags(Bitwise::from(MessageFlag::EPHEMERAL)->getBitSet())

setFlags takes a decimal bit field; getBitSet() returns the binary representation. So asking for EPHEMERAL (64) sent 1000000. It happened to still be ephemeral — 64 divides 1000000 exactly — but it also set five bits nobody asked for. Now uses ->get().

This is the same class of bug as dc-Ragnarok/Fenrir#134, which fixes three payloads in Fenrir itself that send binary where Discord reads decimal.

Since PingCommand is the first thing anyone reads, it now also shows an option constraint (minValue/maxValue) — something the framework has always supported without the skeleton demonstrating it.

Better first-run experience

A missing DISCORD_TOKEN produced a TypeError from inside the framework's config object, which tells a newcomer nothing:

TempcordConfig::__construct(): Argument #1 ($token) must be of type string, null given

The config now says what to do about it instead.

Note

The three workflows still target PHP 8.2/8.3 and would fail against a framework needing 8.5. I could not update them — my token lacks the workflow scope, so the push was rejected. They need php-version: '8.5' in run-tests.yml, static-analysis.yml and fix-php-code-style-issues.yml.