Enforce issue-linked target workflow prompts

[OziinG]

Summary

• Enforce target-repository work as a GitHub issue-linked workflow in the root agent contract.
• Add scoped target-work guidance to the bootstrap skill after target repo creation.
• Update the target repo AGENTS template to require target issue, optional change-control issue, GitHub Development branch creation, linked branch verification, PR-to-dev, validation, merge, cleanup, and reporting rules.
• Define the local folder structure: the three control-plane repos live under <CLEVER_ROOT>/clever-agent-workspace/, and product/service target repos live under <CLEVER_ROOT>/projects/<project-slug>/<target-repo>/ where agent seed documents are injected.
• Add Python preflight workspace_check.session_open_check so bootstrap validation confirms the CLEVER_ROOT-based session layout before startup questions.
• Add preflight_check.agent_response_contract so prompts received at <CLEVER_ROOT> do not trigger ad-hoc work; the agent first inherits the CLEVER workflow, completes initial setup, then continues with the user's prompt.
• Add a concise GitHub README copy-paste prompt: create a CLEVER root folder, fetch the three control-plane repos, then follow clever-agent-project to prepare the work.
• Update regression tests for the branch/PR workflow, project checkout layout, session-root validation, root-prompt response style, and README prompt.

Intended folder layout

<CLEVER_ROOT>/
  clever-agent-workspace/
    clever-agent-project/
    clever-context-monorepo/
    clever-change-control/
  projects/
    <project-slug>/
      <target-repo>/
        AGENTS.md
        docs/project-brief.md
        .github/PULL_REQUEST_TEMPLATE.md
        scripts/apply-github-rulesets.sh

README root prompt shape

The README now provides a short user-facing prompt that says, in effect:

새 CLEVER 작업 루트를 하나 만들고, clever-agent-workspace 아래에 3대 레포를 받은 뒤, clever-agent-project의 README/AGENTS 지침에 따라 preflight와 작업 준비를 진행해줘. 초기 준비 전에는 구현/커밋/PR을 시작하지 말고, 준비가 끝나면 다음 작업은 주신 프롬프트대로 진행하겠다고 답해줘.

Linked issues

• target issue: Enforce GitHub issue-linked development workflow in prompts #34
• clever-change-control issue: Change request: agent-project GitHub workflow prompt enforcement clever-change-control#75

Concurrent Work Gate

• parallel work decision: allowed-with-non-overlap
• target repo issue: Enforce GitHub issue-linked development workflow in prompts #34
• clever-change-control issue: Change request: agent-project GitHub workflow prompt enforcement clever-change-control#75
• open PR checked: no overlapping open PR found during this branch work
• conflict candidates: none identified

Validation

• python3 -m pytest -q — 84 passed, 2 skipped
• python3 .agent/skills/bootstrap-clever-work/scripts/bootstrap_clever_work.py --cwd "$PWD" --workspace-check --json — emitted workspace_check.session_open_check (legacy-layout in this current checkout, with expected nested path reported)
• python3 -m py_compile .agent/skills/bootstrap-clever-work/scripts/bootstrap_clever_work.py — passed
• git diff --check — passed
• npm/Gradle target app commands — not applicable; this control-plane repo has no package or service backend manifest

Notes

• This control-plane repository uses main as the protected PR base; the prompt changes themselves instruct target repositories to use work branches from dev and PRs into dev.