You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> strings are runtime test stages (not dev-phase tags) — kept; 2025-lane
97
+
> initialize banners/curls in pinned examples are lane-correct — kept;
98
+
> house-placeholder `.version("1.0.0")` strings outside the two named
99
+
> examples — kept per the audit's own function-resource-server note.
100
+
73
101
| Example | Lane | Teaches | Why / required fixes | Gate-ref |
74
102
|---|---|---|---|---|
75
103
| `audit-trail-server` | 2026-default | Application-owned persistence inside tools: an immutable SQLite (sqlx) audit log with log/search/report tools, independent of the framework's session storage. | The core pattern — tools owning their own sqlx pool (OnceLock at main.rs:19) for durable, queryable application data — is spec-neutral and fully current on 2026; it compiles clean on the default lane. The fix is narrow: re-anchor actor/correlation from session_id to a 2026-meaningful identity (per-request _meta clientInfo, W3C traceparent per the spec plan's distributed-tracing item, or an explicit actor param), rewrite the unique_sessions stats, and drop the session-required framing. Not a merge/archive candidate — no sibling teaches app-owned DB persistence. — **Staleness:** src/main.rs:108 keys every audit row by session.session_id and main.rs:347-370 reports 'unique_sessions' / 'events_per_session' stats — on the 2026 default the session id is an ephemeral per-request internal id (never sent to the client), so unique_sessions ≈ total_events and the attribution/statistics are meaningless; main.rs:99 'Session required' gating implies a client-visible session that no longer exists; main.rs:443 with_session_storage(SqliteSessionStorage) is incidental to the example's teaching | no |
0 commit comments