submit: add SafeGate Commerce Outcome

[Nurexen-Labs]

SafeGate Commerce Outcome

Adds the SafeGate Commerce Outcome submission under submissions/mcp-hackathon/nurexen-safegate-commerce-outcome/.

What it demonstrates

• Read-only post-payment commerce verification
• Base Mainnet USDC payment verification
• SafeGate-signed attestation verification for fulfillment and evidence
• Deterministic COMMERCE_VERIFIED outcome
• Public health and deployment-proof endpoints bound to the declared review commit

Public references

• Source: https://github.com/Nurexen-Labs/safegate-xagent-commerce-outcome
• Review commit: b460b88ce800839e69839a5d31aac949dfe2543c
• API: https://safegate-xagent-commerce-outcome.vercel.app/v1
• SafeGate: https://safegatelabs.xyz
• Commerce demo: https://www.safeshelf.store

Validation

• Official offline submission validator: PASS
• Official online submission validator: PASS
• Submission scope/security gate: PASS
• Changes limited to this single submission directory

SafeGate does not hold funds, move money, or replace payment rails. Payment verification is independently derived from the Base Mainnet receipt; fulfillment and evidence status are verified from the signed SafeGate attestation.

[Nurexen-Labs]

CI note: the submission validator workflow currently fails before reaching SafeGate validation. The failing step is Check out the untrusted submission without credentials; actions/checkout@v4 refuses to check out fork PR code from a pull_request_target workflow unless explicitly opted in.

Our local official offline validator and official --online validator both pass for this submission.

Please review the workflow checkout configuration and rerun the job when appropriate. Thanks.

[lessthanno]

Thanks for flagging this. We confirmed the failure occurs in the repository-side pull_request_target checkout safeguard before the SafeGate validator runs; it is not a validation failure of your submission.

Your reported local offline and online validation results are noted. We will address the workflow configuration on our side and rerun the official check once the safe review path is in place. No action is needed from you at this time.

[lessthanno]

Submission received: SafeGate Commerce Outcome

Thank you for submitting to the current X-Agent MCP Hackathon. We have received this PR and can see the source files included under submissions/mcp-hackathon/nurexen-safegate-commerce-outcome/source/.

This confirms receipt only. It does not mean the entry has passed eligibility checks, technical review, judging, or been selected for an award. Passing automated checks or a future merge for archival purposes does not, by itself, mean any of those decisions have been made.

Source retention: As required by the submission instructions, the complete source for the submitted capability must be included in this repository, with the dependency files and instructions needed to reproduce it. An external repository link alone is not sufficient. This allows X-Agent to retain the submitted version even if the original repository later becomes unavailable. Please exclude secrets, credentials, and private user data, and clearly document any external or private services the project depends on.

Current check failure: We confirmed that the repository's workflow stops before the submission validator runs. This requires a workflow fix on our side; it is not a rejection of your entry or evidence that your project failed review. Official validation has not yet completed, and you do not need to change your project to resolve this particular workflow error.

Please keep any updates in this PR while submissions remain open. Final review results and awards will be announced separately through the official event channels.

[github-actions]

Submission received — #33

Thank you for submitting to the current X-Agent MCP Hackathon. We have received your pull request.

This is a receipt only. It does not confirm eligibility, completeness, technical approval, a judging result, or an award. Passing automated checks or merging code for archival purposes does not, by itself, mean the entry has passed review or won a prize.

Please include the complete source for the submitted capability in this repository under submissions/mcp-hackathon/<slug>/source/, with dependency files, configuration examples, and reproducible setup/build instructions. An external repository link alone is not sufficient. The official copy is intended to remain available if the original repository later becomes unavailable. Do not include secrets, credentials, or private user data; clearly disclose external and private-service dependencies.

The automated checks report technical checks separately. A workflow failure is not a judging decision. Keep updates in this PR while submissions remain open, and keep the documented source version and deployment evidence consistent.

See the submission instructions. Final review results and awards will be announced separately through the official event channels.

[lessthanno]

We retriggered the official validation using the current review path. The run confirmed that this PR is still affected by a repository-side issue: its stored base commit predates the current validation script, so the job stops before inspecting the submission.

The repository fix is now under review in #51. No participant code change is required for this specific failure. We will run the current validator again after that fix is available.

This failed workflow is not an eligibility, technical-review, judging, or award decision.