docs(sdd): bootstrap SDD foundation for components

[akulakum]

COMPLETES #https://jira-eng-gpk2.cisco.com/jira/browse/SPARK-838067

This pull request addresses

webex/components has no Spec-Driven Development (SDD) foundation for AI-assisted development. Without standing docs, module specs, and a machine-readable manifest, agents and contributors lack a consistent entry point, task routing, and spec coverage tracking.

This PR bootstraps SDD Stage 0 using SDLC-Skills v0.4.3 (sdd-bootstrap plugin). No application/runtime code is changed.

by making the following changes

Added — SDD standing docs (ai-docs/)

• ARCHITECTURE.md — system layout, adapter-injection model, build/publish flow
• CONTRACTS.md — public npm export catalog
• GETTING_STARTED.md — clone, build, test, Storybook
• RULES.md, GLOSSARY.md, SECURITY.md, REVIEW_CHECKLIST.md, SPEC_INDEX.md
• patterns/ — co-located tests, wxc- class prefix, withAdapter injection

Added — module specs (3 modules, all Specced)

Module	Spec	Coverage
src/components/	src/components/ai-docs/components-spec.md	~96%
src/adapters/	src/adapters/ai-docs/adapters-spec.md	~97%
src/styles/	src/styles/ai-docs/styles-themes-spec.md	~96%

Added — agent entry point & manifest

• AGENTS.md — agent router and repo context
• .sdd/manifest.json — module registry, commands, coverage state, validation policy

Updated — .gitignore

• !.sdd/manifest.json — exception so manifest is tracked despite repo-wide *.json ignore
• .generated/ — excludes SDD skill temp outputs (questionnaire, conformance/validation reports)

Explicitly not included (local-only / install artifacts)

• .cursor/, .agents/, .claude/ — runtime skill bundles
• .sdd/templates/, .sdd/metrics/ — copied SDLC-Skills templates
• .generated/ — bootstrap working files

Follow-up required (Session B)

Manifest validation.status is not-run. A separate spec-validator run (different runtime than the generator, per minimum_independence: different-runtime) is required before the repo is SDD-ready.

Change Type

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Tooling change
• Internal code refactor

The following scenarios were tested

• The testing is done with the amplify link
• Docs-only change — no runtime behavior modified
• Generated-doc conformance review: 0 Blocking findings (bootstrap gate)
• Verified .sdd/manifest.json stages and tracks correctly after .gitignore exception
• spec-validator independent validation — pending Session B

The GAI Coding Policy And Copyright Annotation Best Practices

• GAI was not used (or, no additional notation is required)
• Code was generated entirely by GAI
• GAI was used to create a draft that was subsequently customized or modified
• Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
• Tool used for AI assistance (GitHub Copilot / Other - specify)
  • Github Copilot
  • Other - Please Specify
• This PR is related to
  • Feature
  • Defect fix
  • Tech Debt
  • Automation

Checklist before merging

• I have not skipped any automated checks
• All existing and new tests passed
• I have updated the testing document

---

[akulakum]

================================================================================
SDD SPEC VALIDATION REPORT — SUCCESS (Session B / Independent Runtime)

PR: SDLC Stage 0 bootstrap — webex/components
Branch: SDLC_SKILLS_FOR_COMPONENTS
Validated commit: c014045
Validation date: 2026-07-23
Validator: Codex (codex-agent-session / gpt-5)
Generator (Session A): Cursor (cursor-agent-session / composer)

Purpose:
This comment records the successful independent spec-validation (Session B) for the
SDD Stage 0 bootstrap docs in this PR. Validation was run per SDLC-Skills
spec-validator skill with minimum_independence = different-runtime.

FINAL RESULT

Status: SUCCESS — Pass with warnings
Gate: PASS
Blocking findings: 0

This means the SDD docs in this PR passed both:

• Axis A (methodology / SDD manifest rules)
• Axis B (docs match actual code)

Run ID: validation-2026-07-23T085321Z
Local report (not committed, per SDD policy):
.generated/sdd/validation/validation-2026-07-23T085321Z/validation-report.md

RUNTIME INDEPENDENCE

Generator: cursor-agent-session | run bootstrap-2026-07-23T124500Z
Validator: codex-agent-session | run validation-2026-07-23T085321Z
Policy: different-runtime — SATISFIED

WHAT WAS VALIDATED

• .sdd/manifest.json
• AGENTS.md, ai-docs/* (standing docs + patterns)
• src/components/ai-docs/components-spec.md
• src/adapters/ai-docs/adapters-spec.md
• src/styles/ai-docs/styles-themes-spec.md
• Code cross-checks: src/, package.json, rollup.config.js, README.md

KEY PASSES

• 0 blocking methodology or code drift findings
• Public npm exports match src/index.js + src/components/index.js + CONTRACTS.md
• Only WebexJSONAdapter is a public adapter export; domain adapters are internal
• Meeting control registry matches code (DISABLED_JOIN_CONTROL documented correctly)
• Module specs follow template order and section profiles
• Requirement IDs and WHAT/WHY rows valid across all module specs
• Bootstrap questionnaire and conformance evidence present (0 blocking)

NON-BLOCKING WARNING (1)

Module spec metadata still has approved_by = "pending PR approval".
Update approver name/date after PR merge approval in:

• src/components/ai-docs/components-spec.md
• src/adapters/ai-docs/adapters-spec.md
• src/styles/ai-docs/styles-themes-spec.md

VALIDATION HISTORY (this branch)

1. validation-2026-07-23T080630Z @ f9f0f35 — BLOCKED (adapter export + control registry drift)
2. validation-2026-07-23T083549Z @ c014045 — BLOCKED (module spec template order)
3. validation-2026-07-23T085321Z @ c014045 — PASS WITH WARNINGS (final / success)

EVAL SUMMARY

axis_a_fail: 0 | axis_b_fail: 0 | blocking: 0 | important: 1
hallucinated_api_count: 0 | include_if_violations: 0

CONCLUSION

SDD Stage 0 bootstrap for webex/components is spec-validation SUCCESSFUL.
Independent runtime validation passed with zero blocking findings.
Docs-only PR — no runtime/application code changes.

================================================================================