@ductape/mcp 0.1.61 → 0.2.1

package/CHANGELOG.md

@@ -0,0 +1,14 @@
+# Changelog
+
+## Unreleased
+
+- Broadened Feature guidance from durable/event-driven workflows to synchronous or asynchronous named product capabilities.
+- Added evidence-backed `FEATURE`, `FEATURE_STEP`, `DOMAIN_SERVICE`, `UTILITY`, and `INFRASTRUCTURE_ADAPTER` classification guidance.
+- Added synchronous multi-step examples and repository discovery/grouping rules.
+
+## 0.2.0 - 2026-07-26
+
+- Added exhaustive AI-led migration guidance for TypeScript, Go, Java, and .NET.
+- Added original E2E gates, contextual review, semantic database and frontend guidance, and strict verification matrices.
+- Added dependency-aware large-repository guidance.
+- Reinforced the administrative CLI/runtime execute boundary and access-key isolation.

package/README.md

@@ -1,5 +1,10 @@
 # Ductape MCP Server
 
+Migration guidance is available from `ductape_docs({ topic: "migration" })`. It starts with an original E2E
+baseline, defaults to a separate new codebase, requires contextual review and strict parity evidence, and ends
+against the unchanged original E2E suite. Administrative work and marketplace discovery use `ductape_cli`; `ductape_execute` remains
+publishable-key runtime-only. MCP never accepts or forwards `DUCTAPE_ACCESS_KEY`.
+
 MCP (Model Context Protocol) server that exposes **Ductape SDK** operations as tools. All calls go through the **Ductape backend proxy** at a fixed URL; the SDK never runs in the MCP process. It is completely stateless; you provide your **Publishable Key** per execution.
 
 ## Prerequisites
@@ -77,6 +82,19 @@ The server exposes **three tools**:
      - ready-to-copy SDK snippet in `typescript` or `python`
    - Intended for engineers and copilots that need executable examples quickly.
 
+The `ductape_cli` MCP tool also exposes public app discovery:
+`marketplace search <capability>`, `marketplace categories`, and
+`marketplace get <app_tag>`. Inspect the app before generating or executing an action payload.
+
+## Feature classification
+
+`ductape_docs({ topic: "features" })` treats a Feature as a named, reusable product capability
+with a stable input/output contract and a useful managed-execution boundary. Features may be
+synchronous and entirely local; Events, signals, schedules, waits, retries, and rollback are
+optional patterns. Repository analysis distinguishes `FEATURE`, `FEATURE_STEP`, `DOMAIN_SERVICE`,
+`UTILITY`, and `INFRASTRUCTURE_ADAPTER`, explains its evidence, and groups related low-level
+operations instead of turning every exported function into a Feature.
+
 ## Security
 
 - Passing the `publishable_key` on a per-request basis guarantees that each execution is isolated. This architecture safely supports deployments that multiplex multiple user connections in a single server thread (e.g., SSE), avoiding cross-tenant leakage.