docs(ops): record OCI test cluster launch failure

[Hongjiseung-ROK]

Summary

• add docs/ops/oci-test-cluster-results.md with the full OCI validation attempt log
• record the exact oci compute instance launch timeout and the successfully created network OCIDs
• include PASS/FAIL verification status, teardown commands, and the missing required-plan-path note

Context

• Task issue: cs
• Wave: N/A for the 7-wave agent integration plan; this was an infra-only OCI validation run
• Ops plan reference: docs/ops/oci-test-cluster-plan.md
• Required integration plan path from the task was missing locally: /Users/hongjiseung/.agent-orchestrator/projects/chemsmart/worktrees/cs-orchestrator/bin/plan.md

Validation

• OCI IAM region-subscription check in ap-chuncheon-1
• OCI network create sequence completed (VCN, IGW, route table, security list, subnet)
• OCI compute create stopped on first failure and was not retried
• No chemsmart tests run; this PR only records infra validation results after the blocked launch

[gemini-code-assist]

Code Review

This pull request introduces a new documentation file, docs/ops/oci-test-cluster-results.md, which logs the results and failure details of an OCI test cluster deployment. The review feedback correctly identifies security and privacy issues, specifically the inclusion of personally identifiable information (PII) in absolute local file paths and the exposure of a specific source IP address. It is recommended to use relative paths or placeholders to mitigate these risks.

[gemini-code-assist]

This line contains an absolute local path that includes a specific username. This is considered Personally Identifiable Information (PII) and makes the documentation less portable. It is recommended to use a placeholder or a relative path (e.g., using ~).

Suggested change

	- Editable install path check passed: `/Users/hongjiseung/developer/chemsmart`
	- Editable install path check passed: ~/developer/chemsmart

[gemini-code-assist]

Exposing a specific source IP address in the documentation can be a security risk as it reveals infrastructure details. Consider redacting the IP address or using a placeholder.

Suggested change

	- SSH ingress source locked to: `112.171.21.152/32`
	- SSH ingress source locked to: <REDACTED_IP>/32

[gemini-code-assist]

Similar to line 55, this absolute path contains a specific username. Using a placeholder or a relative path is preferred for privacy and clarity.

Suggested change

	- Required reading path from task was missing locally: `/Users/hongjiseung/.agent-orchestrator/projects/chemsmart/worktrees/cs-orchestrator/bin/plan.md`
	- Required reading path from task was missing locally: ~/.agent-orchestrator/projects/chemsmart/worktrees/cs-orchestrator/bin/plan.md