Verify GitHub Actions visibility for Agent Machine validation workflow

[mdheller]

Context

The repo now has .github/workflows/validate.yml and a make validate path covering JSON schemas/examples, YAML manifests, Quadlet templates, AgentPod plan/receipt rendering, CLI smoke checks, and Homebrew formula syntax.

Connector checks for recent commits returned no workflow runs and no combined statuses. That is not a confirmed CI failure, but it means validation status is not visible through the current connector query path.

Required outcome

Confirm whether GitHub Actions is enabled and whether the validate workflow is running on pushes and pull requests to main.

Acceptance criteria

• A visible workflow run exists for a recent commit on main, or a documented reason exists for why no run appears.
• If Actions is disabled or unavailable for this repository, document the repository setting/remediation path.
• If workflow syntax prevents execution, fix .github/workflows/validate.yml.
• If the connector cannot see Actions runs even when GitHub shows them, document that limitation separately.
• make validate remains the canonical local validation command.

Related files

• .github/workflows/validate.yml
• Makefile
• scripts/validate-json.py
• scripts/validate-yaml.py
• scripts/validate-quadlet.py
• scripts/render-agentpod-plan.py
• scripts/render-agentpod-quadlet.py
• scripts/render-agentpod-k8s.py

[mdheller]

Update as of latest bootstrap activation work:

• Latest checked commit: b5083402dbde4b53e87ffb81de3ac0cd74f4e76e.
• fetch_commit_workflow_runs returned an empty run list again.
• get_commit_combined_status returned an empty status list again.
• This remains an absence of visible CI/run data through the connector, not proof of pass or failure.

The repo now has substantially broader validation wired through make validate, including JSON schemas/examples, YAML, Quadlet, renderers, evidence, governance, activation decisions, package imports, CLI smoke checks, and formula syntax.

Next remediation remains: confirm whether Actions is enabled/triggering in the GitHub UI or whether this connector endpoint cannot see the relevant workflow runs for pushes to main.

[mdheller]

CI visibility update after bootstrap docs/index and integration-doc repair:

Observed repository/workflow state through the connector:

• Repository SourceOS-Linux/agent-machine is visible and the connector reports admin/maintain/push permissions.
• Default branch is main.
• .github/workflows/validate.yml exists on main and is configured for push and pull_request events on main.
• The workflow installs requirements-dev.txt and runs make validate.

Latest connector checks performed:

• Checked commit 133534c47f92e5c3b7e29ae62f9befa17a5fc07f with fetch_commit_workflow_runs: returned workflow_runs: [].
• Checked the same commit with get_commit_combined_status: returned statuses: [].

Tooling limitation observed:

• The available connector surface exposes commit-filtered workflow/status lookups and run/job/artifact/log lookups when a run ID is already known.
• I did not find a general repository workflow-run listing action in the available connector surface.
• A commit search attempt using only qualifiers was rejected by GitHub search (Search text is required), so that did not provide an alternate run-discovery path.

Current conclusion:

• This is still not proof that validation passed or failed.
• It is evidence that CI visibility is unavailable through the connector path currently being used.
• Bootstrap MVP remains blocked on external validation proof: either a visible GitHub Actions run in the GitHub UI or a real local/runner execution of make validate.

Recommended remediation:

1. Check the GitHub Actions tab in the UI for this repository and confirm whether the validate workflow has runs for pushes to main.
2. If no runs exist, confirm whether Actions is enabled for the repo/org and whether public-org policy restricts Actions.
3. If runs exist in the UI but the connector still returns empty data, document the connector visibility limitation here and treat UI/local runner output as the validation source of truth.
4. Keep make validate as the canonical validation command.

[mdheller]

Validation proof update:

• PR Harden validation workflow for bootstrap proof #9 (Harden validation workflow for bootstrap proof) produced a visible GitHub Actions workflow run through the connector.
• Workflow run 25322297618 completed successfully.
• The job Validate contracts, examples, CLI, formula, and docs completed successfully.
• The run executed the canonical make validate path.
• PR Harden validation workflow for bootstrap proof #9 was merged after the green run.
• Merge commit: bceca6e92847edb19c2fd0f45709de45fe430e03.

Status change:

• PR-triggered GitHub Actions visibility is confirmed.
• Real GitHub Actions validation proof is confirmed.
• Main-branch push workflow visibility remains uncertain through the connector/API path because post-merge commit lookup returned no visible workflow runs at the time of checking.

I updated BOOTSTRAP_STATUS.md to mark PR validation proof complete and leave only main-branch push visibility as an open follow-up.

Recommendation:

Keep this issue open until main-branch push workflow visibility is either confirmed or explicitly accepted as a connector/API limitation. Bootstrap MVP no longer lacks validation proof; it now lacks only main-branch visibility certainty.