feat: add Qwen Cloud hackathon proof bundle

[princepspolycap]

Problem

The Qwen Cloud Global AI Hackathon packet was drafted, but the submission lacked a public proof bundle, license, architecture asset, integration evidence, and demo recording plan.

Root Cause

The existing repository had agent architecture material but no bounded, truthful Qwen Cloud proof directory and no explicit credential boundary.

Changes

• Add LICENSE with MIT terms.
• Add hackathon/README.md documenting the Autopilot Agent proof bundle and claims boundary.
• Add hackathon/qwen_integration.py, an OpenAI-compatible Qwen Cloud adapter that fails closed when credentials are absent.
• Add hackathon/architecture.svg, a rendered architecture diagram.
• Add hackathon/demo_script.md, a three-minute recording plan and evidence checklist.

Testing

• python -m py_compile hackathon/qwen_integration.py passes.
• Running the integration without credentials fails closed with the explicit message: Qwen Cloud is not configured. Set QWEN_API_KEY and QWEN_BASE_URL....
• No live Qwen request was claimed or attempted because credentials were not available in this execution.

Remaining submission blockers

• Live Alibaba Cloud/Qwen deployment receipt and public code link require valid credentials and endpoint.
• Public demo video URL is not created by this PR.
• Devpost submission remains intentionally out of scope.

[princepspolycap]

Build and validation evidence

Compute sandbox checkout of feat/qwen-cloud-hackathon-proof:

python -m py_compile hackathon/qwen_integration.py
PASS

Credential-boundary smoke run:

QwenCloudError: Qwen Cloud is not configured. Set QWEN_API_KEY and QWEN_BASE_URL to run the live proof; no credentials are bundled.

This is intentional fail-closed behavior. No live Qwen or Alibaba Cloud deployment was claimed without credentials. The branch includes the MIT license, README, integration seam, architecture SVG, and demo script.

[princepspolycap]

Proof-gap closure update

Added and verified on the existing PR branch feat/qwen-cloud-hackathon-proof:

• hackathon/deployment_proof.md at commit f18ff881da9fc068cad919476496c1c7a39bb70d, a submission-safe receipt template that remains explicitly NOT VERIFIED.
• hackathon/README.md updated at commit d5cc68dd93d2549e6dbf383979e2e45c60981a3f to link the template and clarify that local compilation is not deployment evidence.

Verification

• python -m py_compile hackathon/qwen_integration.py passed.
• Running without QWEN_API_KEY and QWEN_BASE_URL failed closed with the expected QwenCloudError; no fabricated response was produced.
• Read-back verification confirmed both files are present on the PR branch.

No live Qwen request was attempted because credentials and endpoint were unavailable. Remaining external blockers are a real provider receipt and the public demo video URL.

[princepspolycap]

Qwen / Alibaba deployment-proof verification

I checked the PR branch and compute environment without changing the repository.

Evidence

• QWEN_API_KEY, DASHSCOPE_API_KEY, ALIBABA_CLOUD_API_KEY, QWEN_BASE_URL, DASHSCOPE_BASE_URL, and ALIBABA_CLOUD_ENDPOINT were all absent.
• Repository search found only the existing credential-boundary documentation and adapter references, not a real provider endpoint or credential.
• python -m py_compile hackathon/qwen_integration.py passed.
• Running the adapter with credentials unset produced the expected fail-closed error: QwenCloudError: Qwen Cloud is not configured...

Disposition

No live provider request was attempted. The existing hackathon/deployment_proof.md remains correctly NOT VERIFIED; I did not replace it with a fabricated proof claim. No files were changed in this verification pass.

Detailed receipt artifact: qwen_live_proof_verification_2026-07-18.md (artifact ID 0db9a772-c16c-4490-8a69-e6733c10656f::1.0).

A real proof update requires provider-issued Qwen/Alibaba credentials and endpoint supplied out-of-band, plus a sanitized provider response/request receipt.

[princepspolycap]

Review receipt: REQUEST_CHANGES recommended. [BLOCKING] hackathon/qwen_integration.py uses print(result) in runtime code, violating Poly's structured logging rule. Use PolyLogger or return the result to a caller without printing. The PR also lacks a concrete issue closure reference and no CI check receipt is available for this head SHA. Add an exact executable no-credential fail-closed validation receipt. Deployment proof correctly remains NOT VERIFIED.

[princepspolycap]

Review blockers addressed in follow-up PR #13: #13

• Removed raw print(result) output from hackathon/qwen_integration.py.
• Added structured, secret-safe logging and non-zero fail-closed CLI behavior.
• Added no-credential regression tests in tests/test_qwen_integration.py.
• Linked implementation tracking issue Harden Qwen Cloud proof adapter for PR #11 review #12: Harden Qwen Cloud proof adapter for PR #11 review #12

Verification receipt:

• Commits: bc742dba3f9abfa337cd4e25c3c540bf71fbb24c and 4f7f0055ed561f05af19212466df0e5a13dd688a.
• Branch: fix/qwen-cloud-pr-11-review-blockers.
• PR fix: harden Qwen Cloud proof entry point #13 opened against feat/qwen-cloud-hackathon-proof.
• Compute sandbox test attempt was blocked by MCP session init failed: no session ID. status=405; no test pass is claimed.
• Live Qwen/Alibaba deployment remains NOT VERIFIED because no real credentials or endpoint were available.