[DOCS] README: reorder sections and rename "Custom resources" to "New resources"

README.md

@@ -20,13 +20,13 @@ A Streamlit app for optimising carbon removal portfolios across different method
 - [Data Maintenance Guide](#data-maintenance-guide)
   - [How it works](#how-it-works-overview)
     - [App tabs](#app-tabs)
-    - [Custom resources](#custom-resources)
+    - [New resources](#new-resources)
     - [Scenarios (save and compare)](#scenarios-save-and-compare)
+  - [File structure](#file-structure-what-each-data-file-does)
+  - [Understanding inputs.csv](#understanding-inputscsv)
   - [Option 1: Hugging Face](#option-1-edit-directly-on-hugging-face-no-local-setup-needed)
   - [Option 2: Local](#option-2-work-locally)
   - [Quick reference](#quick-reference-where-is-each-parameter)
-  - [File structure](#file-structure-what-each-file-does)
-  - [Understanding inputs.csv](#understanding-inputscsv)
 - [Maintenance cases](#maintenance-cases)
   - [Before you start](#before-you-start)
   - [Case 1 - Modify existing coefficient values](#case-1--modify-existing-coefficient-values)
@@ -70,7 +70,7 @@ data/inputs.csv
 
 Every time the app starts, it computes a fingerprint (hash) of the CSV and compares it to the last known value. If they differ, meaning the CSV has been modified, it automatically regenerates all the data files used by the application before loading. You do not need to run anything manually.
 
-**Automatic method deactivation:** if a CDR method requires resources that the user has not added in the Resource inputs tab, the method is automatically disabled in the Method constraints and Portfolio generation tabs. A "Why is this method disabled?" indicator is shown next to the method. This is expected behavior — no data change is needed.
+**Automatic method deactivation:** if a CDR method requires resources that the user has not added in the Resource inputs tab, the method is automatically disabled in the Method constraints and Portfolio generation tabs. A "Why is this method disabled?" indicator is shown next to the method. This is expected behavior: no data change is needed.
 
 ---
 
@@ -81,7 +81,7 @@ The app has seven tabs, accessible from the left sidebar:
 | Tab | Name | Purpose |
 |-----|------|---------|
 | Welcome | Welcome | Introduction, instructions, and a quick-start guide |
-| Resource inputs | Resource inputs | Set the available quantity of each resource; add custom resource batches |
+| Resource inputs | Resource inputs | Set the available quantity of each resource; add new resource batches |
 | Method constraints | Method constraints | Activate or deactivate CDR methods; set caps and constraints per method |
 | Resource coefficients | Resource coefficients | View and adjust the coefficient values (min / median / max) used by the optimiser |
 | Portfolio generation | Portfolio generation | Run the LP optimiser and view results (charts, tables, resource usage) |
@@ -90,25 +90,73 @@ The app has seven tabs, accessible from the left sidebar:
 
 ---
 
-### Custom resources
+### New resources
 
-In the **Resource inputs** tab, users can add custom resource batches — named resources that substitute for a standard or "Other" reference resource within a specific CDR method.
+In the **Resource inputs** tab, users can add new resource batches: named resources that substitute for a standard or "Other" reference resource within a specific CDR method.
 
-For example, a user might add a batch called "Basalt A" linked to the reference group "Basalt mineral" and assign it to the Enhanced weathering method. The optimiser will then use the batch's custom coefficients instead of the standard reference values for that method.
+For example, a user might add a batch called "Basalt A" linked to the reference group "Basalt mineral" and assign it to the Enhanced weathering method. The optimiser will then use the batch's new coefficients instead of the standard reference values for that method.
 
-Custom batches are stored in the session and saved when exporting a scenario. They do **not** require any change to `inputs.csv`.
+New batches are stored in the session and saved when exporting a scenario. They do **not** require any change to `inputs.csv`.
 
 ---
 
 ### Scenarios (save and compare)
 
+In the **Portfolio generation** tab (Export & Save sub-tab), users can:
+
+- **Export** the current inputs only as an Excel `.xlsx` file, or the full scenario (inputs, constraints, coefficients, and optimisation results) as a `.json` file or a `.zip` of CSVs
+- **Import** a previously exported Excel file to reload inputs into all tabs, or a previously exported `.json`/`.zip` scenario file to restore a complete session and re-run the optimisation
+
 In the **Scenario comparison** tab, users can:
 
-- **Export** the current state (resource caps, method constraints, coefficients, optimisation results) as a `.zip` file or an Excel `.xlsx` file
-- **Import** a previously exported scenario file to restore a complete session state
-- **Compare** multiple saved scenarios side by side in the charts
+- Upload one or more saved scenario files (`.json` or `.zip`) and **compare** them side by side in the charts
+
+Scenario files are standalone and portable. Exporting a `.json` or `.zip` preserves the full state including new resource batches; the Excel format covers only the inputs and can be opened directly in Excel.
+
+---
+
+### File structure (what each data file does)
+
+| File | What it is | Do you edit it? |
+|------|-----------|-----------------|
+| `data/inputs.csv` | **Main data file**: all methods, resources and coefficients | ✅ Yes |
+| `data/ui_text.xlsx` | Tooltip texts (on hover), "why is this method disabled?" notes, and each tab's intro paragraph | ✅ Yes |
+| `data/update.py` | Orchestration script: runs both generators below and updates the hash file | ❌ No |
+| `data/generate_model_data.py` | Generates `cost_sliders.json`, `method_groups.json`, `secondary_resources.json` from the CSV | ❌ No |
+| `data/generate_resource_template.py` | Generates `resource_template.xlsx` from the CSV | ❌ No |
+| `data/cost_sliders.json` | Auto-generated. Coefficients used by the app | ❌ No (auto) |
+| `data/method_groups.json` | Auto-generated. CDR method categories | ❌ No (auto) |
+| `data/secondary_resources.json` | Auto-generated. Optional resource assignments | ❌ No (auto) |
+| `data/resource_template.xlsx` | Auto-generated. Excel template for users | ❌ No (auto) |
+| `data/.csv_hash` | Auto-generated. Stores a fingerprint of `inputs.csv` to detect changes on restart | ❌ No (auto) |
+
+> ⚠️ **Never edit the auto-generated files directly**: your changes will be overwritten the next time `update.py` is run.
+
+### Understanding `inputs.csv`
+
+Each row represents **one resource used by one CDR method**, with the following columns:
+
+| Column | Description | Example |
+|--------|-------------|---------|
+| `Implementation` | Name of the CDR method | `Afforestation/reforestation` |
+| `Method group` | Category the method belongs to | `Forestry` |
+| `Resource` | Name of the resource used | `Other land` |
+| `Resource group` | Category the resource belongs to | `Land` |
+| `Type` | Physical type of the resource | `Physical` |
+| `Unit` | Unit of the coefficient (per MtCO₂) | `Mha/MtCO2` |
+| `min` | Minimum coefficient value | `0.002` |
+| `median` | Default (median) coefficient value | `0.094927` |
+| `max` | Maximum coefficient value | `0.384615` |
+| `Is secondary` | Whether this resource is optional for this method | `FALSE` |
+
+> **Primary resources** (`Is secondary = FALSE`) are always active in the model.
+> **Secondary resources** (`Is secondary = TRUE`) are optional: users can toggle them on in the app.
+
+> **Naming convention: "Other" resources:** any resource whose name starts with `Other ` (capital O, followed by a space - e.g. `Other land`, `Other water`) is **hidden from the standard resource display** in Tabs 1 and 3. It still functions normally in the model and remains available as a reference group in the "Add resource" dialog. Use this convention intentionally when you want a resource to be inherited by new user-defined batches but not shown as a standalone input row.
+
+> **Naming convention: "Other" methods:** any CDR method whose name starts with `Other` receives special treatment in the optimiser. Instead of appearing as a fixed method, the LP automatically creates **one variant per new resource batch** the user adds that is linked to that method. This is intended for generic CDR pathways where the type of resource is user-defined. If you add a method using this naming convention, make sure it is intentional.
 
-Scenario files are standalone and portable. Exporting a ZIP preserves the full state including custom resource batches; the Excel format covers the core results and can be opened directly in Excel.
+> **Resource group and OR-substitutable resources:** when a CDR method has two or more **active** resources (primary, or secondary once toggled on) that belong to the same `Resource group`, the optimiser treats them as **interchangeable (OR)**. The method can satisfy its resource need from either one, or any mix of the two, rather than requiring all of them simultaneously. Users will see a hint like *"only one of Other land, Arable land is required"* in the "Why is this method disabled?" panel for primary siblings (secondary siblings are pooled by the optimiser the same way, but this specific hint currently only covers primary resources - see [Case 6](#case-6--change-whether-a-resource-is-optional-secondary-for-a-method)). This behaviour is automatic: it is triggered purely by two active resources sharing the same `Resource group` for the same method, whether or not they are primary. **If you add a resource to an existing group for a method that already has a resource active in that group, you are creating an OR relationship: make sure this is intentional.** If it is not, create a new resource group instead (see Case 5).
 
 ---
 
@@ -120,7 +168,7 @@ This is the simplest option for non-coders with admin access to the Hugging Face
 
 **Steps:**
 
-1. Go to the Hugging Face **Space** (Carbon Dioxide Removal Toolkit) → click the **Files** tab
+1. Go to the Hugging Face **Space** (https://huggingface.co/CGdev: Carbon Dioxide Removal Toolkit) → click the **Files** tab
 2. Open `data/inputs.csv` and click **Edit** (pencil icon)
    *OR*
    Upload a new version of the file: click **Delete** `data/inputs.csv`, then go to **data** folder → click **+ Contribute** → Upload Files
@@ -145,7 +193,7 @@ Use this option when making bigger changes where you want to preview the result
 
 Before starting, make sure you have **Python** (version 3.9 or later) and **git** installed on your machine:
 - Python: https://www.python.org/downloads/ (tick *Add Python to PATH* during installation on Windows)
-- git — Mac: https://git-scm.com/download/mac — Windows: https://git-scm.com/download/win
+- git - Mac: https://git-scm.com/download/mac - Windows: https://git-scm.com/download/win
 
 Then in a terminal, navigate to the folder where you want to put the project and run:
 ```
@@ -153,7 +201,7 @@ git clone <repository URL>
 ```
 Example:
 ```
-git clone https://huggingface.co/spaces/CarbonGap/CRRA_Optimization_Tool
+git clone https://huggingface.co/spaces/CarbonGap/CRRA_Optimization_Tool_V2
 ```
 
 **Step 1b: Set up the Python environment (first time only)**
@@ -239,56 +287,13 @@ Hugging Face will detect the push and rebuild the Space automatically.
 | The app's UI colours and font (fine-tuned overrides) | `assets/styles.css` | `:root` block at the top of the file - change the hex values next to each variable name |
 | The tooltip text on a method name | `data/ui_text.xlsx` | Sheet **Methods**: column `Tooltip` |
 | The tooltip text on a resource name | `data/ui_text.xlsx` | Sheet **Resources**: column `Tooltip` |
-| The text shown in "Why is this method disabled?" for a specific method | `data/ui_text.xlsx` | Sheet **Methods**: column `Note` — supports basic HTML (see [Case 8](#case-8--edit-tooltip-method-note-and-section-intro-texts)) |
-| The "OBJECTIVE" intro paragraph at the top of a tab | `data/ui_text.xlsx` | Sheet **Section Intros**: column `Text`, row selected by `Tab` — supports basic HTML (see [Case 8](#case-8--edit-tooltip-method-note-and-section-intro-texts)) |
+| The text shown in "Why is this method disabled?" for a specific method | `data/ui_text.xlsx` | Sheet **Methods**: column `Note`, supports basic HTML (see [Case 8](#case-8--edit-tooltip-method-note-and-section-intro-texts)) |
+| The "OBJECTIVE" intro paragraph at the top of a tab | `data/ui_text.xlsx` | Sheet **Section Intros**: column `Text`, row selected by `Tab`, supports basic HTML (see [Case 8](#case-8--edit-tooltip-method-note-and-section-intro-texts)) |
 | UI spacing, font sizes, button styles | `assets/styles.css` | Standard CSS: search for the element name |
 | Python library versions | `requirements.txt` | One line per library: see Library Maintenance Guide below |
 
 > After any change to `inputs.csv`, start the app - it detects the change and updates automatically. After changes to `config/config.py`, `assets/styles.css`, or `data/ui_text.xlsx`, simply restart the app.
 
-### File structure (what each file does)
-
-| File | What it is | Do you edit it? |
-|------|-----------|-----------------|
-| `data/inputs.csv` | **Main data file**: all methods, resources and coefficients | ✅ Yes |
-| `data/ui_text.xlsx` | Tooltip texts (on hover), "why is this method disabled?" notes, and each tab's intro paragraph | ✅ Yes |
-| `data/update.py` | Orchestration script: runs both generators below and updates the hash file | ❌ No |
-| `data/generate_model_data.py` | Generates `cost_sliders.json`, `method_groups.json`, `secondary_resources.json` from the CSV | ❌ No |
-| `data/generate_resource_template.py` | Generates `resource_template.xlsx` from the CSV | ❌ No |
-| `data/cost_sliders.json` | Auto-generated. Coefficients used by the app | ❌ No (auto) |
-| `data/method_groups.json` | Auto-generated. CDR method categories | ❌ No (auto) |
-| `data/secondary_resources.json` | Auto-generated. Optional resource assignments | ❌ No (auto) |
-| `data/resource_template.xlsx` | Auto-generated. Excel template for users | ❌ No (auto) |
-| `data/.csv_hash` | Auto-generated. Stores a fingerprint of `inputs.csv` to detect changes on restart | ❌ No (auto) |
-
-> ⚠️ **Never edit the auto-generated files directly**: your changes will be overwritten the next time `update.py` is run.
-
-### Understanding `inputs.csv`
-
-Each row represents **one resource used by one CDR method**, with the following columns:
-
-| Column | Description | Example |
-|--------|-------------|---------|
-| `Implementation` | Name of the CDR method | `Afforestation/reforestation` |
-| `Method group` | Category the method belongs to | `Forestry` |
-| `Resource` | Name of the resource used | `Other land` |
-| `Resource group` | Category the resource belongs to | `Land` |
-| `Type` | Physical type of the resource | `Physical` |
-| `Unit` | Unit of the coefficient (per MtCO₂) | `Mha/MtCO2` |
-| `min` | Minimum coefficient value | `0.002` |
-| `median` | Default (median) coefficient value | `0.094927` |
-| `max` | Maximum coefficient value | `0.384615` |
-| `Is secondary` | Whether this resource is optional for this method | `FALSE` |
-
-> **Primary resources** (`Is secondary = FALSE`) are always active in the model.
-> **Secondary resources** (`Is secondary = TRUE`) are optional: users can toggle them on in the app.
-
-> **Naming convention — "Other" resources:** any resource whose name starts with `Other ` (capital O, followed by a space — e.g. `Other land`, `Other water`) is **hidden from the standard resource display** in Tabs 1 and 3. It still functions normally in the model and remains available as a reference group in the "Add resource" dialog. Use this convention intentionally when you want a resource to be inherited by custom user-defined batches but not shown as a standalone input row.
-
-> **Naming convention — "Other" methods:** any CDR method whose name starts with `Other` receives special treatment in the optimiser. Instead of appearing as a fixed method, the LP automatically creates **one variant per custom resource batch** the user adds that is linked to that method. This is intended for generic CDR pathways where the type of resource is user-defined. If you add a method using this naming convention, make sure it is intentional.
-
-> **Resource group and OR-substitutable resources:** when a CDR method has two or more **primary** resources (`Is secondary = FALSE`) that belong to the same `Resource group`, the optimiser treats them as **interchangeable (OR)**. The method can satisfy its resource need from either one, or any mix of the two, rather than requiring all of them simultaneously. Users will see a hint like *"only one of Other land, Arable land is required"* in the "Why is this method disabled?" panel. This behaviour is automatic: it is triggered purely by two active primary resources sharing the same `Resource group` for the same method. **If you add a resource to an existing group for a method that already has a primary resource in that group, you are creating an OR relationship — make sure this is intentional.** If it is not, create a new resource group instead (see Case 5).
-
 ---
 
 ## Maintenance cases
@@ -344,7 +349,7 @@ You should see `(venv)` at the start of your terminal line.
 
 **When to use:** A CDR method should now also use a resource that is already tracked for other methods (e.g., water is already listed for other methods, and you want to add it to Afforestation/reforestation too). If the resource doesn't exist at all yet, use Case 4 first.
 
-> ⚠️ **This may create an OR relationship:** if the method already has another primary resource (`Is secondary = FALSE`) in the same `Resource group` as the one you're adding, the optimiser will treat the two as interchangeable (the method can run on either one, not both). See [Understanding inputs.csv](#understanding-inputscsv) for details. If this is not the intended behavior, use a different `Resource group` for the new row (Case 5), or mark it `Is secondary = TRUE`.
+> ⚠️ **This may create an OR relationship:** if the method already has another active resource (primary, or secondary and toggled on) in the same `Resource group` as the one you're adding, the optimiser will treat the two as interchangeable (the method can run on either one, not both) as soon as both are active - marking the new row `Is secondary = TRUE` only delays this until a user enables it, it does not prevent it. See [Understanding inputs.csv](#understanding-inputscsv) for details. If this is not the intended behavior, use a different `Resource group` for the new row (Case 5).
 
 **Option 1 - On Hugging Face**
 
@@ -370,7 +375,7 @@ You should see `(venv)` at the start of your terminal line.
 
 **When to use:** A new carbon removal approach needs to be added to the tool.
 
-> ⚠️ **"Other" method naming:** if the method name starts with `Other` (e.g. `Other CDR`), the optimiser treats it specially — it creates one variant per custom resource batch that the user links to this method, instead of running it as a fixed method. Only use this naming if that expansion behavior is intentional. For a standard CDR method with defined resource inputs, use a name that does not start with `Other`.
+> ⚠️ **"Other" method naming:** if the method name starts with `Other` (e.g. `Other CDR`), the optimiser treats it specially: it creates one variant per new resource batch that the user links to this method, instead of running it as a fixed method. Only use this naming if that expansion behavior is intentional. For a standard CDR method with defined resource inputs, use a name that does not start with `Other`.
 
 **Option 1 - On Hugging Face**
 
@@ -400,9 +405,9 @@ You should see `(venv)` at the start of your terminal line.
 
 **When to use:** A resource that doesn't exist yet needs to be used (e.g., a new type of mineral or energy).
 
-> ⚠️ **"Other" resource naming:** if you name the resource starting with `Other ` (capital O + space — e.g. `Other land`, `Other water`), it will be **hidden from the standard resource display** in the app. Users won't see it as a standalone input row, but it will still be available as a reference group when they use the "Add resource" dialog. Only use this prefix if you specifically want the resource to be hidden from direct input.
+> ⚠️ **"Other" resource naming:** if you name the resource starting with `Other ` (capital O + space - e.g. `Other land`, `Other water`), it will be **hidden from the standard resource display** in the app. Users won't see it as a standalone input row, but it will still be available as a reference group when they use the "Add resource" dialog. Only use this prefix if you specifically want the resource to be hidden from direct input.
 
-> ⚠️ **Adding to an existing Resource group may create an OR relationship:** if the method you are adding this resource to already has a primary resource (`Is secondary = FALSE`) in the same `Resource group`, the optimiser will treat the two resources as interchangeable. See [Understanding inputs.csv](#understanding-inputscsv) for details. If this is not the intended behavior, create a new Resource group instead (Case 5).
+> ⚠️ **Adding to an existing Resource group may create an OR relationship:** if the method you are adding this resource to already has another active resource (primary, or secondary and toggled on) in the same `Resource group`, the optimiser will treat the two resources as interchangeable as soon as both are active. See [Understanding inputs.csv](#understanding-inputscsv) for details. If this is not the intended behavior, create a new Resource group instead (Case 5).
 
 **Option 1 - On Hugging Face**
 
@@ -432,7 +437,7 @@ You should see `(venv)` at the start of your terminal line.
 
 ### Case 5 - Add a new resource group (new category)
 
-**When to use:** Your new resource doesn't fit any existing category. Also use this case when the new resource belongs to the same physical category as an existing one but should **not** be treated as interchangeable with it by the optimiser — keeping it in a separate group avoids the automatic OR relationship (see [Understanding inputs.csv](#understanding-inputscsv)).
+**When to use:** Your new resource doesn't fit any existing category. Also use this case when the new resource belongs to the same physical category as an existing one but should **not** be treated as interchangeable with it by the optimiser: keeping it in a separate group avoids the automatic OR relationship (see [Understanding inputs.csv](#understanding-inputscsv)).
 
 **Option 1 - On Hugging Face**
 
@@ -448,7 +453,7 @@ Same steps as Case 4, but write a **new group name** in the `Resource group` col
 
 **When to use:** You want to make a resource optional (user can enable/disable it) or make it always required.
 
-> ⚠️ **Changing a resource from optional to always active may create an OR relationship:** if you set `Is secondary` to `FALSE` for a resource, and the same method already has another primary resource (`Is secondary = FALSE`) in the same `Resource group`, the optimiser will treat the two as interchangeable. See [Understanding inputs.csv](#understanding-inputscsv) for details. If this is not intended, consider moving the resource to a different group (Case 5).
+> ⚠️ **This may create an OR relationship:** the optimiser pools any two resources that are both active (primary, or secondary and toggled on) in the same `Resource group` for the same method - regardless of which way you're changing `Is secondary`. So toggling a secondary resource on (in the app) can create an OR relationship with a sibling in the same group just as much as setting `Is secondary = FALSE` in the CSV can. See [Understanding inputs.csv](#understanding-inputscsv) for details. If this is not intended, consider moving the resource to a different group (Case 5).
 
 **Option 1 - On Hugging Face**
 
@@ -516,28 +521,30 @@ Everything is in the same file, `data/ui_text.xlsx`, across three sheets:
 | Sheet | Columns | Controls |
 |---|---|---|
 | **Resources** | `Resource`, `Tooltip` | Hover tooltip on a resource name |
-| **Methods** | `Method`, `Tooltip`, `Note` | `Tooltip` = hover tooltip on a method name. `Note` = the message shown at the top of that method's "Why is this method disabled?" panel (Method constraints tab) — e.g. explaining that Mineral OAE needs a specific mineral feedstock added as a custom resource. Leave empty for no note. |
-| **Section Intros** | `Tab`, `Text` | The "OBJECTIVE" paragraph shown at the top of a tab. One row per tab — see the `Tab` key table below. |
+| **Methods** | `Method`, `Tooltip`, `Note` | `Tooltip` = hover tooltip on a method name. `Note` = the message shown at the top of that method's "Why is this method disabled?" panel (Method constraints tab), e.g. explaining that Mineral OAE needs a specific mineral feedstock added as a new resource. Leave empty for no note. |
+| **Section Intros** | `Tab`, `Text` | The "OBJECTIVE" paragraph shown at the top of a tab. One row per tab: see the `Tab` key table below. |
 
-> ℹ️ **The "Why is this method disabled?" panel shows two types of text that come from different sources.** The resource hints — e.g. *"Other land: Add as new resource in Resource inputs"* or *"only one of Other land, Arable land is required"* — are **auto-generated** from `inputs.csv` (based on which resources are missing and whether an OR relationship exists). They cannot be changed in `ui_text.xlsx`. The optional free-text `Note` from `ui_text.xlsx` appears above those hints with a lightbulb icon — that is the only part you can edit here. To change the resource hints, you need to change the resource or group structure in `inputs.csv`.
+> ℹ️ **The "Why is this method disabled?" panel shows two types of text that come from different sources.** The resource hints, e.g. *"Other land: Add as new resource in Resource inputs"* or *"only one of Other land, Arable land is required"*, are **auto-generated** from `inputs.csv` (based on which resources are missing and whether an OR relationship exists). They cannot be changed in `ui_text.xlsx`. The optional free-text `Note` from `ui_text.xlsx` appears above those hints with a lightbulb icon: that is the only part you can edit here. To change the resource hints, you need to change the resource or group structure in `inputs.csv`.
 
 > ⚠️ **Exact name match:** the name in column `Resource` or `Method` must match **exactly** the name used in `inputs.csv` (same spelling, same capitalisation). If you rename a method or resource in the CSV, remember to update the name in `ui_text.xlsx` too.
 
 > ⚠️ **`Tab` keys, not tab titles:** the `Tab` column in **Section Intros** uses the internal page name, not the label shown in the sidebar. Use exactly one of:
-> | `Tab` value | Corresponding tab in the app |
-> |---|---|
-> | `tab1_inputs` | Resource inputs |
-> | `tab2_constraints` | Method constraints |
-> | `tab3_coefficients` | Resource coefficients |
-> | `tab4_optimisation` | Portfolio generation |
-> | `tab5_sensitivity` | Sensitivity analysis |
+
+| `Tab` value | Corresponding tab in the app |
+|---|---|
+| `tab1_inputs` | Resource inputs |
+| `tab2_constraints` | Method constraints |
+| `tab3_coefficients` | Resource coefficients |
+| `tab4_optimisation` | Portfolio generation |
+| `tab5_sensitivity` | Sensitivity analysis |
+
 > A row with any other value is simply ignored.
 
-> ⚠️ **These texts contain HTML, not just plain text.** `Tooltip` cells are plain text, but `Note` and `Text` (Section Intros) are rendered as HTML, so you'll see markup like `<strong>bold</strong>`, `<br>` for a line break, and `<li>...</li>` for a bullet-style line. Keep these tags when editing around them — deleting a `<` or `>` by accident will make the raw tag appear as text on the page instead of being applied as formatting. You can add more of the same tags (`<strong>`, `<br>`, `<li>`) but avoid pasting anything more advanced (scripts, styles, other tags) since it is not sanitised before display.
+> ⚠️ **These texts contain HTML, not just plain text.** `Tooltip` cells are plain text, but `Note` and `Text` (Section Intros) are rendered as HTML, so you'll see markup like `<strong>bold</strong>`, `<br>` for a line break, and `<li>...</li>` for a bullet-style line. Keep these tags when editing around them: deleting a `<` or `>` by accident will make the raw tag appear as text on the page instead of being applied as formatting. You can add more of the same tags (`<strong>`, `<br>`, `<li>`) but avoid pasting anything more advanced (scripts, styles, other tags) since it is not sanitised before display.
 
 > ⚠️ **`tab2_constraints`'s text has a placeholder:** its `Text` cell contains `{CO2_UNIT}`, which the app replaces with the actual CO₂ unit (e.g. `MtCO₂`) when displayed. Keep the `{CO2_UNIT}` placeholder (braces included) if you want that value to appear; removing it just removes the unit from the sentence, it won't break anything.
 
-> If a cell is left empty, or a sheet/row is missing entirely, that piece of text is simply skipped (no tooltip / no note / no intro paragraph) — nothing crashes.
+> If a cell is left empty, or a sheet/row is missing entirely, that piece of text is simply skipped (no tooltip / no note / no intro paragraph): nothing crashes.
 
 **Option 1 - On Hugging Face**
 
@@ -570,7 +577,7 @@ The `.xlsx` file cannot be edited inline on Hugging Face. Instead:
 
 **When to use:** A CDR method or resource is no longer relevant and should be removed from the tool entirely.
 
-> ⚠️ If users have saved scenario files (`.xlsx` or `.zip`) that reference the removed method or resource, those fields will be silently ignored on load — no error is raised, but the data will be missing from the restored session.
+> ⚠️ If users have saved scenario files (`.xlsx` or `.zip`) that reference the removed method or resource, those fields will be silently ignored on load: no error is raised, but the data will be missing from the restored session.
 
 **Option 1 - On Hugging Face**
 
@@ -648,12 +655,12 @@ Option 2 (local):
 
 Option 1 (Hugging Face direct):
 - [ ] Downloaded, edited, and re-uploaded `ui_text.xlsx` on Hugging Face
-- [ ] Space has restarted (no update script runs for this file — `Data files updated successfully.` will **not** appear in the logs; this is normal)
+- [ ] Space has restarted (no update script runs for this file: `Data files updated successfully.` will **not** appear in the logs; this is normal)
 - [ ] Verified the updated text appears correctly in the app
 
 Option 2 (local):
 - [ ] Saved `data/ui_text.xlsx`
-- [ ] Restarted the app (`Ctrl+C` then `streamlit run app.py`) — no need to run `update.py`
+- [ ] Restarted the app (`Ctrl+C` then `streamlit run app.py`): no need to run `update.py`
 - [ ] Verified the updated text appears correctly in the app
 - [ ] Committed `data/ui_text.xlsx` and pushed