[ABZerra]

What changes and why

Document the folder-based Cowork setup verified on 16 October 2026, including saved project instructions that explicitly read AGENTS.md when the thin CLAUDE.md import does not expand. Explain the tested contribution route through Desktop Commander and existing host Git/GitHub CLI credentials, with clear boundaries between folder reads, authentication, and publication.

Add one setup guide and verification record, link it from SETUP.md, and replace stale blanket claims of unverified Cowork submission in README.md, AGENTS.md and CONTRIBUTING.md. No validator, workflow, review-policy or live setting changes.

Evidence and limits

Based on owner-authorized folder tests at accepted main e4192e5a040185efb383d329f68175d9c7c92a45, observed by Codex in the isolated Cowork project, plus test PR #4 and its passing checks. PR #4 is closed unmerged and its branches were deleted. The guide labels the verification as observations rather than a verbatim transcript.

Verified: fresh-session project bootstrap, explicit policy reads, repeated same-revision freshness checks, and draft PR creation through the host connector. Not verified: automatic AGENTS import, advancing-main refresh, PR reuse, successful approved auto-merge, or the separately unauthenticated local Claude Code CLI. No private session URLs, local usernames/paths, credentials or unrelated drafts are published.

PR #3 is now merged under the explicit one-time owner exception. This branch has been refreshed against accepted main 6d6301fd3d89660b3d2eca2937fae43d8f48c885; the remaining diff contains only the five Cowork documentation files. The README resolution preserves both the adopted team-review rule and the scoped capability statement. No further governance change is proposed.

Validation and review

All three local validators report zero violations; git diff --check passes. Independent AI review found no actionable issues. The owner subsequently authorized a one-time merge exception for PRs #3 and #5 only, without claiming independent human approval. Final live checks must pass before publication. Future changes retain the one-independent-human-review rule and all existing protections.

Owner-requested maintenance

• Requester: repository owner ABZerra, in the Curator setup conversation.
• Authorized scope: “update the setup documentation with the verified Cowork bootstrap and contribution workflow in a separate draft PR. Don’t merge anything or touch my existing drafts.”
• Behavioral changes: replace outdated capability statements and explain an explicit project bootstrap; preserve shared policy, local adaptations and contribution safeguards.
• Starter source: accepted subvisual/curator main at the SHA above. Focused documentation maintenance, not adoption of an upstream starter release; origin metadata unchanged.
• GitHub settings changes: none.

Latest owner request: prepare PRs #3 and #5 for human review and resolve overlap, without merging or touching existing drafts. This authorizes the review-stack preparation, not publication. Reviewer focus: bootstrap reads shared policy explicitly; host connector/credentials are prerequisites of the verified contribution route; untested capabilities remain qualified.

One-time owner publication exception

ABZerra explicitly authorized merging PRs #3 and #5 without the usual independent human approval for initial sharing readiness. This supersedes the earlier draft/no-merge instruction for these two PRs only. No human review approval is claimed. Required review policy remains in force for all future changes; any temporary administrative exception must be restored and verified after each merge. Checks must pass on the final content.