26A-30 — Command Readiness Checklist

Readiness Phrases

Readiness Checklist

• Future command must be installed only after explicit approval in a later phase.
• Future command install approval must be separate from actual one-row write approval.
• Future command must support inspect/dry-run mode before write mode.
• Future command must require exact approval phrase: SAVE_ONE_DRAFT_SHIFT.
• Future command must require exact one-row limit.
• Future command must use confirmed target table and columns from 26A-24.
• Future command must force unpublished/draft status.
• Future command must force employee notifications disabled.
• Future command must force employee self-view disabled.
• Future command must immediately print created row id after a future write.
• Future command must immediately print rollback instructions after a future write.
• Future command must report affected row count.

Future Command Requirements

• Command name should be clearly HD-specific.
• Command must refuse to run without exact approval phrase.
• Command must refuse to run without row limit of exactly one.
• Command must refuse to run if target table cannot be confirmed.
• Command must refuse to run if required columns are missing.
• Command must refuse to run if publish status would be enabled.
• Command must refuse to run if employee notification would be enabled.
• Command must refuse to run if employee self-view would be enabled.
• Command must produce a manager-readable result packet.
• Command must not depend on Payfast Office code or paths.

Future Command Required Outputs

• Mode used: inspect / write / rollback-inspect / rollback.
• Target table name.
• Target row count.
• Approval phrase match status.
• Payload preview.
• Created row id after future write.
• Test token after future write.
• Rollback phrase required.
• Rollback command preview.
• Affected row count.
• Publish status remained disabled.
• Notification status remained disabled.
• Employee self-view remained disabled.

Future Command Prohibited Actions

• No schedule publishing.
• No employee text messages.
• No employee email notifications.
• No employee self-service visibility.
• No payroll changes.
• No POS changes.
• No reservation changes.
• No payment changes.
• No waiver changes.
• No customer profile changes.
• No unavailable-block changes.
• No conflict-review changes.
• No hard conflict blocking.
• No automatic scheduling.

Future Rollback Requirements

• Rollback must require exact rollback phrase: ROLLBACK_ONE_DRAFT_SHIFT.
• Rollback must require created row id.
• Rollback must require test token or phase marker.
• Rollback must inspect before delete.
• Rollback must affect no more than one row.
• Rollback must refuse published rows.
• Rollback must refuse rows not created by the controlled test.
• Rollback must report affected row count.
• Rollback must not touch employee, payroll, POS, reservation, payment, waiver, customer, unavailable-block, or conflict-review records.

No-Write Proof

• 26A-30 routes are GET-only.
• 26A-30 controller imports Route only and does not import DB, Schema, Artisan, Process, or any model.
• 26A-30 controller does not call insert, create, save, update, delete, destroy, truncate, dispatch, event, mail, notification, queue, broadcast, Artisan, Process, or migration actions.
• 26A-30 does not create app/Console command files.
• 26A-30 does not modify routes/console.php.
• 26A-30 views only display readiness checklist text.
• 26A-30 smoke test checks file and route presence only.

Safety Locks

• No ENV changes.
• No database writes.
• No database deletes.
• No migration creation or execution.
• No Artisan command creation or registration.
• No real draft shift save.
• No real rollback or cleanup command is installed.
• No published schedule.
• No employee self-view change.
• No employee text message.
• No employee email notification.
• No payroll, POS, reservation, payment, waiver, or customer profile changes.
• No hard conflict blocking.
• No automatic scheduling.
• No Payfast Office file, route, controller, or database action.
• This phase contains no POST route and no write endpoint.

Route Readiness

Phase Trail

Next Step Notes

• Recommended next safe phase: 26A-31 — Controlled One-Row Draft Save Command Install Plan / Still No Write.
• Do not install a command from 26A-30.
• Do not run a command from 26A-30.
• Do not create a draft shift from 26A-30.
• Do not add a POST/write route in this phase.
• Do not send employee notifications.
• Do not publish schedules.