@jaypie/mcp 0.8.15 → 0.8.17

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -9,7 +9,7 @@ import { gt } from 'semver';
9
9
  /**
10
10
  * Docs Suite - Documentation services (skill, version, release_notes)
11
11
  */
12
- const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.15#cf726c0a"
12
+ const BUILD_VERSION_STRING = "@jaypie/mcp@0.8.17#7a43e42c"
13
13
  ;
14
14
  const __filename$1 = fileURLToPath(import.meta.url);
15
15
  const __dirname$1 = path.dirname(__filename$1);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jaypie/mcp",
3
- "version": "0.8.15",
3
+ "version": "0.8.17",
4
4
  "description": "Jaypie MCP",
5
5
  "repository": {
6
6
  "type": "git",
@@ -0,0 +1,11 @@
1
+ ---
2
+ version: 1.2.24
3
+ date: 2026-04-06
4
+ summary: Fix operate() logs missing handler/invoke context tags
5
+ ---
6
+
7
+ ## Changes
8
+
9
+ - Fix request-scoped context tags (handler, invoke) missing from operate/stream logs
10
+ - Call `getLogger()` at execution time instead of module initialization time
11
+ - Remove module-level `log` export from logger utility; only `getLogger()` remains
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  description: DynamoDB runtime package, key design, entity operations, and queries
3
- related: apikey, aws, cdk, models
3
+ related: apikey, aws, cdk, models, vocabulary
4
4
  ---
5
5
 
6
6
  # DynamoDB Patterns
@@ -220,7 +220,7 @@ All GSIs use `sequence` (Number) as the sort key for chronological ordering.
220
220
  | `indexScope` | `{scope}#{model}` | List entities by parent | You need hierarchical queries |
221
221
  | `indexAlias` | `{scope}#{model}#{alias}` | Human-friendly slug lookup | You need slug-based lookups |
222
222
  | `indexCategory` | `{scope}#{model}#{category}` | Category filtering | You need to filter by category |
223
- | `indexType` | `{scope}#{model}#{type}` | Type filtering | You need to filter by type |
223
+ | `indexType` | `{scope}#{model}#{type}` | Type filtering | You need to filter by type (note: vocabulary discourages `type` in favor of `category`; `indexType` is retained as a legacy GSI pattern) |
224
224
  | `indexXid` | `{scope}#{model}#{xid}` | External ID lookup | You need cross-system ID lookups |
225
225
 
226
226
  ### Query Functions
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  description: Definitions, naming conventions, ontology, and pedantry
3
- related: fabric, models, services
3
+ related: dynamodb, fabric, models, services
4
4
  ---
5
5
 
6
6
  # Vocabulary
@@ -49,7 +49,7 @@ Arguably composition, identity, instance, and relation would form a more complet
49
49
  - name: most common way to clearly reference the entity
50
50
  - related: array of id strings, complex "{model}#{id}" strings, or `{ id, model }` objects
51
51
  - scope: organizes entities, usually a reference to a parent entity
52
- - sequence: computed scalar, usually normalized createdAt or name
52
+ - sequence: computed scalar, usually `Date.now()` for chronological ordering
53
53
  - state: mutable data the entity tracks
54
54
  - status: canceled, complete, error, pending, processing, queued, sending
55
55
  - updatedAt: timestamp
@@ -66,7 +66,7 @@ Arguably composition, identity, instance, and relation would form a more complet
66
66
  - key => alias; make api or secret keys explicit in name
67
67
  - ou => scope
68
68
  - output => state
69
- - type => category, tags; reserved
69
+ - type => category, tags; reserved (exception: `indexType` GSI exists in DynamoDB as a legacy pattern; prefer `category` for new work)
70
70
 
71
71
  Avoid words defined elsewhere (services, terminology)
72
72