Add MCP doc/repo retrieval to the Ask Freya assistant

context7.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "https://context7.com/schema/context7.json",
+  "projectTitle": "Frigg Framework",
+  "description": "Open-source, serverless-native framework for building direct/native integrations, maintained by Left Hook.",
+  "branch": "next",
+  "folders": ["docs"],
+  "excludeFolders": ["website", "node_modules", "**/dist", "**/__tests__"],
+  "rules": [
+    "Frigg is serverless-native (AWS Lambda) and cloud-agnostic; adopters own their stack.",
+    "Integrations extend IntegrationBase; API modules are installed with `frigg install <name>`.",
+    "The authoritative API-module catalog and roadmap live at /roadmap/ on friggframework.org."
+  ]
+}

website/friggframework-api/assistant.mjs

@@ -199,6 +199,13 @@ Rules:
   ANY question about specific ADRs, API modules, catalog counts, or what's built
   vs. planned, call the tool and answer from what it returns — do not guess or
   recite from memory. Everything else is grounded in the reference below.
+- You may also have live documentation/source tools whose names end in
+  "_list_tools" and "_call_tool" (e.g. frigg-docs for the Frigg docs, frigg-repo
+  for the repository on the next branch). When present, use them for deep,
+  technical, or how-does-the-code-work questions the reference doesn't cover:
+  call the "_list_tools" one to see what a source offers, then "_call_tool" to
+  fetch, and answer from the result rather than guessing. If they're absent, just
+  rely on the reference and point to the docs.
 - If something isn't covered by a tool or the reference, say so plainly and point
   to the docs (https://docs.friggframework.org), the GitHub repo, or /roadmap/
   rather than inventing specifics.