Console Laravel Package

Product Decisions This Supports

• Build vs. buy for RPG tooling: Adopting Console 0.5 replaces custom project validators, battle-simulation harnesses, and save-migration scripts with one maintained CLI. For teams already using Ichiloto, this is primarily an adopt/buy decision, not a build decision.
• Roadmap investment in save compatibility: ichiloto upgrade creates assets/Data/save-compatibility.php, giving later releases an explicit place to describe renamed or removed content. PM should treat versioned save envelopes as a post-launch architecture commitment, not a one-off migration task.
• CI and release quality gates: ichiloto validate loads the project as the runtime would and checks references, identity collisions, maps/NPCs, events/cutscenes, summon assignments, achievements, escape policy, equipment optimization, and save metadata without modifying content. This is suitable as a pre-merge or release gate.
• Balancing and content-tuning workflow: ichiloto battle produces repeatable reports of participants, actions, damage, states, rewards, and outcomes, and restores observed combatants afterward. This supports actor/enemy/skill/equipment tuning through repeated comparisons rather than bespoke scripts.
• Developer onboarding and project hygiene: Engine 0.5 scaffolding, safer overwrite handling in generators, and ichiloto edit reduce setup friction and content-authoring errors. FIGlet title art is low-risk polish, not a core adoption driver.
• Toolchain coupling decision: Console 0.5 installs compatible Editor 0.5 and Engine 0.5. PM should plan upgrades as a coordinated toolchain bump, not a standalone package update.

When to Consider This Package

Consider it when:

• You are building or maintaining an Ichiloto RPG project and want project-wide validation, repeatable battle simulation, and save-compatibility migration from a single CLI.
• You need to migrate pre-Engine-0.5 projects; ichiloto upgrade followed by ichiloto validate is an explicit, supported path.
• Your team can standardize on PHP 8.4.1+ and Symfony Console 8 and is comfortable with a globally installed Composer toolchain.
• You want content validation in CI and need a validator that reads project namespaces without mutating authored data.
• You are balancing combat content and want an observed-state report that restores participants after each simulation.
• You value an integrated Console → Editor → Engine dependency graph with tested installation paths over assembling separate internal scripts.

Look elsewhere when:

• You are evaluating a Laravel web application dependency. This is a PHP game-authoring CLI, not a Laravel library, and likely does not belong in a typical Laravel app's composer.json.
• You cannot meet PHP 8.4.1+/Symfony Console 8, or you need long-term support on older PHP.
• You need library-level APIs embedded directly in an application rather than a global CLI.
• You require a stable 1.0+ API surface; 0.x tooling and lockstep Editor/Engine versions imply upgrade churn.
• Your combat rules or content model diverge from Ichiloto Engine 0.5, because the validator and battle reports encode that runtime's contracts.

How to Pitch It (Stakeholders)

Executives: Console 0.5 reduces the cost and risk of shipping RPG content by replacing ad hoc validation, combat balancing scripts, and save-migration guesswork with one maintained command set. The strongest business case is save continuity and release confidence: upgrade establishes explicit save-compatibility metadata, and validate catches broken references and content contracts before they reach players. The trade-off is a modern runtime baseline (PHP 8.4.1+) and coordinated upgrades across Console, Editor, and Engine.

Engineering: Adopt it as the project's developer toolchain: run ichiloto validate in CI, use ichiloto battle for repeatable balance reports, and require ichiloto upgrade once for legacy projects before opening old saves with the new runtime. The release includes functional coverage for scaffolding, legacy upgrades, non-mutating validation, battle-state restoration, and isolated installation of the full dependency graph, which lowers integration risk. Plan for 0.x API movement and pin the toolchain version per project. Do not introduce it into a Laravel web app unless that app is actually part of an Ichiloto game pipeline.