ci: harden 05.1/07.1 against redundant push-triggered reruns [skip ci]

Two defense-in-depth follow-ups to the write-lock burst fix:

- 05.1 README Sync: add data/inventory.sql to paths-ignore, alongside the
  already-ignored data/inventory.yaml. It is a generated artifact, never
  hand-edited, so a push touching it should not wake the README sync.

- 07.1 PR Guardian: add [skip ci] to its auto-correction commit. Guardian
  pushes the fix back to the PR head branch, whose synchronize event otherwise
  re-runs Guardian (Gemini calls) and the markdown linter on Guardian's own
  cosmetic commit - exactly the CI minutes the workflow's concurrency comment
  says it wants to save. Base branches are unprotected, so no required check is
  stranded; human commits (no [skip ci]) still trigger Guardian normally.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

.github/workflows/05.1.readme_sync.yml

@@ -7,6 +7,7 @@ on:
     paths-ignore:
       - 'README.md'
       - 'data/inventory.yaml'
+      - 'data/inventory.sql'
       - 'docs/**'
       - 'v2-docs/**'
   workflow_dispatch: # Permite ejecución manual desde la pestaña Actions

.github/workflows/07.1.pr_guardian.yml

@@ -64,7 +64,7 @@ jobs:
           # caused a perpetual cosmetic develop<->master drift (see pr_guardian.py).
           git add docs/ README.md data/inventory.yaml data/inventory.sql src/memory/
           if ! git diff --cached --quiet; then
-            git commit -m "style(cleaner): auto-correcting formatting & URL normalization"
+            git commit -m "style(cleaner): auto-correcting formatting & URL normalization [skip ci]"
             git push origin HEAD:${{ github.event.pull_request.head.ref }} || echo "⚠️ Push failed (likely fork permission limit)."
           else
             echo "No formatting changes to commit."