fix: restore community archive validation and compare submitted checksums

Assisted-by: GitHub Copilot (model: GPT-6 Astra, autonomous)

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Author: KSchlobohm

.github/workflows/add-community-bundle.lock.yml

@@ -8,9 +8,17 @@ on:
     names: [bundle-submission]
   skip-bots: [github-actions, copilot, dependabot]
 
+engine:
+  id: copilot
+  args:
+    - --allow-url=https://github.com
+    - --allow-url=https://codeload.github.com
+    - --allow-url=https://release-assets.githubusercontent.com
+    - --allow-url=https://raw.githubusercontent.com
+
 tools:
   edit:
-  bash: ["echo", "grep", "sort", "python3", "jq", "date", "curl"]
+  bash: ["echo", "grep", "sort", "python3", "jq", "date", "curl", "sha256sum"]
   github:
     toolsets: [issues, repos]
     min-integrity: none
@@ -20,7 +28,9 @@ network:
   allowed:
     - defaults
     - github.com
+    - codeload.github.com
     - release-assets.githubusercontent.com
+    - raw.githubusercontent.com
 
 permissions:
   contents: read
@@ -54,6 +64,23 @@ safe-outputs:
     max: 3
   remove-labels:
     allowed: [validation-passed, validation-failed, needs-info]
+
+jobs:
+  conclusion:
+    pre-steps:
+      - name: Mark bundle submission passed after PR creation
+        if: needs.safe_outputs.result == 'success' && needs.safe_outputs.outputs.created_pr_number != ''
+        uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
+        with:
+          script: |
+            const issue = { ...context.repo, issue_number: context.payload.issue.number };
+            const labels = await github.paginate(github.rest.issues.listLabelsOnIssue, issue);
+            for (const name of ['validation-failed', 'needs-info']) {
+              if (labels.some(label => label.name === name)) {
+                await github.rest.issues.removeLabel({ ...issue, name });
+              }
+            }
+            await github.rest.issues.addLabels({ ...issue, labels: ['validation-passed'] });
 ---
 
 # Add Community Bundle from Issue Submission
@@ -100,6 +127,15 @@ Read issue #${{ github.event.issue.number }} and extract these issue-form fields
 
 Issue-form values appear beneath headings matching their labels.
 
+The optional checksum is free-form submission data, not a dedicated issue-form input.
+Extract `submitted_sha256` from the submitted issue, not release metadata or the
+computed digest. Accept a manually appended `### SHA-256` heading (including
+`### SHA-256 (sha256)`) or the `sha256` field in the Proposed Catalog Entry.
+If both sources supply a checksum, they must agree after trimming whitespace
+and normalizing hexadecimal case. A supplied checksum must contain exactly 64
+hexadecimal characters; malformed or conflicting values are submission failures,
+not an absent checksum.
+
 ## Step 2 - Validate the Submission
 
 Run every check and collect all failures before deciding the outcome.
@@ -149,11 +185,40 @@ Run every check and collect all failures before deciding the outcome.
 - Confirm the asset name is versioned and consistent with the submitted bundle
   ID and version.
 
-Use `curl` for binary downloads, follow HTTPS redirects with
-`--location --proto '=https' --proto-redir '=https'`, and bound the request with
-`--max-time 60`. Save the archive under `/tmp/gh-aw/` and inspect the final
-HTTP status with `--write-out '%{http_code}'`. A blocked or failed download
-must not count as a passed check; repository/release metadata is not a
+Use `curl` for binary downloads. After the URL passes the pinning checks, replace
+`VALIDATED_DOWNLOAD_URL` below with that exact URL, safely shell-quoted. Treat
+issue values as data, never as executable shell syntax:
+
+```bash
+curl --location --proto '=https' --proto-redir '=https' --max-time 60 --silent --show-error --write-out '%{http_code}' --output /tmp/gh-aw/community-archive.zip 'VALIDATED_DOWNLOAD_URL'
+```
+
+Run the download and checksum as separate shell calls, without `mkdir`, command
+substitution, pipelines, or chained commands. `/tmp/gh-aw/` already exists.
+Compute SHA-256 only after a successful download with final HTTP 200.
+Use `sha256sum /tmp/gh-aw/community-archive.zip` to record its digest as `actual_sha256`.
+If no checksum was submitted, skip the comparison without failing validation.
+Otherwise, use the edit tool to write `/tmp/gh-aw/community-archive.sha256` with
+exactly this one line and a trailing newline, replacing `EXPECTED_SHA256` with
+the validated `submitted_sha256` (two spaces before the fixed archive path):
+
+```text
+EXPECTED_SHA256  /tmp/gh-aw/community-archive.zip
+```
+
+Run this comparison as a separate shell call:
+
+```bash
+sha256sum --check --strict /tmp/gh-aw/community-archive.sha256
+```
+
+Require exit code 0 and an `OK` result before marking the checksum check passed.
+A `FAILED` checksum comparison is a Failed outcome: report the submitted and
+actual digests, remove `validation-passed`, add `validation-failed`, and stop
+without catalog/docs edits or a PR. Never replace a mismatching submitted checksum
+with the computed or release-metadata digest. A command that cannot run or read
+the archive is Blocked, not a successful comparison.
+A blocked or failed download must not count as a passed check; repository/release metadata is not a
 substitute for fetching the archive. Never execute downloaded content.
 
 Do not fetch arbitrary user-provided URLs. Do not claim the artifact was
