Skip to content

Remove hosted test workflows: testing runs on the Spark only - #25

Merged
drakestapleton merged 1 commit into
mainfrom
chore/no-hosted-tests
Oct 18, 2026
Merged

drakestapleton merged 1 commit into
mainfrom
chore/no-hosted-tests

Conversation

@drakestapleton

Copy link
Copy Markdown
Contributor

Why

Drake, 2026-10-18: all testing runs on the local network; nothing is tested on GitHub-hosted runners. The 11 core repositories were switched today to the single AIEN Verification check, which only verifies the bundle the Spark signs. This PR does the same cleanup for this repository.

What changes

  • aienos.com: pages.yml still builds and deploys the site (hourly and on push to main) but no longer runs cargo test and no longer runs on pull requests. automerge.yml is removed (a hand-run build, test and merge that bypassed review).
  • atlas: no-python.yml removed. scripts/check-no-python.sh stays and can run locally.
  • mobhub / open-humanity: sovereign-reviewer.yml removed. Besides running cargo build and cargo test on a hosted runner, it ran code from outside pull requests under pull_request_target with write permissions, which is a known way to leak repository write access.

Desk: Hermes (Drake's MacBook, driving the Spark).

Drake, 2026-10-18: all testing runs on the local network; nothing is tested
on GitHub-hosted runners. This removes the workflows here that built or
tested code on ubuntu-latest. Workflows that only publish (the aienos.com
Pages deploy) stay, without their test step.
@drakestapleton
drakestapleton merged commit b368ea8 into main Oct 18, 2026
3 of 4 checks passed
@drakestapleton
drakestapleton deleted the chore/no-hosted-tests branch October 18, 2026 23:41
@github-actions

Copy link
Copy Markdown

⚖️ Sovereign Code Review & Alignment Gate

Greetings @drakestapleton. I am AIEN, the automated review gate for the AIENOS project.

Your pull request #25 ("Remove hosted test workflows: testing runs on the Spark only") has undergone automated auditing against the project standards.

✅ Doctrine Diff Audit: PASS

  • Telemetry Check: Clean (zero tracking or surveillance hooks detected).
  • Sovereign Voice & Formatting Check: Clean (zero em/en dashes, zero banned buzzwords).
  • Secrets & Credentials Check: Clean (zero plaintext secrets, hardware vault only).
  • Status: Project standards verified.

🌿 Sovereign Steward: Contributor Alignment Interview

Greetings @drakestapleton. I am AIEN, the automated steward for the AIENOS project.

We welcome all contributors who share our commitment to open collaboration, global humanity, and disciplined systems craftsmanship. We build to expand computing capability, advance open-source intelligence, and share technology freely with the world.

Your pull request #25 ("Remove hosted test workflows: testing runs on the Spark only") is ready for stewardship alignment.

Please respond directly to these four alignment inquiries:

  1. Long-Term Mission Alignment:
    This initiative is an enduring engineering commitment to open-source technology for humanity, not a vehicle for short-term hype, social media monetization, or get-rich-quick ventures. How does your contribution support global progress and the resilience of local communities?

  2. Telemetry & Integrity:
    Do you certify that this change introduces zero telemetry, zero surveillance, and zero artificial paywalls?

    "I certify that my contribution is submitted in service of human sovereignty and open collaboration. I affirm that this work maintains zero telemetry, contains no surveillance backdoors, and introduces no artificial barriers, and that I offer it under AGPL-3.0-or-later, the license that governs this project. I build so that intelligence is owned by the person who runs it, not rented."

  3. Downstream Heritage Preservation:
    Do you acknowledge and agree that any downstream branch, fork, or copy of this work remains under AGPL-3.0-or-later and retains the project's license and attribution notices, as the LICENSE file requires?

  4. Craftsmanship & Native Discipline:
    What architectural trade-offs did you make, and how did you verify that this code introduces zero regressions, zero unneeded dependencies, and complies with our pure native compiled standards?


Reply to this comment with your affirmation. Once verified against the project standards, I will grant the sovereign-interview-passed clearance. For direct sovereign coordination: Drake Stapleton (drake@aienos.com) and AIEN (aien@aienos.com)

@github-actions github-actions Bot added needs-testimony Contributor testimony required sovereign-audit-passed Constitutional diff audit passed labels Oct 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-testimony Contributor testimony required sovereign-audit-passed Constitutional diff audit passed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant