Repository navigation
Commit 02be1fd
fix(workspace): count unsynced memory against the workspace's own setting
Found end-to-end, not by unit tests. Against a live backend, `status` reported
`{local: 14, unsynced: 14}` while `sync` on the same project answered
`{gated: true, skipped: 14}` — the menu headline promising a backlog that the
sweep then refused to move.
`pendingCount` gated only on the pilot flag, while `backfill` also refuses when
the BOUND WORKSPACE has memory switched off. So on a workspace with memory
disabled, every local block counted as outstanding and no action could clear it.
This is the drift `partitionPending` was extracted to prevent — the extraction
made the comparison shared but left the two gates different, which is the same
bug one level up. Both now ask the same question.
Regression coverage for this is the end-to-end run, not a unit test: the unit
suite's temporary project has no memory blocks, so an assertion there would pass
whatever the gate did.
Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_012Q51zFUmPg1WwtS5CrGJE61 parent ae80f16 commit 02be1fd
1 file changed
Lines changed: 10 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
658 | 658 | | |
659 | 659 | | |
660 | 660 | | |
661 | | - | |
| 661 | + | |
| 662 | + | |
| 663 | + | |
| 664 | + | |
| 665 | + | |
| 666 | + | |
| 667 | + | |
| 668 | + | |
662 | 669 | | |
663 | 670 | | |
| 671 | + | |
| 672 | + | |
664 | 673 | | |
665 | 674 | | |
666 | 675 | | |
| |||
0 commit comments