Add issue-ready run bundles

[AbdelStark]

Problem

Preserved run workspaces could already feed release evidence bundles, but operators still lacked a run-scoped issue export that prints the command context, expected signal, observed failure, artifacts, and safe-to-attach notes for a single run.

Closes #148.

Solution

• Add worldforge runs bundle <run-id> for one-run issue bundles under .worldforge/issue-bundles/<run-id>/ by default.
• Reuse the existing safe evidence-copying path while writing evidence_manifest.json, summary.md, and a new issue.md template.
• Record expected signal, observed failure, validation errors, digests, safe_to_attach, excluded files, and first triage step in the generated manifest/template.
• Redact host-local source paths from generated manifests and mark unsafe or local-only artifacts before attachment.
• Document the operator flow in evaluation, operations, and playbook docs.

Validation

• uv lock --check
• uv run ruff check src tests examples scripts
• uv run ruff format --check src tests examples scripts
• uv run python scripts/generate_provider_docs.py --check
• uv run pytest tests/test_issue_bundle_export.py tests/test_harness_workspace.py tests/test_observability.py
• uv run pytest tests/test_evidence_bundle.py tests/test_issue_bundle_export.py tests/test_provider_catalog_docs.py
• uv run pytest tests/test_cli_help_snapshots.py tests/test_docs_site.py
• uv run mkdocs build --strict
• uv run pytest
• uv run --extra harness pytest --cov=src/worldforge --cov-report=term-missing --cov-fail-under=90
• bash scripts/test_package.sh
• uv build --out-dir dist --clear --no-build-logs
• git diff --check

Caveats

This only packages local preserved run workspaces. It does not create GitHub issues, upload artifacts, store bundles remotely, or make unsafe host-owned artifacts attachable.