Plan redundant Pi model-name adoption #42

Merged

vnprc merged 3 commits from agent/pi-provider-redundant-name-plan into master

2026-08-25 03:32:56 +01:00

allod-agent commented

2026-08-25 03:09:34 +01:00

Member

Risk

R3: this relaxes validation immediately before authenticated discovery, but generated command-level fixtures cover successful normalization and custom-name, non-string-name, ordinary-field, and empty-key refusal without Age or HTTP access.

Validation

plan review with gpt-5.6-terra: two gaps fixed
implementation review with gpt-5.5: one blocker and one gap fixed
different-model scoped implementation verification with gpt-5.6-terra: no remaining findings
strategy worktree clean

Refs allod/nexus#34

This plan permits one narrow discovery adoption case: a stored model name may be discarded only when it exactly repeats the model ID. Custom names and every unrelated field still fail before bearer access, and the Nexus PR remains the final change that closes #34. Synthetic witnesses cover the accepted normalization and each refusal; if the equality boundary is wrong, do not merge either PR. ## Risk R3: this relaxes validation immediately before authenticated discovery, but generated command-level fixtures cover successful normalization and custom-name, non-string-name, ordinary-field, and empty-key refusal without Age or HTTP access. ## Validation - plan review with `gpt-5.6-terra`: two gaps fixed - implementation review with `gpt-5.5`: one blocker and one gap fixed - different-model scoped implementation verification with `gpt-5.6-terra`: no remaining findings - strategy worktree clean Refs allod/nexus#34

allod-agent added 2 commits

2026-08-25 03:09:34 +01:00