Skip to content

feat: ship Topocode npm CLI and agent skills - #81

Merged
jdylanmc merged 7 commits into
mainfrom
jdylanmc/issue-13-npm
Sep 28, 2026
Merged

jdylanmc merged 7 commits into
mainfrom
jdylanmc/issue-13-npm

Conversation

@jdylanmc

@jdylanmc jdylanmc commented Sep 28, 2026 •

Copy link
Copy Markdown
Owner

Purpose

Refs #13: deliver @jdylanmc/topo-code@0.1.0 as a practical CLI + portable agent skills toolbelt for unrelated repositories.

Changes

  • Produce an npm tarball with the topo executable, compiled private workspace packages, schemas, site assets, skills and notices. No source checkout, workspace symlinks, unpublished internal packages or absolute local dependency paths are required.
  • Replace the maintained Archify vendor copy with an exact @jdylanmc/topo-archify@0.1.0 dependency, retaining historical integrity evidence and product-specific adapter behavior.
  • Add opt-in topo init --skills, with identical-file preservation and explicit conflicts/symlink failures; preserve existing authored files and unrelated instructions.
  • Ship portable setup/operation/authoring skills and a context-loading Archify maintenance skill with actual upstream-update/regression commands and our integration lessons.
  • Add real installed-tarball consumer proof: initialization, source-grounded authoring, source movement/anchor repair, preview, local serving and a static base-path bundle.
  • Add GitHub Actions-only verification/publication, with normal OIDC and a tightly scoped explicit first-package bootstrap path.

Acceptance evidence

Criterion Current evidence
Renderer dependency and distribution Matching renderer candidate in jdylanmc/topo-archify; exact pristine upstream 3.0.0 runtime, all five native families exercised
Installable Topocode CLI + skills 169-file tarball; twelve concrete private packages bundled; installed bin/schema/resource targets checked
Fresh project use Retained unrelated consumer completes init, story validation, source-change repair, scan, preview, serve and bundle without the source checkout
Maintenance workflow Shipped skill loads full integration context, current pins, compatibility lessons, real regression commands and patch-escalation rules
Preservation Focused setup conflict/symlink/idempotence coverage; existing regression behavior retained
Publication @jdylanmc/topo-code@0.1.0 published through GitHub Actions; public SHA-512 matched the tested tarball and registry-only CLI installation passed

Verification and remaining gates

  • Implementation source regression passed: lint, typecheck, build, unit/integration/license gates and all 52 browser tests.
  • Current tarballs passed installed-consumer proof.
  • Workflow syntax/event guards were locally exercised with actionlint and bounded fixtures; this is not a hosted publication claim.
  • Parent-owned full regression and fresh installed-consumer proof passed. Independent whole-deliverable and scoped correction review found no remaining consequential issues.
  • Final exact-head 6c7b5c9 hosted CI passes. A separately reproduced owned-socket teardown stall is corrected with a shared test helper and focused regression; all 473 existing assertion calls and timeout/retry/concurrency policy remain unchanged. The original historical timeout's precise cause is not claimed.
  • All publication arguments use explicit local tarball paths, proven with actual credential-free npm dry-runs; independent scoped review retained the whole-deliverable coverage.
  • Published and verified: @jdylanmc/topo-code@0.1.0 is public. Release run 36492509209 fetched the exact published renderer, passed the full regression and installed-consumer journey, published the verified artifact, matched its public registry SHA-512, and exercised registry-only CLI installation.
  • Initial public metadata visibility lagged the successful upload. Only the read/install verification job was rerun; publication was not repeated.
  • Scoped Shepherd custody is held by the parent session. Human PR signoff and merge remain separate.

The user manages the temporary bootstrap secret through GitHub UI; no token value is in source, artifacts or this PR. After initial publication, the user configures trusted publishers and revokes the temporary token.

No automatic merge or issue closure. Product behavior remains local-first; upstream 3.0.1's new update checks are not silently adopted.

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