From e0b14f72d62d4a98825a1d55f812eadf3eb89a70 Mon Sep 17 00:00:00 2001
From: Benjamin Alsbury-Nealy <benjamin@silicolabs.ca>
Date: Thu, 14 May 2026 14:10:37 -0400
Subject: [PATCH] Tidy stale studio-web comment on the IO csproj

The original net8.0-only justification cited a planned studio-web WASM
consumer at net10.0. That plan was dropped; Studio remains the primary
client. The new comment reflects current reality: the IO library is
authoring/build-time only, and the Unity package consumes its export
outputs, not its types.

No build or behaviour change.
---
 src/OpenApparatus.IO/OpenApparatus.IO.csproj | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/src/OpenApparatus.IO/OpenApparatus.IO.csproj b/src/OpenApparatus.IO/OpenApparatus.IO.csproj
index 4ead8c9..d32c691 100644
--- a/src/OpenApparatus.IO/OpenApparatus.IO.csproj
+++ b/src/OpenApparatus.IO/OpenApparatus.IO.csproj
@@ -1,10 +1,9 @@
 <Project Sdk="Microsoft.NET.Sdk">
 
   <PropertyGroup>
-    <!-- net8.0 covers both consumers (desktop Studio + studio-web WASM at net10.0,
-         which forward-resolves net8.0 assets). The IO lib isn't a Unity-runtime
-         concern — exports are a build-time / authoring-time activity, and Unity
-         has its own OBJ/glTF importers. So no netstandard2.1 target needed. -->
+    <!-- net8.0 targets the desktop Studio app. The IO lib is authoring/build-time
+         only; the Unity package consumes its export *outputs*, not its types, and
+         doesn't need this DLL at runtime. -->
     <TargetFramework>net8.0</TargetFramework>
     <LangVersion>12</LangVersion>
     <ImplicitUsings>enable</ImplicitUsings>