fix(construct): resolve dangling skill cross-references in spacecraft-ada-guidelines

The skill pointed to two skills that do not exist in the repo:
- spacecraft-safety-critical-rust → repointed to the real spacecraft-rust-guidelines
  (the Rust side of the same high-assurance posture).
- spacecraft-power-of-ten → reframed as the NASA/JPL *Power of Ten* rules (a named
  ruleset, not a skill) so it no longer reads as a skill pointer.

Touched SKILL.md (§Build, §References), references/ATTRIBUTION.md, and
references/AdaCore_Safe_Secure_Rules.md. Repo-wide sweep confirms no other dangling
spacecraft-* skill references remain (spacecraft-docs / spacecraft-native are a RAG
collection name and a JSON enum value, not skill refs). Bundles rebuilt; drift clean.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: UnbreakableMJ

spacecraft-ada-guidelines.skill

@@ -109,7 +109,7 @@ Ada catches at compile/proof time what other languages catch at runtime — *if*
 - **Prove in CI, gated:**
   - `gnatprove -P <proj>.gpr --mode=all --level=2 --report=fail` as the default gate; raise `--level` (0..4) and add `--prover=z3,cvc5,altergo`, `--timeout`/`--steps` for stubborn checks.
   - Treat any unproved check as a build failure for units claiming Silver+.
-- **Coding standard + format:** enforce with `gnatcheck` (rules file in repo) and format with `gnatpp`; gather `gnatmetric` for complexity budgets. Cross-apply `spacecraft-power-of-ten` limits (bounded loops, no recursion in critical code, restricted scope).
+- **Coding standard + format:** enforce with `gnatcheck` (rules file in repo) and format with `gnatpp`; gather `gnatmetric` for complexity budgets. Cross-apply the NASA/JPL *Power of Ten* rules (bounded loops, no recursion in critical code, restricted scope).
 - **SPDX header on every file** (Ada comment syntax):
   ```ada
   -- SPDX-FileCopyrightText: Copyright (C) 2026 Mohamed Hammad & Spacecraft Software
@@ -149,6 +149,6 @@ Ada catches at compile/proof time what other languages catch at runtime — *if*
 - **Rule catalogue (cite IDs from here):** `references/AdaCore_Safe_Secure_Rules.md` — all 41 DYN/RCL/CON/RPP/EXU/OOP/SWE rules with Levels and standards mappings.
 - Extended patterns, full worked examples, and a proof-debugging guide: `references/Spacecraft_Ada_SPARK_Guidelines.md`
 - Conceptual sources, the source PDF, and the SPARK Reference Manual: `CREDITS.md` and `references/ATTRIBUTION.md`
-- Related skills: `spacecraft-power-of-ten` (loop/recursion/scope budgets), `spacecraft-safety-critical-rust` (Rust side of the same assurance posture), `spacecraft-standard` (cross-cutting compliance).
+- Related skills: `spacecraft-rust-guidelines` (the Rust side of the same high-assurance posture), `spacecraft-standard` (cross-cutting compliance); cross-apply the NASA/JPL *Power of Ten* rules (loop/recursion/scope budgets).
 
 When the user provides Ada/SPARK code for review or asks to write a high-assurance unit, immediately apply the rules above: strengthen the types, add and discharge contracts, declare the assurance target, and produce code that passes `gnatprove` at that level. Cite the exact rule or unproved check in any feedback. Prioritize machine-checked correctness and AoRTE above all else.

spacecraft-ada-guidelines.zip

@@ -19,8 +19,8 @@ themselves trigger a root `CREDITS.md` (§15.3 carve-out). AdaCore's adoption-le
 methodology is credited here as the conceptual basis for the assurance ladder.
 
 Cross-references within the Spacecraft skill set:
-- `spacecraft-power-of-ten` — bounded-loop / no-recursion / restricted-scope budgets reused here.
-- `spacecraft-safety-critical-rust` — the Rust side of the same high-assurance posture.
+- The NASA/JPL *Power of Ten* rules — bounded-loop / no-recursion / restricted-scope budgets reused here.
+- `spacecraft-rust-guidelines` — the Rust side of the same high-assurance posture.
 - `spacecraft-standard` — cross-cutting compliance (licensing, SPDX, ISO 8601, naming).
 
 — Spacecraft Software, 2026

spacecraft-ada-guidelines/SKILL.md

@@ -104,7 +104,7 @@ Choose the *most restrictive policy the design allows* (OOP01 is strictest).
 
 ## Spacecraft cross-references
 
-- **DYN02-04, RPP12, RPP14** reinforce `spacecraft-power-of-ten` (no heap, no recursion, bounded everything, no magic numbers).
+- **DYN02-04, RPP12, RPP14** reinforce the NASA/JPL *Power of Ten* rules (no heap, no recursion, bounded everything, no magic numbers).
 - **EXU04 + SWE01** are the formal-verification spine; they map directly to the assurance ladder in `SKILL.md` (Silver = AoRTE proven).
 - **CON01/CON02/CON03** match the skill's Ravenscar/Jorvik + protected-object concurrency rules.