Use an obvious dummy token in Seambot tests

[coderabbitai]

Replace the credential-shaped GitHub installation token fixture with ghs_test-token so CI security and governance checks do not mistake test data for a secret.

Validation: git diff --check passed; tests were not run.

View coding task

[coderabbitai]

Important

Review skipped

This PR was authored by the user configured for CodeRabbit reviews. CodeRabbit does not review PRs authored by this user. It's recommended to use a dedicated user account to post CodeRabbit review feedback.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Essentials

Run ID: e1a96844-3152-48af-816c-04047fc87252

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
36740420	Triggered	Generic Password	b84e2f0	bots/cipherbot/src/analyzers/infra.rs	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[hyperpolymath]

🔴 4 FAILING CHECKS - NEEDS FIXING

✅ CodeRabbit PR: Use an obvious dummy token in Seambot tests
✅ Commit status: success (GitHub status API)
❌ Mergeable state: unstable (due to 4 failing check runs)

---

📋 FAILING CHECKS (All Must Pass)

1. governance / Validate Hypatia Baseline

• 🔗 View details
• 📌 Issue: Baseline validation failing - likely missing or incorrect metadata

2. Validate A2ML manifests

• 🔗 View details
• 📌 Issue: A2ML manifest validation failing - check .a2ml files for syntax/structure errors

3. build · test · clippy (robot-repo-automaton)

• 🔗 View details
• 📌 Issue: Rust build/test/clippy failing in robot-repo-automaton directory

4. GitGuardian Security Checks

• 🔗 View details
• 📌 Issue: Security scan detected secrets or sensitive data

---

🎯 ROOT CAUSE ANALYSIS

The PR title suggests it's about "Use an obvious dummy token in Seambot tests" - this is likely related to the GitGuardian failure. The other failures (Hypatia Baseline, A2ML manifests, Rust CI) may be pre-existing or caused by the token change.

🛠️ RECOMMENDED ACTIONS

1. Check GitGuardian dashboard for specific secret detection details

2. Verify the dummy token is actually "obvious" and not a real token

3. Run governance checks locally to see exact validation errors:

4. Fix all 4 checks before re-attempting merge

⚠️ WILL NOT MERGE until all checks pass. This is a hard blocker.

📌 Priority: HIGH - Blocking merge queue

[hyperpolymath]

DEEP ANALYSIS: PR changes ONLY bots/seambot/tests/github_integration.rs line 154: token from ghs_xxxxx... to ghs_test-token. GitGuardian likely still flagging. Validate Hypatia Baseline probably checking for realistic tokens. Validate A2ML manifests may be pre-existing. build/clippy in robot-repo-automaton is UNRELATED to this change. QUICK FIX: amend to use even more obvious token like TEST_TOKEN_PLACEHOLDER then force-push and re-trigger checks.