chore(git): remove orama attribution-guard scripts from periscope

Author: diazMelgarejo

.cursor/rules/banned-attribution-local.mdc

@@ -356,19 +356,11 @@ GitHub Actions service container in `.github/workflows/ci.yml`.
 
 ## Cursor Cloud: git commits
 
-Run on cloud VM boot:
-
-```bash
-bash scripts/git/apply-attribution-guard-all-repos.sh
-```
-
-Hook-free commit when needed:
-
-```bash
-bash scripts/git/commit-clean.sh -m "type(scope): summary"
-```
-
-See orama-system `docs/wiki/09-cursor-cloud-commit-attribution.md` (canonical).
+periscope is **excluded** from orama attribution-guard scripts (`commit-clean.sh`,
+`sync-attribution-guard-scripts.sh`, etc.). Use standard `git commit` per the Git
+Rules section above. PT and AlphaClaw in the same cloud workspace run
+`bash ../orama-system/scripts/git/apply-attribution-guard-all-repos.sh` from their
+repos (periscope is skipped automatically).
 
 **Fork policy:** integration branch is `merged`. Open agent PRs from
 `cursor/*` branches → `merged` (never → `main`).