mirror of
https://github.com/rohitg00/ai-engineering-from-scratch.git
synced 2026-10-02 01:54:39 +08:00
Rohit Ghumare
ed6d0c0196
* feat(phase-13/22): teach portable agent skill contracts Agent skills need a portable contract before host-specific metadata and runtime policy can be reasoned about. * fix(phase-13/23): make the ecosystem capstone accurate The capstone should model current A2A operations, portable artifact metadata, and deterministic trace timing. * feat(phase-13/24): teach skill discovery and disclosure A useful skill catalog needs explicit scope precedence and bounded progressive disclosure before instructions are loaded. * feat(phase-13/25): teach invocation policy and routing Human, model, application, and skill activation need separate policy decisions before relevance ranking can be trusted. * feat(phase-13/26): teach skill sandbox and trust boundaries Skill instructions are untrusted input, so authority must remain host-owned and every filesystem, network, and command boundary must fail closed. * feat(phase-13/27): add the skill release gate A distributable skill needs adversarial structure, routing, safety, artifact, provenance, installation, and portability evidence before release. * feat(skills): install and render complete skill bundles Progressive-disclosure skills must keep companion references, scripts, assets, and evals intact across discovery, installation, and lesson rendering. * docs(curriculum): index the agent skills mini-course The expanded Phase 13 sequence needs consistent lesson links, durations, translations, and shared terminology across every learner entry point. * feat(certification/11): teach stateless MCP integration Certification learners need the same stateless wire model as the production curriculum. * feat(phase-11/14): modernize MCP protocol contracts The foundational MCP lesson must no longer teach the removed session lifecycle. * fix(phase-13/01): align tool terms with stateless MCP The tool interface introduction should point to the current protocol vocabulary. * feat(phase-13/06): teach stateless MCP fundamentals Learners need the current per-request contract before building clients or servers. * feat(phase-13/07): build a stateless MCP server The server lab should model the protocol that new implementations actually ship. * feat(phase-13/08): build a stateless MCP client The client lab must negotiate every request without relying on session state. * feat(phase-13/09): teach current Streamable HTTP Transport examples need the current POST-only lifecycle and notification behavior. * feat(phase-13/10): teach stateless resources and prompts Resource and prompt discovery must reflect stateless cache and result contracts. * feat(phase-13/11): teach per-request sampling Sampling calls must carry current capabilities and stateless response semantics. * feat(phase-13/12): teach roots and elicitation retries Elicitation retries and roots handling need current capability and MRTR boundaries. * feat(phase-13/13): teach stateless MCP tasks Task storage and subscriptions must survive cross-instance stateless requests. * feat(phase-13/14): update MCP Apps contracts Apps learners need current bridge, subscription, and discovery boundaries. * feat(phase-13/15): update MCP threat boundaries Threat modeling must cover current routing and MRTR state boundaries. * feat(phase-13/16): update MCP OAuth contracts OAuth examples must bind issuers and resources while using current errors. * feat(phase-13/17): update gateway and registry contracts Registry admission must separate publication identity from runtime discovery. * feat(phase-13/18): teach production MCP authentication Production auth should implement real PKCE, CIMD, and resource-bound caching. * docs(phase-13/22): add a runnable skill quickstart Beginners need an exact repository-root path from bundle inspection to host use. * fix(phase-13/23): make the capstone stateless The ecosystem capstone must compose the same current contracts taught upstream. * docs(phase-13/24): clarify host discovery limits Learners should distinguish known context budgets from host fallback behavior. * docs(phase-13/26): clarify sandbox prerequisites The safety lab needs explicit prerequisites and a viable conceptual fallback. * docs(phase-13/27): add real-host release evidence A production claim should require installed-host evidence beyond deterministic fixtures. * docs(phase-16/02): update MCP legacy comparison The interoperability comparison should use the current stateless MCP lifecycle. * feat(phase-19/13): modernize the MCP registry capstone The production capstone must separate Registry publication from stateless runtime discovery. * docs(curriculum): index agent skills and stateless MCP Learners need one coherent route through the skills track and current MCP sequence. * feat(skills): add a focused agent skills learner path A dedicated route removes placement and navigation friction for focused learners. * feat(mcp): add production engineering track * fix(cert-11): harden MCP integration contract * fix(phase-11-14): classify MCP handler failures * fix(mcp-07): validate JSON-RPC request identifiers * fix(mcp-08): reuse strict response decoding * fix(mcp-09): harden HTTP transport boundaries * fix(mcp-11): isolate returned tool descriptors * fix(mcp-12): make continuation state single-use * fix(mcp-14): align lesson response metadata * fix(mcp-15): expire and consume continuation state * fix(mcp-16): bind OAuth enrollment and code exchange * fix(mcp-18): enforce redirect and code lifetimes * fix(mcp-23): validate task identifiers * fix(skills-24): clarify discovery boundaries * fix(skills-25): deny unknown invocation actors * fix(skills-26): validate approval policy shape * fix(mcp-28): terminate unsafe cursor pagination * fix(mcp-29): preserve completed request state * fix(mcp-30): require secure remote endpoints * fix(mcp-31): strengthen conformance checks * fix(agent-skills): align route prerequisites * fix(scripts): harden skill bundle installation * fix(site): validate learning and artifact boundaries * fix(course): address review edge cases * fix(mcp): tighten notification and redirect validation * fix(mcp): secure reproducible lesson state * fix(mcp): use required lesson header comments
79 lines
3.4 KiB
JSON
79 lines
3.4 KiB
JSON
{
|
|
"lesson": "10-mcp-resources-and-prompts",
|
|
"title": "MCP Resources and Prompts",
|
|
"questions": [
|
|
{
|
|
"stage": "pre",
|
|
"question": "A host needs to retrieve a stable architecture note by URI. Which MCP primitive fits best?",
|
|
"options": [
|
|
"A resource",
|
|
"A cancellation notification",
|
|
"A protocol session",
|
|
"A destructive tool"
|
|
],
|
|
"correct": 0,
|
|
"explanation": "A resource exposes addressable content through a URI. A tool performs an operation, while sessions and cancellation do not model readable content."
|
|
},
|
|
{
|
|
"stage": "check",
|
|
"question": "What should a 2026-07-28 server return when resources/read receives an unknown resource URI?",
|
|
"options": [
|
|
"A resources/list_changed notification",
|
|
"JSON-RPC error -32601",
|
|
"An empty successful contents array",
|
|
"JSON-RPC error -32602"
|
|
],
|
|
"correct": 3,
|
|
"explanation": "The current Resources contract uses invalid parameters, code -32602, for an invalid or unknown resource URI. Empty success would hide a caller error."
|
|
},
|
|
{
|
|
"stage": "check",
|
|
"question": "Which cache policy is safest for a user-owned note returned by resources/read?",
|
|
"options": [
|
|
"Public because the URI is stable",
|
|
"Shared across users when the MIME type matches",
|
|
"Private with a bounded TTL",
|
|
"Public with an unlimited TTL"
|
|
],
|
|
"correct": 2,
|
|
"explanation": "A user-owned result should not cross identity boundaries. A bounded private cache can reduce repeated reads while preserving the authorization context."
|
|
},
|
|
{
|
|
"stage": "check",
|
|
"question": "What identifies every notification on a subscriptions/listen response stream?",
|
|
"options": [
|
|
"The original listen request ID in subscription metadata",
|
|
"The resource MIME type",
|
|
"A newly generated protocol session",
|
|
"The server process ID"
|
|
],
|
|
"correct": 0,
|
|
"explanation": "The JSON-RPC ID of subscriptions/listen becomes io.modelcontextprotocol/subscriptionId and is repeated in the acknowledgment and every later event."
|
|
},
|
|
{
|
|
"stage": "post",
|
|
"question": "Why must resources/list and prompts/list be deterministic for the same request inputs?",
|
|
"options": [
|
|
"To grant public access to all returned entries",
|
|
"To avoid validating pagination cursors",
|
|
"To stabilize caches, snapshots, and host interfaces",
|
|
"To make list membership depend on a prior read"
|
|
],
|
|
"correct": 2,
|
|
"explanation": "Stable membership and ordering prevent noisy cache misses and changing interfaces. Authorization can still affect visibility because credentials are explicit request input."
|
|
},
|
|
{
|
|
"stage": "post",
|
|
"question": "What must a current MCP server expose even when clients may call resources/list directly?",
|
|
"options": [
|
|
"A resources/subscribe method for every URI",
|
|
"An initialize method that creates a protocol session",
|
|
"A standalone HTTP GET event stream",
|
|
"server/discover with supported revisions and capabilities"
|
|
],
|
|
"correct": 3,
|
|
"explanation": "Servers must implement server/discover so clients can obtain one capability and version snapshot. Calling it remains optional for a client, which may call another method and handle a structured version error."
|
|
}
|
|
]
|
|
}
|