docs: remove AeroSim drawio copy

docs/projects/aerosim.md

@@ -82,16 +82,13 @@ All use default branch `test` and are primary for AeroSim work:
 - `development-scripts--aerosim`
 - `devsecops-ci-cd-gitea--aerosim`
 - `documentation-docusaurus--aerosim`
-- `drawio-main--aerosim`
 - `template-engine-copier--aerosim`
 - `corp-v1-channel-general--aerosim`
 - `corp-v1-channel-architecture--aerosim`
 - `corp-v1-channel-delivery--aerosim`
 - `corp-v1-channel-releases--aerosim`
 
-Each repository records the central source branch and commit in `ADOPTION.md`.
-
-Current steering policy defaults to seven adopted engineering skills plus four channel skills and references global `drawio-main`. AeroSim retains the historical `drawio-main--aerosim` repository pending an explicit team decision to retain it as an approved exception or retire it; no repository was deleted during alignment.
+Each repository records the central source branch and commit in `ADOPTION.md`. Architecture and documentation work reference the global [`drawio-main`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/drawio-main) skill.
 
 ## Verification
 
@@ -101,12 +98,11 @@ Current steering policy defaults to seven adopted engineering skills plus four c
 - Application tests: four passed across web, API, and shared flight core.
 - Application and documentation production builds: passed.
 - Project-team access to both project repositories: verified.
-- Skills-team organization contains all twelve adopted skill repositories on default branch `test`: verified.
+- Skills-team organization contains all eleven adopted skill repositories on default branch `test`: verified.
 - Harbor organization variable names and secret name `HL_V1_HARBOR_ROBOT_GITEA_ACTIONS_V1_SECRET`: verified without reading secret values.
 - Product lifecycle, solution traceability, and release-readiness registries now exist in project documentation. No Epic or Feature was assigned human approval retrospectively.
 - Both application and documentation `test` branches currently have no branch-protection rule.
 
 ## Outstanding governance decisions
 
-1. A human team member must decide whether to retain `drawio-main--aerosim` as an explicitly approved project copy or use only global `drawio-main` and retire the copy through the normal reviewed process.
-2. A human team member must approve the desired branch-protection policy for both project `test` branches before protection is configured. No protection was added autonomously because required approvals and merge semantics are a governance decision.
+A human team member must approve the desired branch-protection policy for both project `test` branches before protection is configured. No protection was added autonomously because required approvals and merge semantics are a governance decision.