Reorder projects in the sidebar #9

New issue

Closed

opened 2026-08-09 19:53:24 -05:00 by mcp-gateway · 0 comments

mcp-gateway commented

2026-08-09 19:53:24 -05:00

Member

Filed from halfst/mpx-engine #120. Lowest priority of the nine — cosmetic, and today's manual handling is genuinely fine.

What's needed

A way to set a project's position within its folder group — writing sort_order, or a move/reorder tool.

sort_order is already returned on read by list-projects. This is the write side.

Why

Sync Operating Spec §4.1.1 notes it as a limitation and accepts it:

Mechanic: update_project (name = new glyph + title), after health is reconciled. Sidebar sort is manual (MCP can't reorder).

The sync rewrites each effort's sidebar emoji every run to mirror project health — 🛑 / ⚠️ / 🟢 when Active, ⚪ otherwise. Sorting the sidebar by health would put at-risk and blocked work at the top automatically, which is the natural companion to that rewrite. Today the order is whatever Ethan last dragged it into.

Why it's last

Nothing is blocked by this. It changes nothing about correctness, no spec rule depends on ordering, and no vault state drifts without it. Worth doing only once the other eight are done, or never.

Acceptance

Set a project's sort position within its group.
Ordering semantics documented — TickTick's sort_order values are large negative integers, and whether smaller means higher is not obvious from the payload.

Unblocks

Nothing. Filed for completeness so the §4.1.1 caveat has a home if it's ever worth revisiting.

Filed from `halfst/mpx-engine` #120. **Lowest priority of the nine — cosmetic, and today's manual handling is genuinely fine.** ## What's needed A way to set a project's position within its folder group — writing `sort_order`, or a move/reorder tool. `sort_order` is already returned on read by `list-projects`. This is the write side. ## Why `Sync Operating Spec` §4.1.1 notes it as a limitation and accepts it: > Mechanic: `update_project` (`name` = new glyph + title), after health is reconciled. **Sidebar sort is manual (MCP can't reorder).** The sync rewrites each effort's sidebar emoji every run to mirror project health — 🛑 / ⚠️ / 🟢 when Active, ⚪ otherwise. Sorting the sidebar by health would put at-risk and blocked work at the top automatically, which is the natural companion to that rewrite. Today the order is whatever Ethan last dragged it into. ## Why it's last Nothing is blocked by this. It changes nothing about correctness, no spec rule depends on ordering, and no vault state drifts without it. Worth doing only once the other eight are done, or never. ## Acceptance - [ ] Set a project's sort position within its group. - [ ] Ordering semantics documented — TickTick's `sort_order` values are large negative integers, and whether smaller means higher is not obvious from the payload. ## Unblocks Nothing. Filed for completeness so the §4.1.1 caveat has a home if it's ever worth revisiting.