Add Auth0 tutorial

[JulienLavocat]

Description of Changes

Add Auth0 tutorial

API and ABI breaking changes

None.

Expected complexity level and risk

1

Testing

• Followed rendered tutorial on the locally running website

[JulienLavocat]

/update-llm-benchmark

[clockwork-labs-bot]

LLM Benchmark Results (ci-quickfix)

Language	Mode	Category	Tests Passed	Pass %	Task Pass %
Rust	rustdoc_json	basics	25/27	92.6%	83.3%
Rust	rustdoc_json	schema	28/34	82.4%	76.7%
Rust	rustdoc_json	total	53/61	86.9%	80.3%
C#	docs	basics	27/27	100.0%	100.0%
C#	docs	schema	28/34	82.4%	80.0%
C#	docs	total	55/61	90.2%	90.9%

_{Generated at: 2026-01-16T12:55:05.384Z}

[JulienLavocat]

/update-llm-benchmark

[cloutiertyler]

I have not tried it directly, but I think this is a good start and we should merge it and fix any issues that arise. Once the docs are more complete, I'm going to try to build some apps on stream

[JulienLavocat]

/update-llm-benchmark

[JulienLavocat]

/update-llm-benchmark

[clockwork-labs-bot]

LLM Benchmark Results (ci-quickfix)

Language	Mode	Category	Tests Passed	Task Pass %
Rust	rustdoc_json	basics	17/25	67.4% ⬇️ -16.0%
Rust	rustdoc_json	schema	32/34	90.0% ⬆️ +10.0%
Rust	rustdoc_json	total	49/59	77.7% ⬇️ -4.2%
C#	docs	basics	11/25	58.3% ⬇️ -2.8%
C#	docs	schema	10/34	31.5%
C#	docs	total	21/59	46.1% ⬇️ -1.5%

Compared against master branch baseline

_{Generated at: 2026-01-20T11:45:02.790Z}

Failure Analysis (click to expand)

Benchmark Failure Analysis

Generated from: /__w/SpacetimeDB/SpacetimeDB/tools/xtask-llm-benchmark/../../docs/llms/docs-benchmark-details.json

Summary

• Total failures analyzed: 24

Analysis

Analysis of SpacetimeDB Benchmark Failures

Rust Failures

1. Root Causes

1. Missing Primary Keys and Public Modifiers:

   • Several tests (e.g., t_005_update, t_006_delete, t_007_crud, etc.) fail due to missing access modifiers on the struct fields. Notably, primary keys should have pub to be accessible.

2. Schedule At Usage:

   • In scheduled tests like t_002_scheduled_table and t_017_scheduled_columns, the documentation does not clearly explain how to properly set up scheduled reducers and columns.

3. Table Definitions:

   • Errors in identifying the tables may suggest that the documentation lacks details on how to ensure tables are created or seeded correctly before executing tests.

4. General Error Handling:

   • Many errors include warnings about instability, indicating the documentation hasn’t adequately prepared users for expected limitations or how to work around them.

2. Recommendations

a. Update Documentation for Struct Fields

• Section: Struct Field Modifiers
• Change: Reinforce that all fields in structs representing tables should be declared as pub (public).

  #[primary_key]
  pub id: i32,

b. Clarify Schedules and Reducers

• Section: Scheduling and Reducers
• Change: Provide specific examples that detail correct usage of scheduled reducers and column definitions.

  #[table(name = tick_timer, schedule(reducer = tick, column = scheduled_at))]

c. Table Creation and Seeding

• Section: Database Setup
• Change: Include a walkthrough for initializing and seeding tables prior to executing tests.

d. Error Handling in Tests

• Section: Error Messages
• Change: Update the documentation to clarify the potential implications of unstable commands and how to handle them, including fallbacks or alternative methods.

3. Priority

• High: Improvements on struct field access modifiers and scheduling examples.
• Medium: Recommendations on table setup and seeding.
• Low: Enhancements to error handling and stability notes.

---

C# Failures

1. Root Causes

1. Missing Public Modifiers:

   • Similar to Rust, many C# errors arise from the lack of public modifiers for struct fields, which can affect accessibility (e.g., t_004_insert, t_006_delete, etc.).

2. Table Name Consistency Issues:

   • Documented table names must match the expected names in the declarations to avoid runtime errors regarding nonexistent tables.

3. Redundant Modifiers:

   • There are inconsistencies where the Public = true attribute is unnecessary in certain contexts, leading to confusion.

4. Unstable Command Warnings:

   • Like Rust, frequent unstable command warnings highlight the need for better communication regarding command limitations.

2. Recommendations

a. Overview of Struct Fields

• Section: Struct Field Modifiers
• Change: Emphasize that all fields must be marked as public to ensure accessibility within the library.

  [PrimaryKey] public int Id;

b. Consistent Table Naming

• Section: Table Naming Conventions
• Change: Outline naming conventions clearly to ensure consistency between struct definitions and database references.

c. Clean Up Redundant Modifiers

• Section: Table Attribute Usage
• Change: Simplify the examples that use Public = true, focusing on when it is truly necessary.

d. Addressing Unstable Command Handling

• Section: Managing Instabilities
• Change: Provide guidance on how to manage and respond to warnings during command execution.

3. Priority

• High: Adjustments on struct field access and consistent naming conventions.
• Medium: Cleanup on redundant modifiers and reasserting proper access control.
• Low: Instructions on managing unstable commands.

With these changes, we expect a decrease in benchmark test failures and enhanced reliability in user implementations.