Skip to content

Readable graph workspace: cards, labels, wires and visual controls #222

Closed

Description

@mvalancy

Owner feedback from the headed review on2026-10-28: edge labels clip text, collide or sit badly; task/feature cards have tiny text, wasted space and poor structure. The core rendering goal is clean, organized, readable symbols at each detail level. This is active follow-up under #193 and #220, based on the shared geometry foundation #221; no full visual acceptance is claimed from its interaction checks.

Owned continuation: branch feat/clean-graph-symbols-20261028, starting from #221 checkpoint6ac0f48, worktree .worktrees/core-clean-graph-symbols-20261028. Visible preview http://127.0.0.1:28917 uses an isolated API/owned database; original localhost8540 data remains untouched. Keep one headed browser and scoped serial tests; heavy matrices stay in CI.

Done / evidence:

  • Headed review reproduced dim double-faded label text: group opacity0.707107 and child opacity0.707107 compound to0.5 even at full working zoom for a two-edge pair.
  • Source audit found label admission ignores other wires/arrows and drops collision checks on intermediate simulation frames. Existing text measurements and card dimensions do not define a shared reserved layout for every displayed element.
  • Source audit found type-based fixed card widths, separate duplicate wrapping paths and status/priority labels at very small sizes; compact content still reserves large footer space.

Next / acceptance:

  • Define one content/geometry contract for readable label text, backgrounds, icons and clearance. Measure real text, reserve its full footprint, and revalidate on geometry/font/detail changes. One opacity decision, legible working-size labels; do not use clipping/shrinking as admission.
  • Give cards a compact hierarchy: title first, type/actions and status/priority in reserved rows, width/height driven by content. Preserve accessible editing, Grow, expand, drag/save and source identities.
  • Use controlled detail levels so zoom removes secondary information before text becomes illegible. Card/label bounds, routes and hitboxes must consume the same layout; no canonical position writes from display-only changes.
  • Keep labels clear of cards, other labels, unrelated wires, arrows and visible UI obstacles with bounded work outside hot pan/tick paths. Defer only with accessible exact relationship access and honest counts; hiding all content cannot pass.
  • Add small actual rendered regressions for short/long/unbroken names, mixed types, parallel/opposite edges, dense crossing fixture and zoom/phone states. Assert text fits, minimum readable size, no overlaps, useful visible content and original data unchanged. Include deliberate clipping/overlap negatives and review screenshots in the headed window.
  • Commit/push coherent pieces; independent exact-source review, actual strict CI artifacts and final dev checks before closure. Retain failures and limitations.

Recovery: read this issue, PR221 and docs/architecture/schematic-connections.md; fetch the owned branch and inspect its linked PR. Coordinate before editing shared renderer/layout modules. CodeGraph techniques only; no shared library. This does not close the larger1k/10k rendering/loading, hosted or release requirements.

Merged source is 69d0493df1eb48e1190a46b8ea83e3f37f13b1ee on #223. Pre-merge CI40742791571 / Comprehensive40742791524 passed; independent final review5687953453 verified 108 strict passing cases, 72 attachments and 27 screenshots. PR223 merged via the standing dev-only native admin operation to 4a6d75d24ee664a0357aa124168f39c410625902. Parents are exactly live base058aaa70 plus reviewed source69d0493; the complete tree is the tested 6d7629392bb98a09e33e44232941a3933d0f231b. Post-dev CI40749343162 and Comprehensive40749343433 passed. Independent actual artifact acceptance is recorded in #223 (comment) strict passing cases,72 attachments,6 verified archives, matching source/base/tree. This scoped issue is accepted. The implementation boxes above describe completed code and focused evidence, not integration acceptance. Shared status/trace/connection flow fixes the5 durability failures from b33, native scrolling preserves the graph camera on short phones, and exact browser Edit retains its selected record. Active RadarChart measurement/text also use14px/500. Earlier failed and superseded runs remain retained. The reviewed composition is integrated into dev and its actual post-merge checks passed. Wire crossing/minimap and broader LOD work remain tracked in #220/#193; initial saved-position repair is an existing policy and not covered by the already-clear-fixture no-write assertion. The2k post-dev wall-clock zoom boundary (one5.665s sample) and self-host162 OS findings remain retained limits.

Fresh independent exact-source PostCSS compilation confirmed the 14px-equivalent/500/600 utilities. CI does not retain CSS bytes, so those were not claimed inspected. A stale local Vite preview was restarted without source changes and now renders the intended rules; see comment6477709156 and review5688035698.

