From 9d289a561b6fc7d7b2823f6ea976f0fd3693283c Mon Sep 17 00:00:00 2001
From: jcant0n <javiercantonferrero@gmail.com>
Date: Sun, 2 Aug 2026 16:12:25 +0200
Subject: [PATCH] chore: consume the bindings toolbox and declare the upstream
 manifest

The last repository in the fleet still pointing at evergine-standards.
Completes the migration.

Adds binding.yml recording that renderdoc_app.h comes from
baldurk/renderdoc's v1.x branch. Tracking a branch rather than a tag is
deliberate here and the manifest says why: the RenderDoc API header is
an in-application interface that only grows additively, so it does not
carry the struct-layout hazard that makes pinning necessary elsewhere in
the fleet.

This repository was held back earlier because two Sync standards runs
have been stuck in queued since 1 August. They still are, twenty-seven
hours on, past the point where GitHub's own limit should have cancelled
them. Migrating anyway is safe: sync-standards.yml is untouched, and
OpenGL.NET was in the same state and migrated without incident.
---
 .github/workflows/CD.yml |  2 +-
 .github/workflows/CI.yml |  2 +-
 binding.yml              | 30 ++++++++++++++++++++++++++++++
 3 files changed, 32 insertions(+), 2 deletions(-)
 create mode 100644 binding.yml

diff --git a/.github/workflows/CD.yml b/.github/workflows/CD.yml
index 1ef425b..08ac25b 100644
--- a/.github/workflows/CD.yml
+++ b/.github/workflows/CD.yml
@@ -17,7 +17,7 @@ on:
 jobs:
   cd:
     if: github.event_name != 'schedule' || github.ref_name == github.event.repository.default_branch
-    uses: EvergineTeam/evergine-standards/.github/workflows/binding-simple-cd.yml@v2
+    uses: EvergineTeam/Evergine.Bindings/.github/workflows/binding-simple-cd.yml@v1
     with:
       generator-project: "RenderDocGen/RenderDocGen/RenderDocGen.csproj"  # Path to your generator .csproj
       generator-name: "RenderDoc"                # Name of your generator executable
diff --git a/.github/workflows/CI.yml b/.github/workflows/CI.yml
index 0f8e1a6..e3b9f51 100644
--- a/.github/workflows/CI.yml
+++ b/.github/workflows/CI.yml
@@ -20,7 +20,7 @@ on:
 
 jobs:
   ci:
-    uses: EvergineTeam/evergine-standards/.github/workflows/binding-common-ci.yml@v2
+    uses: EvergineTeam/Evergine.Bindings/.github/workflows/binding-common-ci.yml@v1
     with:
       generator-project: "RenderDocGen/RenderDocGen/RenderDocGen.csproj"  # Path to your generator .csproj
       generator-name: "RenderDoc"                # Name of your generator executable
diff --git a/binding.yml b/binding.yml
new file mode 100644
index 0000000..32ca6f7
--- /dev/null
+++ b/binding.yml
@@ -0,0 +1,30 @@
+# Binding manifest — see https://github.com/EvergineTeam/Evergine.Bindings
+# Schema: https://github.com/EvergineTeam/Evergine.Bindings/blob/main/binding.schema.json
+toolbox: 1.0.0
+
+package:
+  id: Evergine.Bindings.RenderDoc
+  project: RenderDocGen/Evergine.Bindings.RenderDoc/Evergine.Bindings.RenderDoc.csproj
+  target-framework: net10.0
+  runtime-identifier: win-x64
+
+upstream:
+  kind: git-tree
+  language: cpp
+  project: https://github.com/baldurk/renderdoc
+  version-from: git-release
+  sources:
+    # `v1.x` is RenderDoc's long-lived release branch, not a tag. The API header is an
+    # in-application interface that only grows additively, so tracking the branch is
+    # safe here in a way it would not be for a struct-layout header.
+    - repo: baldurk/renderdoc
+      ref: v1.x
+      remote-path: renderdoc/api/app/renderdoc_app.h
+      path: RenderDocGen/RenderDocGen/Headers/renderdoc_app.h
+      format: c-header
+
+generator:
+  project: RenderDocGen/RenderDocGen/RenderDocGen.csproj
+  name: RenderDoc
+  output:
+    - RenderDocGen/Evergine.Bindings.RenderDoc/Generated