It's time for your daily thwarting

Signed-off-by: itowlson <ivan.towlson@fermyon.com>

Author: itowlson

.build/check-broken-links.sh

@@ -90,6 +90,9 @@ if ! blc -rv
     --exclude 'https://marketplace.visualstudio.com/items?itemName=BytecodeAlliance.starlingmonkey-debugger'                                                                                \
     --exclude 'http://localhost:16686/'                                                                                                                                                     \
     --exclude 'http://localhost:5050/explore'                                                                                                                                               \
+    `## Spin 4 bits not yet published`                                                                                                                                                                    \
+    --exclude 'https://github.com/spinframework/spin-docs/blob/main/content/v4'                                                                                                                                               \
+    --exclude 'https://docs.rs/spin-sdk/latest/spin_sdk'                                                                                                                                               \
     http://127.0.0.1:3000/v3/javascript-components                                                                                                                                          \
     | tee "${report}"
 then 

content/v4/contributing-docs.md

@@ -8,10 +8,9 @@ keywords = "contribute contributing"
 ---
 
 - [Technical Documentation Types](#technical-documentation-types)
-  - [1. Tutorials](#1-tutorials)
-  - [2. How-To Guides](#2-how-to-guides)
-  - [3. Reference](#3-reference)
-  - [4. Explanation](#4-explanation)
+  - [1. How-To Guides](#1-how-to-guides)
+  - [2. Reference](#2-reference)
+  - [3. Explanation](#3-explanation)
 - [Technical Documentation Procedure](#technical-documentation-procedure)
   - [1. Fork the Repository](#1-fork-the-repository)
   - [2. Clone the Fork](#2-clone-the-fork)
@@ -40,21 +39,17 @@ Below are a few pointers designed to help you contribute.
 
 ## Technical Documentation Types
 
-The following points will help guide your contribution from a resource-type perspective; essentially we would really appreciate you creating and contributing any of the following 4 resource types. 
+The following points will help guide your contribution from a resource-type perspective; essentially we would really appreciate you creating and contributing any of the following 3 resource types. 
 
-### 1. Tutorials
-
-Tutorials are oriented toward learning. Tutorials are designed to get a user started on something new (that they have not tried before). You can think of a tutorial as a lesson i.e. teaching a Spin user [how to use the Key Value store to persist data](/key-value-store-tutorial.md). The tutorial may contain many logically ordered steps i.e. installing Spin, using Spin templates, configuring a Spin application and so forth. The desired outcome for a tutorial is for the user to have a working deployment or application. Think of it as a lesson in how to bake a cake.
-
-### 2. How-To Guides
+### 1. How-To Guides
 
 How-to guides are oriented towards showing a user how to solve a problem, which leads them to be able to achieve their own goal. The how-to guide will follow a series of logical steps. Think of it as providing a recipe for the user's creativity. For example, you can show a user how to [develop a Spin application](/writing-apps.md) without telling them what the application must do; that is up to the user's imagination.
 
-### 3. Reference
+### 2. Reference
 
 Reference resources are merely a dry description; describing the feature in its simplest form. An example of a reference resource is the [Spin application manifest reference](./manifest-reference). You will notice that the Manifest Reference page simply lists all of the manifest entries and available options.
 
-### 4. Explanation
+### 3. Explanation
 
 An explanation resource is written using a deep-dive approach i.e. providing a deep explanation with the view to impart a deep understanding of a particular concept, feature or product. You may find your contribution is so in-depth that it becomes a long form article like a blog post. If that is the case, consider an addition to the Spin Blog.
 
@@ -147,7 +142,7 @@ If you want the code in a code block to be copyable with no "smarts" to remove t
 
 **Multi-tab code blocks**
 
-Examples of multi-tab blocks can be seen in the [Spin installer documentation](./install#installing-spin) and [Spin Key/Value documentation](./key-value-store-tutorial#the-spin-toml-file). The above examples demonstrate how tabs can either represent platforms i.e. `Windows`, `Linux` and `macOS` or represent specific programming languages i.e. `Rust`, `JavaScript` and `Golang` etc. Here is a brief example of how to implement multi-tab code blocks when writing technical documentation for this site, using markdown.
+Examples of multi-tab blocks can be seen in the [Spin installer documentation](./install#installing-spin). The above examples demonstrate how tabs can either represent platforms i.e. `Windows`, `Linux` and `macOS` or represent specific programming languages i.e. `Rust`, `JavaScript` and `Golang` etc. Here is a brief example of how to implement multi-tab code blocks when writing technical documentation for this site, using markdown.
 
 The first step to implementing multi-tab code blocks is placing the `enable_shortcodes = true` configuration at the start of the `.md` file. Specifically, in the `.md` file's frontmatter.
 

content/v4/go-components.md

@@ -371,7 +371,7 @@ WASI can be used when implementing a Spin component.
 
 ## Storing Data in the Spin Key-Value Store
 
-Spin has a key-value store built in. For information about using it from TinyGo, see [the key-value store tutorial](key-value-store-tutorial).
+Spin has a key-value store built in. For information about using it from TinyGo, see [the key-value API guide](kv-store-api-guide).
 
 ## Storing Data in SQLite
 

content/v4/http-trigger.md

@@ -310,7 +310,7 @@ The HTTP component interface is defined using a WebAssembly Interface (WIT) file
 
 The HTTP types and interfaces are defined in [https://github.com/spinframework/spin/tree/main/wit/deps/http@0.3.0-rc-2026-03-15](https://github.com/spinframework/spin/tree/main/wit/deps/http@0.3.0-rc-2026-03-15), which tracks [the `wasi-http` specification](https://github.com/WebAssembly/wasi-http).
 
-In particular, the entry point for Spin HTTP components is defined in [the `handler` interface](https://github.com/spinframework/spin/blob/main/wit/deps/http@0.3.0-rc-2026-03-15/handler.wit):
+In particular, the entry point for Spin HTTP components is defined in [the `handler` interface](https://github.com/spinframework/spin/blob/main/wit/deps/http@0.3.0-rc-2026-03-15/worlds.wit):
 
 <!-- @nocpy -->
 

content/v4/javascript-components.md

@@ -309,7 +309,7 @@ allowed_outbound_hosts = ["redis://localhost:6379"]
 
 ## Storing Data in the Spin Key-Value Store
 
-Spin has a key-value store built in. For information about using it from TypeScript/JavaScript, see [the key-value store tutorial](key-value-store-tutorial).
+Spin has a key-value store built in. For information about using it from TypeScript/JavaScript, see [the key-value API guide](kv-store-api-guide).
 
 ## Storing Data in SQLite
 

content/v4/kv-store-api-guide.md

@@ -10,7 +10,7 @@ url = "https://github.com/spinframework/spin-docs/blob/main/content/v4/kv-store-
 - [Custom Key Value Stores](#custom-key-value-stores)
 - [Granting Key Value Store Permissions to Components](#granting-key-value-store-permissions-to-components)
 
-Spin provides an interface for you to persist data in a key value store managed by Spin. This key value store allows Spin developers to persist non-relational data across application invocations. To learn more about key value store use cases and how to enable your Spin application to use a key value store, check out our [key value tutorial](./key-value-store-tutorial.md).
+Spin provides an interface for you to persist data in a key value store managed by Spin. This key value store allows Spin developers to persist non-relational data across application invocations.
 
 {{ details "Why do I need a Spin interface? Why can't I just use my own external store?" "You can absolutely still use your own external store either with the Redis or Postgres APIs, or outbound HTTP. However, if you're interested in quick, non-relational local storage without any infrastructure set-up then Spin's key value store is a great option." }}
 

content/v4/rdbms-storage.md

@@ -31,6 +31,8 @@ The Spin SDK surfaces the Spin MySQL and PostgreSQL interfaces to your language.
 | `query`    | statement, SQL parameters  | database records    | Runs the specified statement against the database, returning the query results as a set of rows. |
 | `execute`  | statement, SQL parameters  | integer (not MySQL) | Runs the specified statement against the database, returning the number of rows modified by the statement.  (MySQL does not return the modified row count.) |
 
+> The PostgreSQL interface is asynchronous (a blocking one is available for backward compatibility); the MySQL interface is blocking.
+
 The exact detail of calling these operations from your application depends on your language:
 
 {{ tabs "sdk-type" }}
@@ -39,22 +41,20 @@ The exact detail of calling these operations from your application depends on yo
 
 > [**Want to go straight to the reference documentation?**  Find it here.](https://docs.rs/spin-sdk/latest/spin_sdk/index.html)
 
-MySQL functions are available in the `spin_sdk::mysql` module, and PostgreSQL functions in the `spin_sdk::pg4` module.
-
-> If you want to be compatible with Spin 3.3 or earlier, or with downstream hosts that have not yet rolled out Spin 3.4 support, you should use the `spin_sdk::pg3` module for PostgreSQL. The module interfaces are identical, but `pg3` does not support all the data types in `pg4`.
+MySQL functions are available in the `spin_sdk::mysql` module, and PostgreSQL functions in the `spin_sdk::pg` module.
 
-The function names match the operations above. This example shows MySQL:
+The function names match the operations above. This example shows MySQL (blocking):
 
 ```rust
-// For PostgreSQL, use `spin_sdk::pg` or `spin_sdk::pg3`
 use spin_sdk::mysql::{self, Connection, Decode, ParameterValue};
 
 let connection = Connection::open(&address)?;
 
 let params = vec![ParameterValue::Int32(id)];
-// For PostgreSQL, use `$1` placeholder syntax
+
 let rowset = connection.query("SELECT id, name FROM pets WHERE id = ?", &params)?;
 
+// MySQL returns the rows as a vector
 match rowset.rows.first() {
     None => /* no rows matched query */,
     Some(row) => {
@@ -63,6 +63,27 @@ match rowset.rows.first() {
 }
 ```
 
+And PostgreSQL (async):
+
+```rust
+use spin_sdk::pg::{self, Connection, Decode, ParameterValue};
+
+let connection = Connection::open(&address).await?;
+
+let params = vec![ParameterValue::Int32(id)];
+
+let (columns, rows, result) = connection.query("SELECT id, name FROM pets WHERE id = $1", &params).await?;
+
+// PostgreSQL returns the rows as a stream
+while let Some(row) = rows.next().await {
+	let name = String::decode(&row[1])?;
+	// ... more processing ...
+}
+
+// Check if the row stream ended due to completion or an error
+result.await?;
+```
+
 **Notes**
 
 * Parameters are instances of the `ParameterValue` enum; you must wrap raw values in this type.

content/v4/rust-components.md

@@ -446,7 +446,7 @@ The future does not resolve until the stream ends, so be sure not to await it un
 
 ## Storing Data in the Spin Key-Value Store
 
-Spin has a key-value store built in. For information about using it from Rust, see [the key-value store tutorial](key-value-store-tutorial).
+Spin has a key-value store built in. For information about using it from Rust, see [the key-value API guide](kv-store-api-guide).
 
 ### Serializing Objects to the Key-Value Store
 

content/v4/testing-apps.md

@@ -230,7 +230,7 @@ key_value_stores = ["default"]
 ...
 ```
 
-> If you would like to learn more about Key Value storage, see [this tutorial](./key-value-store-tutorial.md).
+> If you would like to learn more about Key Value storage, see [the key-value API guide](kv-store-api-guide).
 
 After editing, the whole `my-app/spin.toml` file will look like the following:
 

content/v4/writing-apps.md

@@ -356,7 +356,7 @@ By default, Spin components are not allowed to access Spin's storage services.
 key_value_stores = [ "default" ]
 ```
 
-See [Persisting Data with Spin](key-value-store-tutorial) for more information.
+See [the key-value API guide](kv-store-api-guide) for more information.
 
 ## Example Manifests