Skip to content

feat: initialize a branded diagram home and inventory - #84

Merged
jdylanmc merged 6 commits into
mainfrom
jdylanmc/init-landing
Sep 30, 2026
Merged

jdylanmc merged 6 commits into
mainfrom
jdylanmc/init-landing

Conversation

@jdylanmc

@jdylanmc jdylanmc commented Sep 30, 2026 •

Copy link
Copy Markdown
Owner

Outcome

topo init now creates a recognizable, usable Topocode application shell
immediately. topo serve works before a scan, including in an empty or
unborn Git repository. Home is a categorized diagram inventory, not an
automatically selected first diagram or Repository canvas.

This is the core product change requested after the separate Rust/Tauri
integration experiment in #83. It does not depend on that experiment or
promote its language support into production.

Behavior

  • Plain initialization and --skills initialization create Home, shared
    navigation, an honest empty state and packaged notices.
  • Initialization invokes neither the scanner nor a model or native diagram
    renderer. No empty authoritative graph is fabricated.
  • Home and the sidebar use the same catalogue entries, filtering,
    family/category/folder grouping and Git-backed sorting.
  • Topocode's identity stays visible independently of the configured project
    title, including collapsed navigation.
  • Story preview can populate the inventory before scanning. Existing story
    routes, native renderers, evidence, exports and return links remain.
  • Generated Repository exploration stays available at ?view=repository;
    existing scope/page/focus links retain their behavior.
  • Repeat initialization preserves authored configuration, skills, notes and
    an existing generated site.
  • A validated unscanned state supports static bundles without weakening
    scanned-source or story freshness checks.

Validation

  • Local complete regression: 391 tests passed, including all 56 browser tests.
  • Parent independently installed the candidate and exercised immediate empty
    Home, populated inventory, categories/search, native viewers, preservation,
    and a non-root static bundle in Chrome.
  • Empty and populated Home, categories/search, keyboard navigation, preserved
    context, Repository selection, and non-root static deployment exercised.
  • Independent whole-change review and the orphan-cache freshness correction
    are complete. The test-only setup optimization retained every preservation
    assertion without increasing timeouts or retries.
  • Exact-head hosted CI
    passed at 3adc114bf38584e29caa7d151159305e9b6a223f, including the production
    regression, native renderer package checks and installed-toolbelt proof.

Boundaries

No new frontend framework, dependency version, renderer pin, scanner behavior,
test deadline/concurrency relaxation, or npm publication. The public npm
0.1.0 package is unchanged; the new behavior is demonstrated through this
PR's built/installed candidate.

Related help, shipped skills, maintained product specification, workspace,
catalogue, preview, bundling and source-grounded architecture-story guidance
are updated together.

Create an explicitly unscanned shell before analysis and reuse the story
inventory on Home. Preserve existing generated sites and repository deep
links; keep repository exploration an explicit selection.

Public npm 0.1.0 is unchanged. This candidate requires independent review
and release-owner action before publication.
Limit the narrow-screen collapsed default to Home. Existing story pages
retain their expanded navigation and explicit collapse behavior.
Keep the existing origin-remote invariant explicit in first-story guidance.
Allow bundles without HEAD only when the cached Home matches an empty
initialization and no rendered stories remain. Reject stale previews
without changing their cache or the existing bundle.
Prepare one genuine preview and copy its Git/cache state per case.
Seed prior output without a second native render, and retain full
file-byte assertions through Node strict Buffer equality.

Keep production code, timeouts, retries, and concurrency unchanged.
@jdylanmc
jdylanmc marked this pull request as ready for review September 30, 2026 17:47
@jdylanmc
jdylanmc merged commit 4b8c085 into main Sep 30, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant