more improvements

Author: kentcdodds

.github/workflows/validate.yml

@@ -8,11 +8,11 @@ on:
   push:
     branches:
       - 'main'
-  pull_request:
-    branches:
-      - 'main'
+  pull_request: {}
+
 jobs:
   setup:
+    name: 🔧 Setup
     strategy:
       matrix:
         os: [ubuntu-latest, windows-latest, macos-latest]
@@ -35,6 +35,28 @@ jobs:
       - name: ⬣ ESLint
         run: echo "Linting not working in CI"
 
+  tests:
+    name: 🧪 Test
+    runs-on: ubuntu-latest
+    # Use continue-on-error to ensure this job doesn't fail the workflow
+    continue-on-error: true
+
+    steps:
+      - name: ⬇️ Checkout repo
+        uses: actions/checkout@v4
+
+      - name: ⎔ Setup node
+        uses: actions/setup-node@v4
+        with:
+          node-version: 24
+
+      - name: 📦 Install dependencies
+        run: npm ci
+
+      - name: 🧪 Run tests
+        id: run_tests
+        run: node ./epicshop/test.js ..s
+
   deploy:
     name: 🚀 Deploy
     runs-on: ubuntu-latest

epicshop/dev.js

@@ -0,0 +1,53 @@
+# fly.yaml app configuration file generated for epicweb-dev-advanced-mcp-features on 2025-07-11T10:06:25-06:00
+#
+# See https://fly.io/docs/reference/configuration/ for information about how to use this file.
+#
+
+app: 'epicweb-dev-mcp-fundamentals'
+primary_region: sjc
+kill_signal: SIGINT
+kill_timeout: 5s
+swap_size_mb: 512
+
+experimental:
+  auto_rollback: true
+
+  attached:
+    secrets: {}
+
+services:
+  - processes:
+      - app
+    protocol: tcp
+    internal_port: 8080
+
+    ports:
+      - port: 80
+
+        handlers:
+          - http
+        force_https: true
+      - port: 443
+
+        handlers:
+          - tls
+          - http
+
+    concurrency:
+      type: connections
+      hard_limit: 100
+      soft_limit: 80
+
+    tcp_checks:
+      - interval: 15s
+        timeout: 2s
+        grace_period: 1s
+
+    http_checks:
+      - interval: 10s
+        timeout: 2s
+        grace_period: 5s
+        method: get
+        path: /resources/healthcheck
+        protocol: http
+        tls_skip_verify: false

epicshop/fly.toml

@@ -4,16 +4,17 @@
 them even more useful! In this step, you'll learn how to link a resource
 directly in your tool responses.
 
-Why does this matter? Sometimes, a tool's output isn't just plain text—it might
-be a file, a database record, or some other structured data. By linking to
-resource references, you enable clients (and LLMs) to follow links to additional
-context, download files, subscribe to updates, or fetch related data on demand.
+Why does this matter? Sometimes, an embedded resource is more content than is
+necessary for a tool's output. It could be a whole video potentially. By linking
+to resource references, you enable clients (and LLMs) to decide whether they
+want to follow links to additional context, download files, subscribe to updates,
+or fetch related data on demand.
 
 Your goal in this step:
 
-- Update your tools so that, when they create a tag, we tell them it was created
-  and also include a reference to the tag (using the `type: 'resource_link'`
-  content type in the response).
+- Update the `list_entries` and `list_tags` tools so when they create a tag or
+  entry, we tell them it was created and also include a reference to the tag or
+  entry (using the `type: 'resource_link'` content type in the response).
 - Make sure the resource includes the correct URI and metadata, so clients can
   easily fetch the resource if they want more details.
 
@@ -33,7 +34,7 @@ resource:
 }
 ```
 
-To test this out, create a new tag and notice the resource is included in the
-response.
+To test this out, check the response from `list_entries` and `list_tags` and
+notice the resource is included in the response.
 
 - 📜 [MCP Spec: Tools (Resource Links)](https://modelcontextprotocol.io/specification/2025-06-18/server/tools#resource-links)