[Review required] SDD onboarding: webex-android-sdk-example

[ciscoRankush]

Automated Spec-Driven Development onboarding.

Run outcome

❌ FAILED — review required. Do not merge until the blocking checks are resolved.

• Time taken: 23m

• Cost: $16.3850 reported + additional unknown cost

• Automated answer source: config-fallback (preconfigured assess-only assumption; not human-verified).

Failure context

• Code: validation_unavailable
• Detail: validation_unavailable: generated-document conformance could not execute: generated-doc-conformance: generated-doc-conformance: typed generated-document conformance report was rejected: generated-document conformance artifact mapping contradicts host-owned facts

Provenance

• Execution identity: repo-annotation@0.7.1+workflow.1#sha256:94e34b47e7e9b38e4748b51db0105845036409b5f307ac676fd75e8b31f85b4f
• Plugin source bundle: repo-annotation@0.7.1+workflow.1#sha256:553a28755f5664ba13160280719b2ba6aeb45d1f3c3903dbf7477300d0e79aab
• Claude runtime projection: claude-plugin@v1#sha256:334dfb789fb554be952b7f7fe25a77d3a0c757efdc650ff938401bd2e9d1a5c1
• Plugin upstream commit: b19a028dbbd0c73516ccb50a371618ede5cefc0a
• Workflow overlay: workflow.1
• Target repository commit: a0f5876b6aa973330c1a02b8c6f33fe23ae46ebe

Validation

Gate: BLOCKED

