v0.1.8

Highlights

Adds four new commands.install.* keys consumed by escalated-laravel v1.2.3's reordered install flow (escalated-laravel#89, fixes escalated-laravel#88):

• seedingPermissions — task label for the permission seeder
• runningMigrations — task label for the migration step
• runMigrationsConfirm — interactive prompt asking the user whether to auto-run migrations + seeding during install
• stepSeed — printed instruction shown when the user opts out of auto-run

The seedingPermissions key was the immediate cause of the bug visible at escalated-laravel#88 — the install command referenced the key but it didn't exist anywhere, so the French task label rendered the literal escalated::commands.install.seeding_permissions string instead of a translation.

All 14 locales translated; native artifacts (Rails YAML, Symfony YAML, Spring properties, Django/WP/Phoenix gettext) regenerated. validate_locales.py reports key parity.

Pipeline fix

The publish workflow was rebuilding every ecosystem from manifests with hard-coded versions (most stuck at 0.1.0 since project start, npm at 0.1.7 from a manual bump). When v0.1.8 was originally tagged earlier today, the npm job tried to publish 0.1.7 again and got 403'd by the registry; the others would have re-uploaded their stale 0.1.0 packages or no-op'd.

Added scripts/stamp_version.sh and a "Stamp version from tag" step in every publish job, so the tag is the single source of truth and ecosystems can't drift out of sync again. All six ecosystem manifests bumped to 0.1.8 so the source tree matches.

Full Changelog: v0.1.7...v0.1.8