@@ -203,15 +268,41 @@ should add to Spec Kit.
 
 ### Validation outcome
 
-If any check fails:
+Choose exactly one outcome below, in order. A check that could not run is
+incomplete, not a passed check or a confirmed submission defect.
+
+#### Blocked
+
+If a permission denial, sandbox/network restriction, timeout, or service outage
+prevents a required check, validation is blocked by the workflow environment:
+- Comment with the attempted URL, exact error, and workflow run link, asking a
+  maintainer to investigate and rerun validation.
+- Do not ask the submitter to change a URL or resubmit solely
+  because the workflow could not perform the check.
+- Remove `validation-passed`. Do not add `validation-failed` or `needs-info` solely for an
+  environment blocker. Do not describe unperformed checks as passed.
+- If independent submission checks failed, report those separately
+  and apply `validation-failed` for those failures only. An observed HTTP 404
+  or a checksum mismatch is a submission failure, not a permission failure.
+- Stop processing here without editing catalog/docs files or opening a PR.
+  Do not evaluate the Failed or Passed outcomes below.
+
+#### Failed
+
+If there are no environment blockers and a completed check found a submission defect:
 
 1. Comment once with every failed check and a specific correction.
 2. Remove `validation-passed`.
 3. Add `validation-failed`; add `needs-info` when submitter input is needed.
 4. Stop without editing files or creating a pull request.
 
-If all checks pass, remove `validation-failed` and `needs-info`, add
-`validation-passed`, and continue.
+#### Passed
+
+If there are no environment blockers and every required check completed and passed:
+remove `validation-failed` and `needs-info`, add `validation-passed`, and continue.
+After successful PR creation, the `conclusion` job also applies these
+issue labels independently of the agent. It does not run when no PR was created
+or safe-output processing failed.
 
 ## Step 3 - Determine Add or Update
 
@@ -227,7 +318,15 @@ correction at the same version.
 ## Step 4 - Update the Community Catalog
 
 Edit `bundles/catalog.community.json`. Insert new entries alphabetically by
-bundle ID. The entry shape is:
+bundle ID.
+
+For both new entries and updates, only after every required validation passes,
+set `sha256` to `actual_sha256` from the downloaded archive. Do this even when no
+checksum was submitted. Replace any previous catalog digest; do not reuse a digest
+from an older archive. A submitted mismatch must fail validation before this step;
+writing the computed digest must never be used to bypass that failure.
+
+The entry shape is:
 
 ```json
 {
@@ -240,6 +339,7 @@ bundle ID. The entry shape is:
     "author": "<author>",
     "license": "<license>",
     "download_url": "<download-url>",
+    "sha256": "<actual_sha256>",
     "repository": "<repository>",
     "requires": {
       "speckit_version": "<speckit-version>"
@@ -256,7 +356,7 @@ bundle ID. The entry shape is:
 }
 ```
 
-Use the validated proposed entry rather than inventing metadata. Keep
+Use the validated proposed entry for submitted metadata and set `sha256` as above. Keep
 `verified: false`. Update the top-level `updated_at` to today's UTC date at
 midnight and preserve the top-level `catalog_url`.