Skip to content

Publish the Topocode CLI and portable agent skills on npm #13

Closed

Description

@jdylanmc

This was generated by AI during triage.

Current status (2026-09-29)

Inspected baseline: main@b64bb2f.

Status: completed and published on 2026-09-28.

  • Owned public identities: @jdylanmc/topo-code@0.1.0 and @jdylanmc/topo-archify@0.1.0.

  • Topocode ships its CLI, compiled private implementation modules, schemas/assets/notices, portable operation and story-authoring skills, and context-loading Archify maintenance guidance. topo init --skills installs project context without replacing existing differing files.

  • The renderer is a normal exact dependency containing all 104 pristine upstream Archify 3.0.0 runtime files. Consumers need no source checkout, workspace dependency resolution, install hook, or runtime fetch beyond ordinary npm package installation.

  • Packaging boundaries, compatibility/update escalation, and GitHub-Actions-only release procedures are documented in the release guide and maintenance skill.

  • Both packages were published and their public registry integrity verified. Topocode's registry-only CLI installation succeeded.

Delivery evidence

Consumer entry point

With Node.js 22+ and Git, in a supported TypeScript/JavaScript repository:

npm install --save-dev @jdylanmc/topo-code@0.1.0
npm exec --no -- topo init . --skills
npm exec --no -- topo scan .
npm exec --no -- topo serve .

The renderer is installed automatically. Public npm publication does not guarantee that a private registry mirror has synchronized the versions.

Separate follow-ups

Trusted-publisher configuration and temporary-token/secret cleanup are tracked in #82; they do not make this release unshipped or block consumption. Stale candidate/pre-publication wording is tracked under #75. Cross-machine comparisons (#42), a manual authoring walkthrough (#46), and renderer-assurance obligations (#41) remain distinct; package automation does not prove them complete.

Previous issue text and original requirements (historical; current disposition is above)

Reconciled status (2026-09-27)

Inspected baseline: main@c8e22ec. Maintained intent: docs/product-spec.md.

Disposition: remains open for the scope below.

