feat(studio): introduce optional in-engine Studio tools for enhanced workflow

This commit adds a new feature to the Vulkan renderer, enabling optional in-engine Studio panels (session strip and command strip) controlled by the `r_studio_tools` variable. These tools provide lightweight workflow enhancements reminiscent of classic id Studio, allowing for quick access to session information and command execution. Documentation has been added to describe the usage and functionality of these tools, improving the overall development experience within the engine.

Author: timfox

AGENTS.md

@@ -4,7 +4,7 @@
 
 ### Overview
 
-This is an **idTech3 engine fork** - a C/C++ game engine based on Quake III Arena with Vulkan 1.4 + RTX rendering, PBR, audio codecs (Opus/FLAC/WebM/MP3), Lua/Duktape scripting, and ImGui debug UI. It produces a client (`idtech3`), dedicated server (`idtech3_server`), and renderer plugins (`idtech3_opengl.so`, `idtech3_vulkan.so`).
+This is an **idTech3 engine fork** - a C/C++ game engine based on Quake III Arena with Vulkan 1.4 + RTX rendering, PBR, audio codecs (Opus/FLAC/WebM/MP3), Lua/Duktape scripting, and ImGui debug UI (optional **Studio** session + command strips via `r_studio_tools`; see `docs/IN_ENGINE_STUDIO_TOOLS.md`). It produces a client (`idtech3`), dedicated server (`idtech3_server`), and renderer plugins (`idtech3_opengl.so`, `idtech3_vulkan.so`).
 
 ### Building
 

docs/AMPL.md