• Outcome: validation_unavailable
• Proof: not established
• 🔒 manifest-schema (deterministic): pass
• 🔒 plugin-conformance (deterministic): pass
• 🔒 source-fidelity-inventory (deterministic): pass
• 🔒 heading-conformance (deterministic): pass
• · manifest-parity (deterministic): fail
  • Medium hf_747fb6fa11ebb4abdf4fbeda1b036e8a0e210aef8150c283198d2129483cae36: ai-docs/ARCHITECTURE.md: auth/env var "CLIENT_SECRET" is in the docs but not in the manifest
  • Medium hf_28c3283325d7c0a43c5ddaa32d3d6f2a5ef89a78fdfdd78f4978023e03d870e3: ai-docs/SECURITY.md: auth/env var "CLIENT_SECRET" is in the docs but not in the manifest
  • Medium hf_7b500bc90fe3c89968a3099b6f48be2d24623474306cef7a000e051ef7d262dd: ai-docs/GETTING_STARTED.md: registry host "27.2.12479018" is in the docs but not in the manifest
  • Medium hf_84e72ba37ba3af2bdbcf102b921befee91f455b3d27f75e35fa53ad10130a2b6: ai-docs/GETTING_STARTED.md: registry host "dependencies.kt" is in the docs but not in the manifest
  • Medium hf_ab24245f7f8db1b4e2ed735ec6bcd1bebaa9c5c9e9111d5dfd12c5961ffcaf59: ai-docs/GETTING_STARTED.md: registry host "webexsdk.aar" is in the docs but not in the manifest
  • Medium hf_75a2b8a6c595782f4b76cce3ab4cf93c13ac14d54acdc09090b044e8b0d2b463: ai-docs/GETTING_STARTED.md: registry host "security.md" is in the docs but not in the manifest
  • Medium hf_e589d16e03df74706b68ed861740f0260500c53d285ab5fd6d22f049b170a475: ai-docs/GETTING_STARTED.md: registry host "build.gradle" is in the docs but not in the manifest
  • Medium hf_f4227c6085ddbf88c57ba82686de117b8396e6f85081ea25cd03f71227949911: ai-docs/GETTING_STARTED.md: registry host "readme.md" is in the docs but not in the manifest
  • Medium hf_81ee361f1e7107b594f0539624f719f99d1ef33583063ad63c7c687a3dd0e5ac: ai-docs/GETTING_STARTED.md: registry host "allprojects.repositories" is in the docs but not in the manifest
  • Medium hf_352b8c683857fe9f78efa947e5eaa89a8928e1815eebd1b0adda645593d4818a: ai-docs/GETTING_STARTED.md: registry host "agents.md" is in the docs but not in the manifest
  • Medium hf_9d38421e556a895c0e56d9d6231f1adc1951165f2542e0c2cc22432027df7ba1: ai-docs/GETTING_STARTED.md: registry host "architecture.md" is in the docs but not in the manifest
  • Medium hf_1b9dea3c6604ad69debd19c010e8a3cd92a2935a744f7c7ff1a342df497858e7: ai-docs/SPEC_INDEX.md: registry host "manifest.json" is in the docs but not in the manifest
  • Medium hf_af45a1234ed91bad95a2be418f13d401c98850b4c5722cb51a64654290ea09e7: ai-docs/SPEC_INDEX.md: registry host "rules.md" is in the docs but not in the manifest
  • Medium hf_0e436910c8a2e4b20f25e226dcf05a66a3d462877ef70f2a2c040e20ab8c945f: app/src/main/java/com/ciscowebex/androidsdk/kitchensink/ai-docs/kitchensink-spec.md: registry host "callobjectstorage.kt" is in the docs but not in the manifest
  • Medium hf_85f9e5ef9b5e2b32214b165a7ff7e949255a055723cb4290e4f07f0de6e88ed4: app/src/main/java/com/ciscowebex/androidsdk/kitchensink/ai-docs/kitchensink-spec.md: registry host "architecture.md" is in the docs but not in the manifest
  • Medium hf_f69cfde7f5ea8f03ab99a06a9eab2756f7aabcb2323247770da338dac03820f3: app/src/main/java/com/ciscowebex/androidsdk/kitchensink/auth/ai-docs/auth-spec.md: registry host "architecture.md" is in the docs but not in the manifest
  • Medium hf_6f060e56d6fe4387ada3b3d8b6d82ca3c389e2fe4be2a9264a35a00e084aa166: app/src/main/java/com/ciscowebex/androidsdk/kitchensink/calling/ai-docs/calling-spec.md: registry host "callobjectstorage.kt" is in the docs but not in the manifest
  • Medium hf_0c8de7f54112fa82f49dd834691e944afa853fa7f4c66dac1992fd31a8d926df: app/src/main/java/com/ciscowebex/androidsdk/kitchensink/calling/ai-docs/calling-spec.md: registry host "architecture.md" is in the docs but not in the manifest
  • Medium hf_ee00ab8d8ec268a4b8b3bd8183d719d2d3dd6cdebaad2a28089538aeab37914e: app/src/main/java/com/ciscowebex/androidsdk/kitchensink/messaging/ai-docs/messaging-spec.md: registry host "architecture.md" is in the docs but not in the manifest
  • Medium hf_d2fe86d84bd64f1a9f7c3b31b995e56e3d633d78c505e97d16ca31c799291730: app/src/main/java/com/ciscowebex/androidsdk/kitchensink/webhooks/ai-docs/webhooks-spec.md: registry host "architecture.md" is in the docs but not in the manifest
• 🔒 generated-doc-conformance (llm): fail
  • execution: unavailable; runtime claude-cli; model us.anthropic.claude-opus-4-8; tools unknown; evidence unknown/unknown
  • Blocking conformance_report_invalid: typed generated-document conformance report was rejected: generated-document conformance artifact mapping contradicts host-owned facts

Coverage

• Specced-module coverage: 0% (0/10 modules).

Status	Modules	Meaning
Specced	0	Surface documented to the policy threshold
Partial	5	Documented but below the threshold
Untracked	5	No specification yet

⚠️ 10 of 10 modules are not yet Specced. The generated coverage-review report in .generated/ names the highest-impact remaining gaps and the next required action for each; treat that as the work list rather than this summary.

Next steps

1. Review the blocking validation findings and the generated diff.
2. Correct the documentation on this review branch, or fix the workflow if the finding is not repository-specific.
3. Re-run the onboarding job and confirm every blocking check passes before merging.

Harness job: 4c2aeec1-d1de-4b14-9456-25d514ec82c8