Activity

  1. mvalancy commented on Oct 28, 2026

    @mvalancy
    MemberAuthor

    Published checkpoint 351749f, draft #223. The shared card/label geometry now has18 passing focused tests and scoped web TypeScript passes. Full/compact two-item visuals were inspected in one headed Chrome window. This is development evidence only.

    Next acceptance includes the owner's explicit requirement for headless thousands-of-node zoom-out/return-to-detail cases, cardinality/identity retention, readability/clutter and response-time evidence. Run larger tests in CI, serially; keep the local headed review lightweight. Current source paths and new tests are in #223, so recovery does not depend on this workstation.

    PR221 is in final independent artifact review with green exact-head CI; close that foundation separately before integrating this visual slice. #220 and #193 remain truthful trackers for routing/buses and full LOD completion. No additional overlapping issues are needed for this slice.

  2. mvalancy commented on Oct 28, 2026

    @mvalancy
    MemberAuthor

    Recovery checkpoint: published 6d81752, PR #223, branch feat/clean-graph-symbols-20261028. Three coherent commits are pushed: content geometry351749f, actual visual/2k gates e4f654a, and bounded placement/focus/paging correction6d81752. No new overlapping issue was opened.

    Actual first large run: CI40706957761 loaded2000 API items and5000 relationships, retained all IDs and passed clean eight-group overview geometry/accounting. First detail zoom failed5847ms/5000ms and showed zero labels. Preserve that failure; source corrections now bound failed work, exclude hidden labels, redraw only visible changed card content, and retain timing files even before a budget failure. Independent source review also caught unreachable0.08 zoom; the gate uses the real minimum0.1. The five-second limit was not relaxed.

    Current local evidence:22 geometry/budget,14 relationship UI,33 unified CLI cases; scoped web types; two desktop/phone headed cases with deliberate overlap/clipping controls and focus return pass22.0s; full smoke6pass2.0min before the final performance correction. These are owned scoped checks, not clean final-tree acceptance.

    Running remotely: CI40709921026, Comprehensive40709920716. Next: review exact-head2000-item/browser artifacts and independent review; fix concrete failures, then integrate/verify dev under AGENTS.md. Do not close this issue or #220/#193 based on partial evidence. Full routing/buses and10k/loading remain in their existing trackers.

  3. mvalancy commented on Oct 28, 2026

    @mvalancy
    MemberAuthor

    Portable checkpoint,2026-10-28: PR#223 source 5b16ce93020068ae251b1dc856cde5f6fc0537b0 is pushed on feat/clean-graph-symbols-20261028. One active visual slice; #221 is fully accepted/closed with its owned branch/worktree removed.

    Done:18px titles,14px working text/edge-label floor,14–16px controls, larger styled overview summaries, measured card/label geometry, bounded placement, exact paged relationships/focus, held-pan reconciliation, hidden overview work skipped. Latest correction samples long routes inside the viewport. Actual5d scale run loaded2000/5000 and passed overview, but failed zero labels; its3709ms browser/5011ms wall is retained, not acceptance. Timing now checks actually visible readable content, including a1200ms negative control.

    Local latest:24 scoped route/overview tests and web types passed; headed desktop+phone2 passed23.3s, one browser/worker, zero retries, strict cleanup. Small probes reuse owned dependencies. Exact CI40716064148 / Comprehensive40716064057 and independent5b review are pending. No merge or completion claim.

    Resume from any machine: fetch the branch, read AGENTS.md and .agents/inbox/2026-10-28-readable-symbols-need-reserved-geometry.md; inspect PR#223 review threads and the two exact runs. Download actual ci-large-symbols, item-wire/symbol, semantic/nested, phone and other applicable artifacts; retain failures and verify source/tree/fingerprint. Correct any failure in this branch, request independent review, then follow the dev-only integration playbook and wait for post-dev acceptance before closing this issue. Original user graphs remain untouched. Full item routing/buses stays #220, larger/hosted work stays #193.

  4. changed the title [-]Clean graph symbols: readable labels and compact adaptive item cards[/-] [+]Readable graph workspace: cards, labels, wires and visual controls[/+] on Oct 28, 2026
  5. mvalancy commented on Oct 28, 2026

    @mvalancy
    MemberAuthor

    Portable checkpoint: PR #223 source bcc0b91a3638a278f610c2785002a106b86d0eb9 is pushed cleanly on feat/clean-graph-symbols-20261028.

    The owner's current visual direction is included: readable 18px item/group titles, a 14px secondary-text floor, firmer body/control weights, three-pixel screen-stable wires, and 44px icon view controls with hover/focus labels. This retains the geometry, focus, held-pan and scale corrections.

    Latest local headed checks used one worker and zero retries: three symbol/navigation cases passed in 36.2s; desktop 1440px and phone 360px journeys through all eight views passed in 24.6s; the phone 390px hierarchy/trace case passed in 26.0s. Types passed. Independent a378 review found no additional blocker after the oriented-label correction and recorded minimap/card occlusion as a limitation. Review of bcc is requested.

    Current CI40723490908 and Comprehensive40723490955 are pending/running. The preceding a378 CI executed the 2,000-item/5,000-edge stage successfully, but its broader run was unfinished at the latest push. This is not full-run or artifact acceptance.

    To resume: fetch this branch, read PR #223 and its review threads plus the canonical readability lesson, then inspect exact-source CI and actual strict artifacts. Complete review and gates before dev integration; wait for post-dev acceptance before closing #222. Existing #220 owns the next relationship-priority control with per-pair fallback and remaining item routing. Its proposed policy/test matrix is published in schematic-connections.md. No additional overlapping Core implementation PR was opened.

  6. mvalancy commented on Oct 28, 2026

    @mvalancy
    MemberAuthor

    Published final source aaa2913fd9a113b0f35127953f2835d8eea9d740 on feat/clean-graph-symbols-20261028 / PR #223. Stronger body/control typography (500/600), 14px secondary text, screen-stable 3px wires, and icon navigation are in the headed preview. The final review correction preserves keyboard-focus labels after a different pointer hover; its regression passed in 14.4s.

    Exact final CI 40726146104 and Comprehensive 40726146346 run on GitHub-hosted workers; collect with gh run download <run-id> -R GraphDone/GraphDone-Core. The independent reviewer is checking this source, intended live-dev composition, and final artifacts. Earlier a378 and bcc actual 2,000-item/5,000-relationship stages passed, but their full runs were cancelled by source updates; neither is final acceptance.

    Next: inspect final strict reports, screenshots/video, cleanup and provenance; resolve review threads, then integrate into dev under AGENTS.md and the dev-admin playbook. Wait for actual post-dev CI/artifacts before closing #222. #220 remains open for relationship priority/fallback and actual obstacle routing/buses. Local validation stays serial and small; the large matrix stays in CI.

  7. mvalancy commented on Oct 28, 2026

    @mvalancy
    MemberAuthor

    Published b33febb8c80fe28ef2960d3b799b7c9a311b4c25 on the existing #223 branch. Final aaa CI40726146104 passed the actual 2,000/5,000 zoom case and runtime gates, but failed three new-user cases that targeted a hidden compact-card header gear; seven later stages were skipped. Independent trace review confirms both motion cases had already completed drag, saved coordinates and camera readiness, then stalled before the 17-second idle sample. The failure is retained in the PR audit and canonical lesson.

    The correction uses the visible card double-click, exact original item IDs, actual camera readiness, editor title and accessible type checks. API assertions, frame counts and the 17-second / 1px stability contract remain intact. The three phone journeys passed locally in 1.2 minutes, and a full-card desktop lifecycle passed in 11.8s, one headed worker and zero retries. Runtime source is unchanged.

    Exact CI 40731080444, Comprehensive 40731080454 and independent review are running. PR stays draft; merge requires final source/artifact review and all applicable checks, then post-dev acceptance before #222 closes. The headed preview is restored; large testing remains in CI.

  8. mvalancy commented on Oct 28, 2026

    @mvalancy
    MemberAuthor

    Checkpoint: source fe84973 on PR #223 fixes the actual control overlap from CI40731080444 and the separately reproduced exact-browser Edit dismissal. Status, trace and Connections share responsive flow in item/group modes; each reserves its measured obstacle. Existing normal-click durability checks remain strict. Six focused headed cases, the 390px hierarchy/trace journey,20 component tests and web types passed. Details and retained failures are in the committed lesson .agents/inbox/2026-10-28-graph-controls-need-shared-flow.md.

    Next: independent exact-source review and fresh CI/artifact acceptance, then authorized dev integration and post-merge checks before closure. The preceding b33 run passed new-user42 and the actual2k gate but failed durable5 and skipped4 downstream stages; do not treat it as acceptance. Source is frozen on feat/clean-graph-symbols-20261028. The separate relationship-priority UI is pushed on draft #224, stacked on this branch, so this issue can close independently when its gates pass.

  9. mvalancy commented on Oct 28, 2026

    @mvalancy
    MemberAuthor

    Preview correction, 2026-10-28: the long-running owned Vite process served stale Tailwind utilities (.text-xs 12px, .font-normal 400) even though its configuration file was byte-identical to the reviewed source (SHA256 ab33c1897cd34ea18ff04cd6ef644558b59254dcaeb6120225eef4951e8f3ff8). Restarting only that owned preview, without source edits, served .text-xs 14px, .font-normal 500 and .font-medium 600. A rendered overview sample then contained no visible sampled text below 14px/500. Earlier local explicit SVG geometry results remain scoped to their assertions; they do not prove every app utility used the new baseline. Independent acceptance uses the final CI build and actual artifacts. Canonical follow-up should document restarting previews after typography/build configuration changes and checking emitted CSS, not only source-file hashes.

  10. mvalancy commented on Oct 28, 2026

    @mvalancy
    MemberAuthor

    Accepted after native dev integration4a6d75d and successful post-dev workflows40749343162/40749343433. Independent actual artifact closeout: #223 (comment) . Broader wiring and LOD acceptance remain open in #220/#193.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions