llms.txt: PBR option served by the v2 LoRA; name materials for metal

README.md

@@ -71,6 +71,10 @@ Terrain and ground: `POST /api/terrain {"upload_id": "up_...", "prompt": "an alp
 `files.bundle_zip` (splat maps, seamless detail textures, `blender_terrain.py`, `three_terrain.js`). See the
 "Terrain and ground" section of /llms.txt.
 
+PBR materials: add `"pbr": true` to a texture job (or POST /api/jobs/{id}/pbr afterwards) for
+`files.textured_pbr_glb` with a de-lit base colour and a metallicRoughness texture (roughness, metallic maps from a
+LoRA on Qwen-Image-Edit-2511, run on the caller's ZeroGPU quota).
+
 MCP client configuration:
 ```json
 {"mcpServers": {"projtex": {"type": "http", "url": "https://townbox-projection-texturing.hf.space/mcp",

app/llms.txt

@@ -73,8 +73,8 @@ default backend qwen-turbo, about 30 s with qwen-space).
   has a de-lit base colour and a glTF metallicRoughness texture (G roughness, B metallic) on every material, so the
   model reacts to your scene's light (varnished wood and porcelain catch highlights, brass and chrome reflect);
   files.albedo_pbr, roughness, metallic, metallic_roughness are the maps for your own material. Material names and
-  part_prompts settle metal or not where they say it ("Brass", "walnut veneer", "gloss paint"): glossy paint can
-  otherwise come out metallic. pbr.metallic_fraction and pbr.roughness_mean in the status summarise the result.
+  part_prompts settle metal or not where they say it ("Brass", "walnut veneer", "gloss paint"), so name your
+  materials: metal is the hardest map to read from a picture. pbr.metallic_fraction and pbr.roughness_mean in the status summarise the result.
 - Game-ready single asset: "single_mesh": true returns one object with one material (metallic/roughness are the
   area-weighted means of yours); POST /api/jobs/{id}/bake {"single_mesh": true} switches an existing job.
 - Prepare meshes like this: one GLB with all parts (several objects and materials are fine), modifiers applied,