Notes context and matching passages

2026-09-25 — Behavior

Project and bindr association edits keep the current note and browsing context open. Explicit Open project and Open bindr links handle navigation. Pending writes disable duplicate actions, failed bindr tagging preserves a successful project mount, and the last-project guard remains. A note that moves outside the active filter stays open with an Outside current filter row until the user deliberately changes selection or filter.

Notes search builds on the previous highlighting release. List rows show two distinct matching source passages. Preview matches opens a scrollable, line-based preview with separate matching paragraphs. Repeated excerpts compact into one group; expand the occurrence count to select the exact source position. Current source is checked before selection. Changed or ambiguous content offers current matches; unsafe rendered mappings show an explicit source excerpt. A completed jump does not steal the caret on later edits.

Files and folders use native draggable subview tabs inside the resource detail workspace. Drag a tab to an edge for side-by-side views. Closing one leaves its siblings open; Views reopens closed subviews. Mounted state survives switching and docking. The ML-Dash inspector has native Params and lazy Log siblings. Outer Notes/project navigation and existing source-browser URL controls retain their separate ownership.

Verification scope

Implementation verification recorded 2,383 passing tests (5 skipped), TypeScript checking, and CUA browser checks against real-component fixtures for association failures, exact duplicate selection, stale recovery, caret preservation and resource docking. These fixture checks are distinct from authenticated deployed product acceptance, which is owned by the app release.

No production note content is changed for this documentation release.

Docs and public skills

The Notes guide owns the user-facing procedure. Its generated reference feeds the public dreamlake-notes skill. CLI/Python examples, final API operations and concurrency rules are unchanged; no runnable examples are added. The dated development and release records do not independently change skills: they describe implementation and verification, while the procedure is generated from the guide through the docs-to-skills flow.

Release screenshots

Fresh staging/product screenshots remain pending. The release browser initially opened authenticated staging, then timed out during test-note input; subsequent CUA browser access reported Browser is not available. No saved release image was produced. The release lead authorized continuing publication with this gap recorded. Earlier real-component fixture observations are not presented as new staging screenshots or clean-dependency visual acceptance.