T-6G17-explorer-markdown-landing-list

Status: closed/done · Impact: medium · Complexity: medium

Goal

The notes landing page filters a flat list of every note in scope, fed by the frontmatter index. After the Browse/Notes unification (#1302–#1305) the tree shows every file kind, but the landing list is still markdown-only and still rides the whole-corpus index sweep. Decide what the list should enumerate and which read feeds it — the follow-up the unification plan parked (“markdown-only landing list, wire/walk decision”).

Today

Location	Role today
solutions/determined/experiences/notes/app/pages/apps/notes/index.vue	The landing page: filter over a flat list of every note in scope, rows labeled by vault
solutions/determined/experiences/notes/app/stores/notesVault.ts	The frontmatter index the list reads — the “wire”
solutions/determined/packages/shell/app/components/ShellVaultBrowsePane.vue	The unified tree host, fed by depth-1 vaultQueryNodes pages — the “walk”

Proposed

A recorded decision plus its implementation: either the landing list stays markdown-only on the index (and says so), or it becomes a file list riding the same paged vaultQueryNodes read the tree uses — one enumeration contract for both surfaces.

Approach

1. Decide the contract: what does “every note” mean on the landing page post-unification, and is the index sweep the right cost for it?
2. Implement whichever side wins; align the empty-scope and truncation stories with the tree’s.

Files to touch

Location	Kind	Change
solutions/determined/experiences/notes/app/pages/apps/notes/index.vue	modify	The list’s source and its filter contract

Acceptance criteria

• AC-1: The wire/walk decision is written down (here or in a decision doc) and the landing page’s behavior matches it.

Out of scope

• The display relabel (T-6OQZ).

Dependencies

• none

Discovery context

• Parked as an open follow-up in the tree-unify plan when #1305 merged the Browse/Notes surfaces.

---

← Back to Tasks