iName Dev Log · Oct 3

iName fixed 'bleeding' and 'breaking' today. Bleeding: data leaked between profiles — one profile's context seeping into another's recommendations; with isolation repaired, each profile keeps to itself now. Breaking: the naming-evaluation flow had gaps — the AI-review and batch-evaluation routes are wired back, with the recommend page taking the biggest share of the surgery. Naming is serious business; users hand their birth data to a profile, and a profile must not carry someone else's flavor.