From cde003c697dc22b80c063029d2697e69be5e0c8d Mon Sep 17 00:00:00 2001
From: Serge Rabyking <serge.rabyking@chipflow.io>
Date: Sat, 16 May 2026 20:37:40 +0200
Subject: [PATCH] docs: add gf180mcu process and per-origin credentials
 behaviour

Catches the training docs up with two recent chipflow-lib changes:

- #169 adds Process.GF180MCU = "gf180mcu", and the matching backend
  techno plugin plus SRAM IP make it end-to-end usable, including
  automatic memory inference. Listed alongside ihp_sg13g2 in both
  the Supported Processes table and the chipflow.toml reference.

- The credentials file is now keyed by origin instead of holding a
  single api_key, and 'chipflow auth login' always re-mints rather
  than reusing a cached key. Documents the new file shape, the
  automatic migration of legacy single-key files, and the per-origin
  scope of logout.
---
 chipflow-toml-reference.md |  1 +
 training-commands.md       | 19 +++++++++++++++++++
 2 files changed, 20 insertions(+)

diff --git a/chipflow-toml-reference.md b/chipflow-toml-reference.md
index f7051cd..abdebba 100644
--- a/chipflow-toml-reference.md
+++ b/chipflow-toml-reference.md
@@ -38,6 +38,7 @@ Required for silicon builds.
 | Value | Description |
 |-------|-------------|
 | `ihp_sg13g2` | IHP 130nm SiGe BiCMOS open-source process |
+| `gf180mcu` | GlobalFoundries 180nm MCU open-source PDK — four-size SRAM IP available for automatic memory inference |
 
 **Voltage format:** float or string with optional `V` suffix (e.g. `1.8`, `"1.8V"`, `"1.8v"`).
 
diff --git a/training-commands.md b/training-commands.md
index dc07072..20f1836 100644
--- a/training-commands.md
+++ b/training-commands.md
@@ -208,12 +208,28 @@ When `CHIPFLOW_API_KEY` is set, chipflow-lib uses it directly and skips all othe
 cat ~/.config/chipflow/credentials
 ```
 
+The credentials file is keyed by origin (the platform URL you authenticated against), so a key for `https://build.chipflow.com` and one for a staging endpoint coexist without overwriting each other:
+
+```json
+{
+  "origins": {
+    "https://build.chipflow.com": { "api_key": "..." }
+  }
+}
+```
+
+Legacy single-key files from older chipflow-lib versions are migrated automatically on first use — no manual cleanup needed.
+
+`chipflow auth login` always re-authenticates and re-mints the key for its target origin, even when a cached key is already present. This avoids silently returning a stale key after switching environments.
+
 ### Logout (removes saved credentials from Option A)
 
 ```bash
 uv run chipflow auth logout
 ```
 
+`logout` only removes the entry for the current origin; keys for other origins stay in place.
+
 ---
 
 ## Pin Assignment and pins.lock
@@ -423,6 +439,9 @@ The Makefile in this repository sets `CHIPFLOW_ROOT` automatically for each desi
 | Process | Value in chipflow.toml |
 |---------|----------------------|
 | IHP 130nm SiGe BiCMOS | `ihp_sg13g2` |
+| GlobalFoundries 180nm MCU | `gf180mcu` |
+
+Both processes include automatic SRAM inference — declare an Amaranth `Memory(...)` of appropriate depth/width and the build flow picks the right macro from the PDK's library.
 
 Other processes may be available on request. If your target process is not yet supported, the ChipFlow team can work with you to port it to the platform — contact us for details.