Review follow-up for K27:
- The opened Overview area or file reaches only Overview, and the hotspot
area only Hotspots. Endpoints, Entry points and Hotspots no longer draw
or report an area opened in Overview, so the chat context names nothing
that is not on screen.
- Plan or 3D in System structure and in Behavior is part of the entry and a
step, as on the shared map. The Behavior path to a destination is a step;
the operation on the call chain and the page of direct calls stay with the
entry without being steps, so Back and Forward return to them.
- The in-view "Back" buttons of System structure and Behavior are absorbed
into the one Back beside the subtabs.
- Back, Forward or a Recent jump while typing in the Routes filter first
records the typed text as a step instead of dropping it.
- replaceNavigation also merges with the step after it, so no two equal
steps end up next to each other.
Signed-off-by: Bernhard Jackiewicz <bj@techport.io>
Hand-test finding K27: Architecture had scattered ways back with different
meanings (the Overview trail, a "Back" in System structure that walked the
focus, a "Back" in Behavior that walked the starts) and no way back from
"Show these N routes". Nothing went forward.
Architecture now keeps one place (subtab; opened area or file and Plan or
3D; route perspective and filter; System structure focus and expanded
groups; Behavior start, destination and where followed calls began) and
records it in the bounded model Galaxy uses (graph/navigation-history.ts),
with the same rules: at most 25 steps, consecutive duplicates merge, a new
navigation after Back drops the forward branch, no pushState, a Recent list
of 8 places, Alt+Left and Alt+Right only in the active workspace and not
while typing or while another surface takes the keys, a fresh history per
project.
Back, Forward and Recent sit beside the subtabs; their tooltips name the
target ("Back to Overview · django"). The old "Back" buttons in System
structure and Behavior stay in place and take the same step. "Whole system"
and the Overview trail stay as ordinary steps.
Architecture adds three refinements: typing in the route filter becomes one
step once it pauses; a choice the page makes itself (the suggested Behavior
start, a reset after reindexing) replaces the current step
(replaceNavigation), so Back never bounces on it; and the current step
keeps the newest details of its place (refreshNavigation), so a step whose
suggested start was rejected for a stale snapshot is still named after the
start the journey shows.
The views read their part of the place from the workspace and report
changes back; rendered on their own, as in their unit tests, they keep it
as their own state and offer no Back. A new tab row class avoids the
existing atlas-arch-bar meter. The concept doc now covers both workspaces.
Signed-off-by: Bernhard Jackiewicz <bj@techport.io>
Review of the hand-test fixes, K2 and K8. Restoring a history entry with
the same root (Back to another depth, or the minus button while a layer
loads) cleared the selection, so Selection details disappeared and the
chat lost its context, although commit 96fbec67 said it stays. Only the
"All graph" entry clears the selection now; another root still selects
itself once loaded.
Signed-off-by: Bernhard Jackiewicz <bj@techport.io>
Hand test K2: the concept now names the late project, cancel as Back and the empty-canvas click as history rules, as implemented.
Signed-off-by: Bernhard Jackiewicz <bj@techport.io>
Hand test K2 and K9. A click on a node made it the new root with no way
back, and a click just beside a node threw away scope, layers and path.
A bounded history (25 entries, consecutive duplicates merged, forward
branch dropped on a new navigation, no pushState) now records root,
depth, direction, edge types, open path and view. Back and Forward sit
in the scoped toolbar with tooltips naming the target, Alt+Left and
Alt+Right work outside fields, and a Recent list jumps to the last 8
roots. All graph is an entry of its own.
An empty-canvas click inside a scope now only clears the path
highlight. The scope is left only through All graph, Escape or Back.
The concept is in docs/development/pr-2068-galaxy-history.md; the
model in graph/navigation-history.ts is meant for K27 as well.
Signed-off-by: Bernhard Jackiewicz <bj@techport.io>
Add the measured browser acceptance (19 of 19 checks), the test runs on
the final tree, what was not run and why, and the remaining limits, with
ten downscaled screenshots of the fixed views beside the reproduction.
Signed-off-by: Bernhard Jackiewicz <bj@techport.io>
Reproduce every point from the 2 October review call in a real browser
against a Django 5.2.7 index and this repository as control, and record
the plan with measured causes, priorities and open decisions.
The capture script splits each interaction into numbered screenshots
with a visible cursor ring and records canvas identity, camera and the
prompt sent to the browser model, so resets, zoom direction and chat
evidence are measurable rather than described. Only 17 downscaled
images are committed; the full series stays local.
Signed-off-by: Bernhard Jackiewicz <bj@techport.io>
Record the failed first pass, integrated repairs, actual Playwright flows,
source and research decisions, same-port daemon behavior and maintainer entry
points. Include before/after screenshots and the final map recheck after login.
Archive original test logs losslessly with SHA-256 records; retain failed runs
separately instead of presenting them as successful checks.
Disclose unresolved global C lint, parser callsite coordinates, heuristic
architecture roles, manual diff narrowing and outstanding platform validation.
Signed-off-by: Bernhard Jackiewicz <bj@techport.io>
Bernhard Jackiewicz