Skip to content

fix: root package.json for Glama tool detection#12

Merged
hyperpolymath merged 1 commit into
mainfrom
fix/glama-root-entrypoint
Mar 13, 2026
Merged

fix: root package.json for Glama tool detection#12
hyperpolymath merged 1 commit into
mainfrom
fix/glama-root-entrypoint

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

  • Add root-level package.json pointing to mcp-bridge/main.js
  • Enables Glama and npx to discover the MCP entry point at repo root

Context

Glama's inspector likely looks for package.json at the repo root, not in subdirectories. The mcp-bridge/package.json wasn't being found.

🤖 Generated with Claude Code

Move package.json to repo root (pointing to mcp-bridge/main.js) so
Glama and npx can discover the MCP entry point without navigating
into subdirectories.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@hyperpolymath hyperpolymath merged commit 9cded89 into main Mar 13, 2026
12 of 14 checks passed
@hyperpolymath hyperpolymath deleted the fix/glama-root-entrypoint branch March 13, 2026 20:38
hyperpolymath added a commit that referenced this pull request Apr 19, 2026
Parallel session closed with commit 473733b on main. Updates the
mirrored handover README to match:

- 16 tasks shipped (full list: #1, #3-#8, #13-#17, #32, #35, #36, #37)
- 27 Zig + 41 Deno E2E assertions green, panic-attack clean
- 007-mcp family (#9-#12) complete in separate repo The-Metadatastician/007
- Next pick-up: Task #33 (client_kind+variant) + #34 (capability advertisement)
- Proof Track: P-04..P-07 in Durability.idr, keystone P-06
- Shared-state warning on local_coord_ffi.zig + local_coord_adapter.zig

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
hyperpolymath added a commit that referenced this pull request Jun 8, 2026
…ards#91 / #100)

Refreshes docs/integration/hcg-tier2-rollout-runbook.md from v0.1
(draft, 2026-05-20, pre Phase-D) to v0.2 reflecting the current
state of the single-lane channel rooted at standards#91:

- §1.1 Phase D deliverables: tick D-1..D-3 + D-4 bootstrap with
  http-capability-gateway PR refs (#12 / #14 / #22 / #26 / #30) and
  the boj-server D-1 load-profile (#168) that joint-closed standards#99
  on 2026-06-01. The one remaining open item is the owner-driven
  perf-rebaseline workflow dispatch + `_status: scaffold-placeholder
  -> active` flip; called out explicitly rather than left as a stale
  unchecked checkbox.

- §1.4 BoJ-side prereqs: tick the three loopback-bind layers
  (#130 / #131 / #132), the Phase C TrustPolicy clause (#106), the
  NetworkPolicy (#173), and the SSE-route policy coverage (#165).
  The Trustfile `tier_2_gateway.status: PENDING` line stays
  intentionally unchecked - it's the §6.4 last-action target.

- §1.5 Gateway-side prereqs: tick the new
  `container/gateway-deploy.k9.ncl` from http-capability-gateway#38
  (2026-06-03), record what stays PLACEHOLDER until cerro-torre
  signing runs, and expand the smoke-test entry with the concrete
  allow/deny sequence boj-server#165 deferred.

- Header banner: replace the stale "Phase D has merged the scaffold
  only" Phase-D-dependency note with a current-state summary,
  bump version 0.1 -> 0.2, date 2026-05-20 -> 2026-06-08.

- CHANGELOG.md: Documentation entry under [Unreleased] summarising
  the refresh.

No code, infrastructure, or runtime behaviour changes. The runbook
is the operator-facing source of truth for what's gating the next
Phase E owner action; the drift it had was making "what's still
open" harder to read at a glance.

Refs hyperpolymath/standards#91
Refs hyperpolymath/standards#100

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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