fix: createTool drops version field, uses [skip version], publishable…

… via dispatch (#19)

* fix: createTool registry entry mirrors canonical generator; publish via dispatch

- buildWouldBeEntry no longer injects the removed per-tool `version` field
  and now mirrors scaffold/generator.py build_registry_entry exactly
  (homepage, topics, status, pagesType), so a born repo's catalog entry
  matches the canonical single source of truth.
- Registration commit uses the fleet opt-out `[skip version]` instead of
  `[skip ci]`, which previously suppressed all CI on the meta PR (so required
  checks never reported and the API merge blocked).
- publish.yml gains workflow_dispatch and an already-published idempotency
  guard so the package can be published/re-published without depending on a
  GITHUB_TOKEN release event (which does not trigger downstream workflows).
- Bump 0.2.0 -> 0.2.1.

Signed-off-by: fOuttaMyPaint <tmhospitalitystrategies@gmail.com>

* chore: retrigger CI [skip version]

Signed-off-by: fOuttaMyPaint <TMhospitalitystrategies@gmail.com>

---------

Signed-off-by: fOuttaMyPaint <tmhospitalitystrategies@gmail.com>
Signed-off-by: fOuttaMyPaint <TMhospitalitystrategies@gmail.com>

fix: createTool drops version field, uses [skip version], publishable…

… via dispatch (#19)

* fix: createTool registry entry mirrors canonical generator; publish via dispatch

- buildWouldBeEntry no longer injects the removed per-tool `version` field
  and now mirrors scaffold/generator.py build_registry_entry exactly
  (homepage, topics, status, pagesType), so a born repo's catalog entry
  matches the canonical single source of truth.
- Registration commit uses the fleet opt-out `[skip version]` instead of
  `[skip ci]`, which previously suppressed all CI on the meta PR (so required
  checks never reported and the API merge blocked).
- publish.yml gains workflow_dispatch and an already-published idempotency
  guard so the package can be published/re-published without depending on a
  GITHUB_TOKEN release event (which does not trigger downstream workflows).
- Bump 0.2.0 -> 0.2.1.

Signed-off-by: fOuttaMyPaint <tmhospitalitystrategies@gmail.com>

* chore: retrigger CI [skip version]

Signed-off-by: fOuttaMyPaint <TMhospitalitystrategies@gmail.com>

---------

Signed-off-by: fOuttaMyPaint <tmhospitalitystrategies@gmail.com>
Signed-off-by: fOuttaMyPaint <TMhospitalitystrategies@gmail.com>

fix: createTool drops version field, uses [skip version], publishable…

… via dispatch (#19)

* fix: createTool registry entry mirrors canonical generator; publish via dispatch

- buildWouldBeEntry no longer injects the removed per-tool `version` field
  and now mirrors scaffold/generator.py build_registry_entry exactly
  (homepage, topics, status, pagesType), so a born repo's catalog entry
  matches the canonical single source of truth.
- Registration commit uses the fleet opt-out `[skip version]` instead of
  `[skip ci]`, which previously suppressed all CI on the meta PR (so required
  checks never reported and the API merge blocked).
- publish.yml gains workflow_dispatch and an already-published idempotency
  guard so the package can be published/re-published without depending on a
  GITHUB_TOKEN release event (which does not trigger downstream workflows).
- Bump 0.2.0 -> 0.2.1.

Signed-off-by: fOuttaMyPaint <tmhospitalitystrategies@gmail.com>

* chore: retrigger CI [skip version]

Signed-off-by: fOuttaMyPaint <TMhospitalitystrategies@gmail.com>

---------

Signed-off-by: fOuttaMyPaint <tmhospitalitystrategies@gmail.com>
Signed-off-by: fOuttaMyPaint <TMhospitalitystrategies@gmail.com>

fix: simplify release workflow to tag from package.json; bump package…

….json to 0.2.0 (#16)

The previous release workflow created version-bump PRs using GITHUB_TOKEN.
GitHub blocks workflow triggers on GITHUB_TOKEN-created PRs, so the required
Ecosystem drift check never ran, keeping the PR permanently blocked.

New approach: developers bump package.json as part of their feature/fix PRs.
The release workflow reads the version, checks if the tag exists, and if not
tags + creates a GitHub Release. No PR creation, no polling, no race conditions.

Also bumps package.json to 0.2.0 so v0.2.0 is cut when this merges.

Signed-off-by: fOuttaMyPaint <TMhospitalitystrategies@gmail.com>

feat: implement read-core MCP tools (devtools_getRegistry, getFleetSt…

…atus, checkDrift, inspectRepo) (#6)

- Four read-only tools against the TMHSDigital developer-tools ecosystem
- GitHub REST API default mode with 5-minute in-memory TTL cache
- Optional local mode via DEVTOOLS_META_ROOT env var
- devtools_checkDrift fetches drift policy from meta-repo standards/drift-checker.config.json at runtime
- TypeScript, Node 20+, vitest; 17 tests passing
- CI on Node 20 and 22; publish workflow on npm release
- Write surface documented in ROADMAP.md v0.2.0 (not implemented)

Signed-off-by: fOuttaMyPaint <tmhospitalitystrategies@gmail.com>
Signed-off-by: fOuttaMyPaint <TMhospitalitystrategies@gmail.com>

feat: implement read-core MCP tools (devtools_getRegistry, getFleetSt…

…atus, checkDrift, inspectRepo) (#6)

- Four read-only tools against the TMHSDigital developer-tools ecosystem
- GitHub REST API default mode with 5-minute in-memory TTL cache
- Optional local mode via DEVTOOLS_META_ROOT env var
- devtools_checkDrift fetches drift policy from meta-repo standards/drift-checker.config.json at runtime
- TypeScript, Node 20+, vitest; 17 tests passing
- CI on Node 20 and 22; publish workflow on npm release
- Write surface documented in ROADMAP.md v0.2.0 (not implemented)

Signed-off-by: fOuttaMyPaint <tmhospitalitystrategies@gmail.com>
Signed-off-by: fOuttaMyPaint <TMhospitalitystrategies@gmail.com>