PHAYRIOSIS REBORN CONTINUATION NOTE - PHASE 5 LIVE METEOR FLIGHT
Version: 0.0.14

Purpose
-------
Phase 5 converts the persistent Phase 4 pending-meteor roll into a real server-authoritative falling entity. This phase deliberately stops before terrain destruction. Its purpose is to validate entity registration, client spawning/rendering, flight synchronization, target selection, persistence, and scheduler handoff independently from crater generation.

Added
-----
- PhayriosisMeteorEntityRegistry: registers phayriosisreborn:phayriosis_meteor using Forge RegisterEvent on the MOD bus. Kept outside the generated MCreator entity registry to avoid invasive edits.
- PhayriosisMeteorEntity: no-gravity AbstractArrow-based synchronized meteor. It steers to one target at constant speed, passes through living entities, and treats terrain/target arrival as the impact endpoint.
- PhayriosisMeteorLaunchSystem: consumes Phase 4 pending rolls only after addFreshEntity succeeds. Targets 80-120 blocks from a random Overworld player by current default settings, starts the meteor high enough to be visible, and records runtime launch/impact state.
- PhayriosisMeteorClient: client-only renderer registration. Uses the existing meteoric_rock item model at 6x renderer scale with full-bright rendering as a temporary native Phayriosis visual. No generated art is introduced here.
- PhayriosisMeteorEventData schema 2: adds active-flight, launch-attempt, successful-launch, impact, last-target, and retry fields while retaining Phase 4 scheduler data.

Important Phase Boundary
------------------------
DO NOT add crater carving, explosions, infection conversion, meteor fragments, camera shake, sound, or particles to this phase. On impact the meteor only records completion and discards itself. Phase 6 should attach terrain generation to PhayriosisMeteorLaunchSystem.onMeteorImpact after this flight path has been validated in-game.

Scheduler contract
------------------
A Phase 4 pendingMeteor flag is not consumed until the entity successfully enters the world. Failed launch attempts retry after 20 ticks. On successful launch, activeMeteor is set and PhayriosisMeteorScheduler.markPendingMeteorLaunched is called. Impact clears activeMeteor.

Testing
-------
Normal startup/world-save tests can use superflat. To make a meteor eligible quickly, set Phayriosis to at least phase 1 and move world time to day 7 (168000 ticks). Scheduler chance is currently 50% per 3600-tick eligible check. If a check misses, advance another 3600 ticks and retry. Watch the sky around the player: spawn geometry is intentionally near/above the player and the target lands 80-120 blocks away by default.

Known future hardening
----------------------
- Add stale activeMeteor recovery if an entity is externally removed/unloaded incorrectly.
- Replace temporary block-item rendering with the final large meteor visual/model only after flight validation.
- Phase 6 owns terrain-safe impact/crater generation and all destructive behavior.
