chore(examples): archive slice — 4 archives + 1 merge (maintainer-approved)

Slice 1 of the examples disposition, per
docs/plans/2026-07-28-examples-review.md (now stamped EXECUTED):

Archived to examples/archived/ with dated banners (reason + superseded-by):
- manual-tools-server — manual trait implementation is owned by
  calculator-add-manual-server (the CLAUDE.md-designated reference); its
  session-persistence teaching is false on the 2026 stateless lane.
- dynamic-resource-server — name/README promised dynamic-resource teaching
  the code never contained (zero resources registered); URI-template
  resources are owned by function-resource-server.
- alert-system-server — both teachable ideas owned elsewhere
  (stateful-server, derive-macro-server); the remainder suggested
  transport sessions exist on the 2026 lane.
- simple-logging-server — per-session log storage is the removed 2025
  session model; never exercised the MCP logging capability.

Merged: session-aware-logging-demo archived as a superseded strict subset
of session-logging-proof-test (which adds 3-session isolation, the full
level cascade, and PASS/FAIL verification).

Same-commit reference cleanup:
- workspace members + default-members (cargo metadata verified)
- EXAMPLES.md: 5 rows removed, active count 55 → 50
- root README: business list renumbered; Basic Patterns →
  calculator-add-manual-server; Business Value row removed
- examples/minimal-server/README.md: Next Steps link repointed (+ the two
  already-dead links removed)
- scripts/verify_phase{2,5,8}.sh entries removed (legacy dev scripts —
  the actual CI gates never referenced any of the five)
- tests/working_examples_validation.rs compilation list

Gates: scripts/ci-gates.sh all → ALL GATES PASSED.

Author: hortovanyi

Cargo.toml