Local source-checkout distribution is implemented: private Yarn workspaces, Node.js 22+, compiled site assets, static bundles, and shipped notices. Public npm distribution is still unshipped. Local @topo/* names do not establish public scope ownership.

Remaining scope

  • Confirm an owned public package/scope identity and the credentials/access needed for an eventual release.
  • Choose install/npx delivery, public package boundaries and compiled-asset packaging.
  • Agree release/versioning policy, including schema-affecting changes.

Readiness and dependencies

Keep the existing public-release decision/blocked status. Do not treat historical registry transport failures or Ajv installation as current blockers; no new registry/ownership test was performed in this cleanup. This does not block local use, #74 marketing, or #75 documentation of supported source-checkout installation.

Merged delivery evidence: #16, #53, #78. These merge commits are ancestors of the inspected main revision.

Current source and regression evidence:

Existing exact-main CI is successful. This reconciliation inspected current code, committed regression coverage and merged history; it does not claim a new test run, manual walkthrough, visual acceptance, cross-machine experiment, or approval of paused work.

Historical issue scope (preserved; current disposition and readiness are above)

Current status (2026-09-19)

Public npm publication remains deferred pending an owned package identity and release/distribution decisions. The private Yarn workspace, Node 22 floor, compiled site assets, and shipped notices already exist. The old Ajv-installation and permanent registry-outage framing is obsolete; #40 records the registry correction. This is not a blocker for local #40 delivery. The blocked label applies to public publication only.

Evidence: docs/licenses.md; README.md; #40 CON-02.

Original issue text is preserved below. This update records current delivery status without erasing historical decisions. #40 governs the next architecture-story MVP; it does not imply that the broader historical roadmap is implemented.


Governed by the PRD (#1). This issue tracks one open decision.

The question

How is TOPO packaged and shipped?

Already settled

  • TypeScript and Node.
  • One yarn workspace, @topo/* packages.
  • Local-first: no hosted service, no telemetry, no account.
  • The site is compiled once; data regenerates via a command-line command.

Blocked

The @topo npm namespace availability cannot currently be checked. The public npm registry is unreachable from this machine — ENOTCONN — because the local npm client is pinned to an internal Microsoft Azure DevOps feed. This also blocks installing any package that is not mirrored on that feed (ajv, for example).

This needs to be resolved from a machine with public registry access, or by reconfiguring the registry for this workspace, before the package namespace is committed to.

Still open

  • Is @topo available? If not, what is the scope name?
  • Package split: core, schema, scanners, renderer, modules, command-line interface.
  • Distribution: npm install, npx one-shot, or both.
  • How the compiled site is shipped — as a package asset, downloaded, or built on install.
  • Node version floor.
  • Release and versioning strategy, especially for schema-affecting changes (Decision: canonical graph schema #2).

Done when

The namespace question is answered with evidence, and a package layout is agreed.

Activity

  1. added
    decisionAn open design decision that must be resolved
    blockedCannot proceed until an external blocker clears
    on Aug 26, 2026
  2. jdylanmc commented on Sep 13, 2026

    @jdylanmc
    OwnerAuthor

    Distribution gate rechecked during the autonomous backlog pass after #25. The private Yarn workspace, Node.js 22 floor, compiled site assets, and shipped-license gates are implemented. Ajv and the required runtime dependencies are installed and validated through the configured mirror, so graph validation is no longer blocked on installing Ajv.

    Public scope ownership is still unverified. On 2026-09-13 an anonymous direct request to registry.npmjs.org/@topo%2Fschema failed with a connection/transport error (HTTP 000); an independent fetch also failed at transport. No registry settings, credentials, namespace reservations, or publications were changed. Even a package-level 404 would not prove namespace ownership.

    Remaining human/access gate: confirm an npm scope/account you control and public registry access before selecting a public identity or publishing. Local @topo/* names remain internal conventions, not an ownership claim. Keeping this issue open.

  3. changed the title [-]Decision: packaging and distribution[/-] [+]Decision: public npm identity, packaging, and release strategy[/+] on Sep 27, 2026
  4. jdylanmc commented on Sep 27, 2026

    @jdylanmc
    OwnerAuthor

    Backlog reconciliation (2026-09-27)

    Inspected baseline: main@c8e22ec. Maintained intent: docs/product-spec.md.

    Disposition: remains open for the scope below.

    Local source-checkout distribution is implemented: private Yarn workspaces, Node.js 22+, compiled site assets, static bundles, and shipped notices. Public npm distribution is still unshipped. Local @topo/* names do not establish public scope ownership.

    Remaining scope

    • Confirm an owned public package/scope identity and the credentials/access needed for an eventual release.
    • Choose install/npx delivery, public package boundaries and compiled-asset packaging.
    • Agree release/versioning policy, including schema-affecting changes.

    Readiness and dependencies

    Keep the existing public-release decision/blocked status. Do not treat historical registry transport failures or Ajv installation as current blockers; no new registry/ownership test was performed in this cleanup. This does not block local use, #74 marketing, or #75 documentation of supported source-checkout installation.

    Merged delivery evidence: #16, #53, #78. These merge commits are ancestors of the inspected main revision.

    Current source and regression evidence:

    Existing exact-main CI is successful. This reconciliation inspected current code, committed regression coverage and merged history; it does not claim a new test run, manual walkthrough, visual acceptance, cross-machine experiment, or approval of paused work.

  5. changed the title [-]Decision: public npm identity, packaging, and release strategy[/-] [+]Publish the Topocode CLI and portable agent skills on npm[/+] on Sep 29, 2026
  6. added
    enhancementNew feature or request
    decidedDecision made and recorded with evidence
    and removed
    decisionAn open design decision that must be resolved
    blockedCannot proceed until an external blocker clears
    on Sep 29, 2026
  7. jdylanmc commented on Sep 29, 2026

    @jdylanmc
    OwnerAuthor

    This was generated by AI during triage.

    Backlog reconciliation (2026-09-29)

    Closing as completed: both 0.1.0 packages are public, both delivery PRs are merged, and GitHub Actions verified public registry bytes plus Topocode's registry-only installation. Removed obsolete blocked/decision labels. Remaining human-owned publishing administration is tracked separately in #82; historical registry failures are not current publication blockers.

    Evidence and preserved historical requirements are in the updated issue body. Baseline: main@b64bb2f. No repository source or credential changes.

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

    decidedDecision made and recorded with evidenceenhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions