chore: prepare v1 rc release readiness

[0xsarwagya]

Summary

• fixes the failing license check from the current Validation Lab run by aligning nested package LICENSE files with the root LICENSE
• prepares the repository/package/skills/site metadata for v1.0.0-rc.1
• adds RC-safe publish guards, npm pack validation, release-version validation, CI/security workflows, and first-user smoke validation
• refreshes generated site docs, validation evidence, skills reports, and release readiness reports

Evidence

• pnpm install --frozen-lockfile
• pnpm build
• pnpm check-types
• pnpm test
• pnpm release:gates
• pnpm docs:check-site

Notes

The original failed GitHub job was on main at 3cf80c2 and failed in pnpm license:check because packages/intelligence/LICENSE differed from the root LICENSE. This branch passes the recursive license check locally.

RC_READINESS.md still marks public RC launch as blocked until the dedicated ontoly.sarwagya.wtf domain is attached or the live OSS route remains canonical.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.