[codex] Clarify harness profile and provenance docs

[BruceL017]

Summary

• Add Harness profile and citation/provenance docs that separate portable OKF bundle conventions from Harness workspace support files.
• Add a compact data analytics example workspace with dataset, table, metric, relationship, reference, manifest, and raw source layers.
• Clarify that URL source registration records a pointer, not a webpage snapshot, including CLI next-step guidance and a test.

Verification

• pnpm lint
• pnpm typecheck
• pnpm test
• pnpm build
• node packages/cli/dist/main.js check --workspace examples/data-analytics-workspace --json
• node packages/cli/dist/main.js evidence "How do we calculate monthly active buyers?" --workspace examples/data-analytics-workspace --json

[pumblus]

@BruceL017 thanks for the PR and for pushing the provenance docs forward. The Harness profile, citations/provenance guidance, and URL-source clarification all fit the current direction: local-first workspaces, explicit source trails, and bounded evidence from synthesized wiki/ content. I do not think this should merge as-is yet, mainly because the new examples/data-analytics-workspace expands the public example surface beyond the current “one small example workspace” scope, and the branch currently has conflicts in docs/WORKFLOWS.md and llms-full.txt.

Could you split this into two PRs? I would be comfortable reviewing the docs/CLI clarification first: docs/HARNESS_PROFILE.md, docs/CITATIONS.md, the URL pointer next-step, the source test, the existing example citation fix, and regenerated llms files after resolving conflicts. The data analytics example looks useful, but I think it should be a separate product-scope decision with its own validation coverage before we add a second maintained public example.