@@ -0,0 +1,91 @@
+# AMPL (A Mathematical Programming Language)
+
+**AMPL** is an algebraic modeling language for describing and solving large-scale optimization and scheduling problems. Syntax is close to conventional mathematical notation; models are typically separated from data (`.mod` / `.dat` / `.run`).
+
+**Official site:** [https://www.ampl.com](https://www.ampl.com)
+
+**Not part of this engine:** idTech3 does not embed or depend on AMPL. This page is a **standalone reference** only.
+
+## Origins and license
+
+Designed by Robert Fourer, David M. Gay, and Brian W. Kernighan at Bell Labs; first appeared in 1985. The **translator** is proprietary (AMPL Optimization LLC); the **AMPL Solver Library (ASL)** for reading `.nl` files and automatic differentiation is open source. **AMPL/MP** is an open-source library for building certain solver classes.
+
+## Problem classes (examples)
+
+Linear and mixed-integer programming, quadratic and mixed-integer QP, nonlinear and MINLP, second-order cone programming, complementarity (MPECs), constraint programming, global optimization, and others depending on the linked solver.
+
+## Solver interaction
+
+AMPL normally invokes a solver in a **separate process** via a well-defined **`.nl`** interface, which isolates solver crashes from the interpreter and allows mixed 32/64-bit translator/solver combinations.
+
+## Sample model (Dantzig transportation)
+
+Classic linear program: minimize freight cost subject to plant capacity and market demand.
+
+```ampl
+set Plants;
+set Markets;
+
+param Capacity{p in Plants};
+param Demand{m in Markets};
+param Distance{Plants, Markets};
+param Freight;
+
+param TransportCost{p in Plants, m in Markets} :=
+    Freight * Distance[p, m] / 1000;
+
+var shipment{Plants, Markets} >= 0;
+
+minimize cost:
+    sum{p in Plants, m in Markets} TransportCost[p, m] * shipment[p, m];
+
+s.t. supply{p in Plants}:
+    sum{m in Markets} shipment[p, m] <= Capacity[p];
+
+s.t. demand{m in Markets}:
+    sum{p in Plants} shipment[p, m] >= Demand[m];
+
+data;
+
+set Plants := seattle san-diego;
+set Markets := new-york chicago topeka;
+
+param Capacity :=
+    seattle   350
+    san-diego 600;
+
+param Demand :=
+    new-york 325
+    chicago  300
+    topeka   275;
+
+param Distance : new-york chicago topeka :=
+    seattle        2.5      1.7     1.8
+    san-diego      2.5      1.8     1.4;
+
+param Freight := 90;
+```
+
+## Solvers (partial)
+
+AMPL supports many solvers, including open-source and commercial examples: **CBC**, **CLP**, **IPOPT**, **SCIP**, **HiGHS**, **CPLEX**, **Gurobi**, **MOSEK**, **KNITRO**, **SNOPT**, **MINOS**, **Bonmin**, **Couenne**, **Gecode**, **JaCoP**, and others. See the current list at [Solvers – AMPL](https://ampl.com/products/solvers/).
+
+## APIs and tooling
+
+Official APIs exist for **Python**, **R**, **C++**, **C#**, **MATLAB**, and **Java**. NEOS and similar services accept AMPL models remotely.
+
+## See also
+
+- [JuMP](https://jump.dev/) (Julia)
+- [Pyomo](http://www.pyomo.org/) (Python)
+- [GNU MathProg](https://www.gnu.org/software/glpk/) (GLPK subset of AMPL)
+- [NEOS Server](https://neos-server.org/)
+
+## References
+
+- Fourer, Gay, Kernighan, *AMPL: A Modeling Language for Mathematical Programming* (2003), Duxbury/Brooks-Cole. ISBN 978-0-534-38809-6. [Online book](https://ampl.com/resources/the-ampl-book/)
+- Fourer, Gay, Kernighan, “A Modeling Language for Mathematical Programming,” *Management Science* 36(5), 1990. [DOI 10.1287/mnsc.36.5.519](https://doi.org/10.1287/mnsc.36.5.519)
+
+---
+
+*Summary incorporates material from the Wikipedia article [“AMPL”](https://en.wikipedia.org/wiki/AMPL) (retrieved 2026); [Creative Commons Attribution-ShareAlike 4.0 International License](https://creativecommons.org/licenses/by-sa/4.0/).*

docs/Clipper.md

@@ -0,0 +1,66 @@
+# Clipper (xBase programming language)
+
+**Clipper** (Nantucket Clipper, later **CA-Clipper**) is an **xBase** compiler and language: a dBase III–style dialect compiled to DOS executables, aimed mainly at database-centric business applications (inventory, CRM, banking/insurance front-ends, etc.). It is **not** the same thing as polygon-clipping libraries often named “Clipper” in geometry (e.g. Angus Johnson’s library).
+
+**Not part of this engine:** idTech3 does not embed, compile, or run Clipper code. This page is a **standalone reference** only.
+
+## Origins and license
+
+Developed by **Nantucket Corporation** (from 1984); sold to **Computer Associates** in 1992; product renamed **CA-Clipper**. Final CA release commonly cited: **CA Clipper 5.3b** (May 1997). Original platform: **DOS**; translator/toolchain was **proprietary**.
+
+Compared to Ashton-Tate **dBASE III**, a major selling point was **compilation** to standalone programs instead of shipping an interpreted runtime for every line. Over time the language gained C/Pascal–like constructs, **object-oriented** features, and **code blocks** (mixing dBase-style macros / evaluation with function-pointer–like behavior). Nantucket’s **Aspen** line later fed **CA-Visual Objects** for Windows native code.
+
+One classic **dBase** feature **not** in Clipper was the interactive **dot-prompt** command environment.
+
+## Successors and clones
+
+Active or historical implementations include **Harbour** and **xHarbour** (GPL and related), **XBase++** (Alaska Software), **FlagShip**, and others—often portable across DOS, Windows, Linux, Unix, and macOS, with extended runtimes and **RDD** (replaceable database drivers) for DBF/CDX/FoxPro-style formats, SQL bridges, etc.
+
+**CA Clipper Tools** (CA library) became a **de facto** extension standard among many clones.
+
+## Hello world
+
+```clipper
+Procedure Main       // Or Proc Main
+    ? "Hello World!"
+Return               // Or Retu
+```
+
+## Simple data-entry pattern (illustrative)
+
+Classic `@ ... SAY ... GET ... READ` style (fragment; not a full program):
+
+```clipper
+USE Customer SHARED NEW
+clear
+@  1, 0 SAY "CustNum" GET Customer->CustNum PICT "999999" VALID Customer->CustNum > 0
+@  3, 0 SAY "Contact" GET Customer->Contact VALID !empty(Customer->Contact)
+@  4, 0 SAY "Address" GET Customer->Address
+READ
+```
+
+## Version history (selected)
+
+| Era | Examples |
+|-----|----------|
+| Nantucket “seasonal” | Winter ’84 (1985) … Summer ’87 (1987) |
+| Clipper 5.x (Nantucket) | 5.00 (1990), 5.01 (1991), 5.01 Rev.129 (1992) |
+| CA-Clipper 5.x | 5.20 (1993) … 5.3b (1997) |
+
+Full release tables appear in historical vendor documentation and archives such as [The Oasis](https://harbour.github.io/the-oasis/docs/) (Clipper/xBase mirror; legacy site [the-oasis.net](http://www.the-oasis.net/)).
+
+## Community / archives
+
+- Usenet (historical): `comp.lang.clipper`, `comp.lang.clipper.visual-objects`
+- **Harbour Project:** [https://harbour.github.io/](https://harbour.github.io/)
+- CA/Grafx-era site is largely gone; last useful snapshots are often in the [Wayback Machine](https://web.archive.org/web/*/http://www.grafxsoft.com/clipper.htm)
+
+## See also
+
+- [dBase](https://en.wikipedia.org/wiki/DBase) — original interpreted xBase family
+- [Harbour](https://en.wikipedia.org/wiki/Harbour_(software)) — open-source Clipper-like compiler
+- [Visual FoxPro](https://en.wikipedia.org/wiki/Visual_FoxPro) / **FoxPro** — related xBase lineage on Windows
+
+---
+
+*Summary incorporates material from the Wikipedia article [“Clipper (programming language)”](https://en.wikipedia.org/wiki/Clipper_(programming_language)) (retrieved 2026); [Creative Commons Attribution-ShareAlike 4.0 International License](https://creativecommons.org/licenses/by-sa/4.0/).*

docs/EDITOR_BRIDGE.md

@@ -3,6 +3,8 @@
 Entity definitions and key/value conventions shared between the
 id Tech 3 engine and idTech3Radiant editor for feature parity.
 
+For optional in-engine **Studio** panels (session strip + command strip) that surface this document at runtime, see **[IN_ENGINE_STUDIO_TOOLS.md](IN_ENGINE_STUDIO_TOOLS.md)** (`r_studio_tools`).
+
 ## Entity Key/Value Reference
 
 ### Volumetric Fog (`worldspawn` keys)

docs/IN_ENGINE_STUDIO_TOOLS.md

@@ -0,0 +1,40 @@
+# In-engine tools (id Studio–inspired)
+
+The Vulkan + **Dear ImGui** overlay (`r_imgui`, toggle **F11** / `toggle_imgui`) already provides a docked **inspector**: PostFX, volumetrics, physics, profiler, placeholder Objects/Inspector/Shader/Viewport panels.
+
+This document describes the optional **Studio** layer: lightweight, in-game workflow helpers reminiscent of classic **id Studio** (session strip + command strip), not a full map editor.
+
+## Toggle
+
+| Cvar | Default | Meaning |
+|------|---------|---------|
+| `r_imgui` | `1` | Master switch for the ImGui overlay (inspector CPU work). |
+| `r_studio_tools` | `0` | When `1`, enables **Studio** menu, **Studio / Session**, and **Studio / Console** panels. |
+
+On startup with `r_studio_tools 1`, the Session and Console panels open automatically (with `r_imgui 1`). Enabling **Studio tools** from the inspector **Developer** menu at runtime also opens both panels.
+
+Startup logs:
+
+- `[VK][imgui] debug inspector r_imgui=…`
+- `[VK][studio] r_studio_tools=…`
+
+## Studio / Session
+
+Read-only view of common session cvars (`mapname`, `fs_game`, `fs_basegame`, `sv_hostname`) plus **Quick commands** (`map_restart`, `disconnect`, `vid_restart`) and a small **dev** row (`noclip`, `god`, `notarget`) routed through the normal command buffer.
+
+## Studio / Console
+
+Single-line command entry (Enter or **Run**) that appends to the main **command buffer**—same as the drop-down console. A **local history** (last 48 lines) is shown above the input; it is **not** a mirror of the full engine log.
+
+## Editor parity
+
+Entity keys and conventions shared with **idTech3Radiant** are documented in **[EDITOR_BRIDGE.md](EDITOR_BRIDGE.md)**.
+
+## Future work (non-goals for this pass)
+
+- Live game view texture in the Viewport panel  
+- Full scene graph / property grid wired to entities  
+- Shader live hot-reload beyond `r_reloadShaders` / `vid_restart`  
+- Two-way IPC with the external editor  
+
+Those remain roadmap items; the Studio layer is intentionally small and safe to ship disabled by default.