The server exposes POST /api/v1/people/reassign and the Rust SDK has people::reassign(face_ids: &[String], person_id: Option<&str>) -> Result<()> (imogen-sdk/rust/src/people.rs:91), but the CLI's PeopleCommand (list / show / name / hide / merge / faces / status / enable) has no way to move a misgrouped face to another person — or to "unassign" it (person_id: None).
Sketch of the CLI shape, alongside the existing imogen people merge:
imogen people reassign <face-id>... --to <person> # move faces to a person, by id or name
imogen people reassign <face-id>... --unassign # person_id: None
--to <person> should resolve through the same find_person name-or-id lookup imogen people merge/imogen people show already use. imogen people faces <asset> (PeopleCommand::Faces) already prints face ids, so the natural flow is imogen people faces <asset> --ids | xargs imogen people reassign --to "Correct Name".
Not implementing this issue — filed as a tracking issue per an audit of imogen-cli's selection semantics (see PR against main from that audit).
The server exposes
POST /api/v1/people/reassignand the Rust SDK haspeople::reassign(face_ids: &[String], person_id: Option<&str>) -> Result<()>(imogen-sdk/rust/src/people.rs:91), but the CLI'sPeopleCommand(list/show/name/hide/merge/faces/status/enable) has no way to move a misgrouped face to another person — or to "unassign" it (person_id: None).Sketch of the CLI shape, alongside the existing
imogen people merge:--to <person>should resolve through the samefind_personname-or-id lookupimogen people merge/imogen people showalready use.imogen people faces <asset>(PeopleCommand::Faces) already prints face ids, so the natural flow isimogen people faces <asset> --ids | xargs imogen people reassign --to "Correct Name".Not implementing this issue — filed as a tracking issue per an audit of
imogen-cli's selection semantics (see PR against main from that audit).