Cosmetic plant names in source conversations

In source 1-8 and 1-9, Dave can rename a living Peashooter as Gatling Pea without changing its species or attacks. Native records already distinguish sourceCard 10 from displayCard 410, with the full living allocation ID and cell. The prior AI request contained only the real species, so neither Dave nor that individual plant could reliably recognize the visible prank.

The new optional nameplate: "gatling" observation is accepted only for a living Peashooter in the correct source 1-8/1-9 chapter with native identity. The config advertises source-plant-nameplate-v1; older requests remain valid. Dave and plant prompts receive the localized displayed name separately from the real species and a precise explanation that the label itself adds no heads, attacks or upgrades. Other native upgrades remain separate facts. No code execution, new action, plant bond, save format or provider change.

The browser companion derives the tag only from a single matching native record, including ID/generation, source chapter, epoch, real/display cards and current cell. Missing, dead, duplicate, replaced or mismatched records do not inherit it, and old hosts receive no unsupported field. Conversation labels follow the same observed nameplate while the model retains the real species. Native code and saved records remain unchanged.

Seven relevant pre-change checks pass. The new host regression fails before implementation, then all nine focused checks pass. The complete 505 NPC checks, hosted build (5/5 tasks) and typecheck (8/8 tasks) pass. Local logs: plant-prank-{baseline,red,green,npc,build,typecheck}.log. Browser/native-save and live provider verification are separate work; they are not claimed here.