STAR WARS DEFAULT DEMO PORTRAITS - 18 October 2026
Run after the existing Star Wars team renaming package. Existing company/employee keys are explicit mappings. No local numeric EMP_ID is used. Four original official images are embedded in the data SQL, so the SQL package does not need internet access or SQL Server filesystem access.

Mappings: AFORBES/0901633 Leia, AFORBES/0140765 Luke, AFORBES/9053433 Ahsoka. User authorised choosing an existing record for Obi-Wan: T1000/0007910. That fourth record receives only a fictional Employee name/FullName, Personal Known_As and portrait. No login, membership, employee number, company, hierarchy, role, department, assessment or payroll values are reassigned. Its user display name is intentionally outside this bounded update.

Review mappings against Dev Lighter before execution. Update both the data SQL mapping tuples and mapping JSON together if target keys differ. Retained originals stay in the target-local __Codex_StarWarsPortraitBackup table, never in this distributable package. Reruns preserve the first before-image and reject unexpected photo/name drift.

Run-StarWarsPortraits.ps1 -Mode DryRun -ExpectedDatabase <database> -ExpectedMachine <SQL machine>
Supply HRF_SQL_CONNECTION_STRING securely. Then use -Mode Rehearse -AllowDemoChanges to test apply AND restore under an outer rollback. Apply uses -Mode Apply -AllowDemoChanges. Verify uses -Mode Verify. Restore uses -Mode Rollback -AllowDemoChanges. The explicit runner selects only the four named .sql files and stops on errors.

The transaction briefly locks Employee and Personal and temporarily disables t_PAY_Personal and t_Upd_Employee if originally enabled. It restores their state before commit; rollback restores transactional DDL after any error. This avoids photo-trigger payroll queues and unrelated employee business processing. Photo timestamp and audit triggers retain their normal state. Existing unrelated queues are not deleted. Run in a quiet demo maintenance window because concurrent activity can wait on these brief locks. This is an explicit demo package, not an automatic application upgrade.

Do not re-run the broader three-person rename package on the current local database merely to add photos. It is already applied there. For Dev Lighter, review its own guarded rename/department package and isolation requirements first, then this companion. No Dev Lighter execution has occurred in this task.

Sources: official StarWars.com Databank images, with exact URLs and hashes in Portrait_Mapping_and_Sources.json. Images remain third-party material. No generated portraits are used. Appearance evidence is separate from production workflow QA.
