Tracking: Remote spaces & content browsing fixes (post PR #52)

[nsheaps]

Tracking Issue

Follow-up bugs and improvements identified after PR #52 for remote spaces and content browsing.

Issues

• Space details and listing show 0 for pages and storage used #59 — Space details and listing show 0 for pages and storage used
• Remote space file browser shows demo space files instead of remote content #60 — Remote space file browser shows demo space files instead of remote content
• Space details action buttons should be inline with short labels #61 — Space details action buttons should be inline with short labels
• Remote space sidebar nav, folder structure, and .cept.yaml configuration #62 — Remote space sidebar nav, folder structure, and .cept.yaml configuration
• Add GitHub icon button and page menu for remote repo pages #63 — Add GitHub icon button and page menu for remote repo pages
• Remote repo page URLs replace / with - causing collisions #64 — Remote repo page URLs replace / with - causing collisions
• 404 handling and branch names with / in remote space URLs #65 — 404 handling and branch names with / in remote space URLs

Priority Order

1. Remote repo page URLs replace / with - causing collisions #64 — URL path encoding (foundational, affects all remote page routing)
2. 404 handling and branch names with / in remote space URLs #65 — 404 handling and / in branch names (foundational, affects URL parsing)
3. Remote space file browser shows demo space files instead of remote content #60 — File browser shows wrong files (core functionality broken)
4. Remote space sidebar nav, folder structure, and .cept.yaml configuration #62 — Sidebar nav, folder structure, .cept.yaml (core content model)
5. Space details and listing show 0 for pages and storage used #59 — Pages/storage stats showing 0 (data display)
6. Add GitHub icon button and page menu for remote repo pages #63 — GitHub icon button and page menu (UX feature)
7. Space details action buttons should be inline with short labels #61 — Action button layout (cosmetic UX)

Notes

Issues #64 and #65 should be tackled first as they're foundational to how remote content URLs work. #60 and #62 fix core content loading. The rest are UX improvements.