Commit 0dc6483
committed
fix(cli): release the pin when config set writes the selection order
`ocx config set` is fully generic -- it setPaths any dotted path, validates,
and saves -- so writing codexAccountPriorities through it stored the new
order and left activeCodexAccountPinned untouched. Nothing self-heals that:
releaseDrainedCodexAccountPin only fires on a pin whose account is drained,
so a pin on a healthy account kept capping the tier ceiling and the order
just written had no visible effect. The documented rule that any priorities
write releases the pin was true only through `ocx account priority` and the
management route.
`import` is deliberately not covered. That file supplies its own pin, so it
is a statement rather than a leftover.
Found by CodeRabbit on #715.1 parent b4b3cf6 commit 0dc6483
2 files changed
Lines changed: 46 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
| 2 | + | |
2 | 3 | | |
3 | 4 | | |
4 | 5 | | |
| |||
102 | 103 | | |
103 | 104 | | |
104 | 105 | | |
| 106 | + | |
| 107 | + | |
| 108 | + | |
| 109 | + | |
| 110 | + | |
| 111 | + | |
| 112 | + | |
| 113 | + | |
105 | 114 | | |
106 | 115 | | |
107 | 116 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
178 | 178 | | |
179 | 179 | | |
180 | 180 | | |
| 181 | + | |
| 182 | + | |
| 183 | + | |
| 184 | + | |
| 185 | + | |
| 186 | + | |
| 187 | + | |
| 188 | + | |
| 189 | + | |
| 190 | + | |
| 191 | + | |
| 192 | + | |
| 193 | + | |
| 194 | + | |
| 195 | + | |
| 196 | + | |
| 197 | + | |
| 198 | + | |
| 199 | + | |
| 200 | + | |
| 201 | + | |
| 202 | + | |
| 203 | + | |
| 204 | + | |
| 205 | + | |
| 206 | + | |
| 207 | + | |
| 208 | + | |
| 209 | + | |
| 210 | + | |
| 211 | + | |
| 212 | + | |
| 213 | + | |
| 214 | + | |
| 215 | + | |
| 216 | + | |
| 217 | + | |
181 | 218 | | |
0 commit comments