@@ -21,22 +21,19 @@ members = [
   # Test crates
 
   # Active examples (33 total)
-  "examples/alert-system-server",
   "examples/audit-trail-server",
   "examples/calculator-add-builder-server",
   "examples/calculator-add-function-server",
   "examples/calculator-add-manual-server",
   "examples/calculator-add-simple-server-derive",
   "examples/completion-server",
   "examples/derive-macro-server",
-  "examples/dynamic-resource-server",
   "examples/dynamic-tools-server",
   "examples/elicitation-server",
   "examples/function-macro-server",
   "examples/function-resource-server",
   "examples/lambda-mcp-client",
   "examples/lambda-mcp-server",
-  "examples/manual-tools-server",
   "examples/minimal-server",
   "examples/notification-server",
   "examples/pagination-server",
@@ -49,7 +46,6 @@ members = [
   "examples/roots-server",
   "examples/sampling-server",
   "examples/simple-dynamodb-session",             # Simplified and ready - utility binaries commented out
-  "examples/simple-logging-server",
   "examples/simple-postgres-session",             # Fixed API mismatches - ready to use
   "examples/simple-sqlite-session",               # Fixed API mismatches - ready to use
   "examples/stateful-server",
@@ -70,7 +66,6 @@ members = [
   "examples/client-initialise-report",
   "examples/logging-test-client",
   "examples/logging-test-server",
-  "examples/session-aware-logging-demo",
   "examples/session-logging-proof-test",
   "examples/session-management-compliance-test",
   "examples/streamable-http-client",
@@ -120,20 +115,17 @@ default-members = [
   # examples use 2025-only features (tasks/sampling/elicitation/logging builders,
   # the runtime ToolBuilder, pagination envelopes) or the bilingual client and are
   # held out until ported or pinned to the 2025 opt-in.
-  "examples/alert-system-server",
   "examples/audit-trail-server",
   "examples/calculator-add-builder-server",
   "examples/calculator-add-function-server",
   "examples/calculator-add-manual-server",
   "examples/calculator-add-simple-server-derive",
   "examples/completion-server",
   "examples/derive-macro-server",
-  "examples/dynamic-resource-server",
   "examples/function-macro-server",
   "examples/function-resource-server",
   "examples/icon-showcase",
   "examples/lambda-authorizer",
-  "examples/manual-tools-server",
   "examples/middleware-auth-lambda",
   "examples/middleware-auth-server",
   "examples/middleware-logging-server",
@@ -146,7 +138,6 @@ default-members = [
   "examples/resource-server",
   "examples/resources-server",
   "examples/simple-dynamodb-session",
-  "examples/simple-logging-server",
   "examples/simple-postgres-session",
   "examples/simple-sqlite-session",
   "examples/tool-output-introspection",

EXAMPLES.md

@@ -1,6 +1,6 @@
 # MCP Framework Examples
 
-This document provides a comprehensive overview of all **55 active examples** in the MCP Framework (plus `examples/archived/`), organized by learning progression from basic concepts to advanced implementations.
+This document provides a comprehensive overview of all **50 active examples** in the MCP Framework (plus `examples/archived/` — grown by 5 in the 2026-06-12 archive slice, see `docs/plans/2026-07-28-examples-review.md`), organized by learning progression from basic concepts to advanced implementations.
 
 **✅ All active examples compile under their lane's CI gates** (2026-07-28 default lane
 + per-manifest 2025-11-25 pins). Per-example functional re-verification against the
@@ -69,7 +69,6 @@ cargo run --example minimal-server
 | **resources-server** | 8041 | ✅ VALIDATED | Multiple resource types | Resource handling patterns |
 | **resource-test-server** | 8043 | ✅ VALIDATED | Resource testing | Resource validation framework |
 | **function-resource-server** | 8008 | ✅ VALIDATED | Function-based resources | Resource function patterns |
-| **dynamic-resource-server** | 8048 | ✅ VALIDATED | Runtime resources | Dynamic resource creation |
 | **session-aware-resource-server** | 8008 | ✅ VALIDATED | Session-aware resources (2025-11-25 pinned) | Session context integration on the stateful lane |
 
 ## 🟢 **FEATURE-SPECIFIC SERVERS** (8 examples) - Specialized MCP Features
@@ -90,9 +89,7 @@ cargo run --example minimal-server
 | Example | Port | Status | Description | Advanced Features |
 |---------|------|--------|-------------|-------------------|
 | **comprehensive-server** | 8002 | ✅ VALIDATED | All MCP features in one server | Complete framework showcase |
-| **alert-system-server** | 8010 | ✅ VALIDATED | Alert management | Enterprise alert management system |
 | **audit-trail-server** | 8009 | ✅ VALIDATED | Audit logging | Comprehensive audit logging system |
-| **simple-logging-server** | 8008 | ✅ VALIDATED | Simplified logging | Simplified logging patterns |
 | **zero-config-getting-started** | 8641 | ✅ VALIDATED | Zero-configuration setup | Getting started tutorial server |
 
 ## 🔴 **SESSION & STATE** (4 examples) - Advanced State Handling
@@ -101,7 +98,6 @@ cargo run --example minimal-server
 |---------|------|--------|-------------|------------------|
 | **stateful-server** | 8006 | ✅ VALIDATED | Advanced stateful operations (2025-11-25 pinned) | Session state management on the stateful lane |
 | **session-logging-proof-test** | 8001 | ✅ VALIDATED | Session logging validation | Session-based logging verification |
-| **session-aware-logging-demo** | 8000 | ✅ VALIDATED | Session-scoped logging | Session-aware logging patterns |
 | **logging-test-server** | 8052 | ✅ VALIDATED | Logging test suite | Comprehensive logging test suite |
 
 ## 🟠 **CLIENT EXAMPLES** (5 examples) - Client Implementation
@@ -139,7 +135,6 @@ cargo run --example client-initialise-report -- --url http://127.0.0.1:8641/mcp
 |---------|------|--------|-------------|--------------|
 | **derive-macro-server** | 8765 | ✅ VALIDATED | Derive macro tools | `#[derive(McpTool)]` with code generation tools |
 | **function-macro-server** | 8003 | ✅ VALIDATED | Function macro tools | `#[mcp_tool]` attribute macro patterns |
-| **manual-tools-server** | 8007 | ✅ VALIDATED | Manual tool impl | Session state, progress notifications, complex schemas |
 | **tools-test-server** | random | ✅ VALIDATED | Comprehensive tool testing | All MCP tool patterns and edge cases |
 | **tool-output-introspection** | 8641 | ✅ VALIDATED | Output schema via introspection | Automatic field-level output schema generation |
 | **tool-output-schemas** | 8641 | ✅ VALIDATED | Output schema via schemars | `schemars::JsonSchema` derive for JSON Schema output |

README.md

@@ -581,19 +581,18 @@ let server = McpServer::builder()
 ### 🏢 Real-World Business Applications
 Development servers for actual business problems:
 
-1. **dynamic-resource-server** → Enterprise API Data Gateway
-2. **audit-trail-server** → Application Audit & Compliance System (SQLite-backed)
-3. **elicitation-server** → Customer Onboarding Platform
-4. **notification-server** → Development Team Alert System
-5. **completion-server** → IDE Auto-Completion Server
-6. **prompts-server** → AI-Assisted Development Prompts
-7. **derive-macro-server** → Code Generation & Template Engine
-8. **calculator-add-\*-server** → Calculator examples (builder, function, derive, manual patterns)
-9. **resources-server** → Development Team Resource Hub
+1. **audit-trail-server** → Application Audit & Compliance System (SQLite-backed)
+2. **elicitation-server** → Customer Onboarding Platform
+3. **notification-server** → Development Team Alert System
+4. **completion-server** → IDE Auto-Completion Server
+5. **prompts-server** → AI-Assisted Development Prompts
+6. **derive-macro-server** → Code Generation & Template Engine
+7. **calculator-add-\*-server** → Calculator examples (builder, function, derive, manual patterns)
+8. **resources-server** → Development Team Resource Hub
 
 ### 🔧 Framework Demonstrations
 Educational examples showcasing framework patterns:
-- **Basic Patterns**: minimal-server, manual-tools-server, zero-config-getting-started
+- **Basic Patterns**: minimal-server, calculator-add-manual-server, zero-config-getting-started
 - **Advanced Features**: stateful-server (2025-pinned), pagination-server, tasks-e2e-inmemory-server (2025-pinned)
 - **Macro System**: derive-macro-server, function-macro-server, function-resource-server
 - **Serverless**: lambda-mcp-server (AWS Lambda with SQS integration)
@@ -1192,7 +1191,6 @@ curl -N -H "Accept: text/event-stream" \
 ## 📊 Business Value Examples
 
 ### Enterprise Integration
-- **dynamic-resource-server**: API orchestration across Customer, Inventory, Financial, and HR systems
 - **audit-trail-server**: SOX, PCI DSS, GDPR, and HIPAA compliance reporting
 
 ### Developer Productivity

docs/plans/2026-07-28-examples-review.md

@@ -26,6 +26,13 @@ own binary. The worst offenders print broken curl commands from their own stdout
 
 ## 🗄️ Archive (4) — no remaining teaching value or actively misleading
 
+> **EXECUTED 2026-06-12** (maintainer-approved slice 1): all four moved to
+> `examples/archived/` with dated banners; `session-aware-logging-demo`
+> merged (archived as a superseded duplicate of `session-logging-proof-test`)
+> in the same slice. Workspace members, EXAMPLES.md, root README,
+> `verify_phase{2,5,8}.sh`, and the compilation-validation test list cleaned
+> in the same commit.
+
 | Example | Lane | Teaches | Why / required fixes | Gate-ref |
 |---|---|---|---|---|
 | `alert-system-server` | 2026-default | A rule-based alerting domain app (cooldowns, severities, regex log matching) built from derive-macro tools persisting rules/history in framework SessionContext state. | Its two teachable ideas are both better taught elsewhere on the 2026 lane: session-state-on-stateless-transport is owned by examples/stateful-server (which has the correct 2026 'application-level SessionContext is not the removed transport session' framing), and derive-macro tool patterns are owned by derive-macro-server. What remains is ~600 lines of un-README'd domain logic that, unframed, actively suggests transport sessions exist on the 2026 default. The repo already has an examples/archived/ mechanism. Only reference is the legacy manual scripts/verify_phase5.sh:229 — not ci-gates.sh, not .github/workflows, not e2e_utils.rs — so archiving is safe. If the maintainer wants a 'realistic app' demo to survive, the alternative is a merge of its cooldown/severity flavor into stateful-server, with stateful-server surviving. — **Staleness:** No README at all (only Cargo.toml + src); main.rs:117,275,513 hard-fail with 'Session required' and store everything in SessionContext with zero framing that on 2026 this is the framework's application-level state layer, NOT the removed transport session (contrast examples/stateful-server/README.md:63-68, which was given exactly that framing in a12f14c — this example was skipped by that rewrite); main.rs:661 `.sse(true)` is a no-op on the 2026 POST-only lane; main.rs:1-6 doc-comment says 'manage alert history using session state' with no 2026 caveat. | no |
@@ -35,6 +42,8 @@ own binary. The worst offenders print broken curl commands from their own stdout
 
 ## 🔀 Merge (1) — duplicate of a sibling
 
+> **EXECUTED 2026-06-12** — see the archive note above.
+
 | Example | Lane | Teaches | Why / required fixes | Gate-ref |
 |---|---|---|---|---|
 | `session-aware-logging-demo` | 2025-pinned | Per-session MCP logging-level filtering: tools call session.notify_log and a session-scoped level (set via a custom tool) determines which notifications/message events reach that session's SSE stream. | Correctly manifest-pinned to protocol-2025-11-25 (Cargo.toml:9-13), but it is a strict subset of session-logging-proof-test: identical architecture (server with a send-log-at-level tool + set-level tool, inline reqwest client doing initialize → set level → cascade filtering checks), while proof-test adds 3-session isolation, the full level cascade, and PASS/FAIL verification instructions. It also sets the level via a custom tool rather than the spec logging/setLevel method, so it teaches nothing the survivor doesn't. Merge into session-logging-proof-test (survivor). Not referenced by any CI gate (only legacy verify_phase8.sh:95-144). — **Staleness:** src/main.rs:187-194 inline client hardcodes protocolVersion 2025-06-18 (annotated as intentional backward-compat testing); src/main.rs:292 .version("1.0.0"); Cargo.toml lacks the '2025-11-25 regression example' manifest comment its siblings logging-test-server/client carry | no |

examples/alert-system-server/Cargo.toml …/archived/alert-system-server/Cargo.tomlexamples/alert-system-server/Cargo.toml renamed to examples/archived/alert-system-server/Cargo.toml examples/alert-system-server/Cargo.toml renamed to examples/archived/alert-system-server/Cargo.toml

@@ -0,0 +1,5 @@
+> **ARCHIVED 2026-06-12** — session-state-on-stateless-transport is owned by `stateful-server` (2025-pinned, correctly framed) and derive-macro patterns by `derive-macro-server`; what remained suggested transport sessions exist on the 2026 lane.
+> Disposition record: `docs/plans/2026-07-28-examples-review.md`. Not a
+> workspace member; kept for reference only.
+
+# alert-system-server

examples/archived/alert-system-server/README.md

@@ -1,3 +1,7 @@
+> **ARCHIVED 2026-06-12** — its name/README promised dynamic-resource teaching the code never contained (zero resources registered); URI-template resources are owned by `function-resource-server`.
+> Disposition record: `docs/plans/2026-07-28-examples-review.md`. Not a
+> workspace member; kept for reference only.
+
 # Dynamic Resource Server Example
 
 A comprehensive demonstration of **dynamic MCP resources** with parameterized URIs for accessing specific entities. This example shows how real-world resource systems should work with identifiers instead of static paths.