docs(archdev-skill): tag every archdev log post with its project

[ark-archastro]

Review on ArchCode

Problem and author intent

Slice 2 of the ArchDev projects plan added archdev log post --project <id> (firstlanding #15014), on top of archdev projects list|show|create|update from slice 1 (#14977). The CLI warns when a post carries no project but does not refuse, so the skill text is what actually gets agents tagging their posts. This is the skill half of that change.

Requires CLI 0.46.0, the release that ships both projects and log post --project (published 2026-09-24 from firstlanding 25faed7884, which includes both PRs). The bootstrap scripts now enforce that floor and upgrade older installs, so the skill text and the CLI cannot drift apart on a machine that runs bootstrap.

What changed

• archdev/SKILL.md section 3, beat 2: before the first post, find the project with archdev projects list --query "<subject>" and pass its ID as --project <id> on every archdev log post in the session.
• archdev/references/monitor.md:
  • New "Tag every post with its project" subsection under Team lifecycle posts: look up first, read the descriptions, pass the ID on notes, events, and --kind posts alike; create a project only when no active one fits, named for the product area or initiative; never one per PR, task, or session. Explains that the tag lands in metadata.project_id beside the pull_request/task_id join keys, that there is no default, and that an untagged post warns and shows under Unfiled.
  • Every archdev log post example (lifecycle table examples, reply, merged --kind done --event pr.closed, free-text, and the structured Report step 5) carries --project.
  • A rules bullet: the CLI checks the prj_ shape only and never looks the project up on a post.
  • The project belongs to the work, not the session: on a steer to a different initiative, look it up again before the next post (also in SKILL.md beat 2).
  • A compatibility bullet: on a CLI below 0.46.0 that bootstrap could not upgrade, post without the flag and do not retry with it.
• archdev/scripts/bootstrap.sh, bootstrap.ps1, references/bootstrap.md: minimum version 0.46.0, and supports_skill / Test-Skill probe projects list --help and log post --help for --project <id> before accepting an installed binary.

Rebased on main after cc6592e (review-annotations text); the SKILL.md beat-2 paragraph keeps both additions.

Risk

Low. Docs plus the bootstrap version floor. Raising the floor means every machine that runs bootstrap upgrades to 0.46.0 on its next session start; that is the intended effect.

Testing

Read-through plus probe checks. The examples match archdev log post --help on a CLI built from firstlanding main at cf41c32751, each line parses as shell (one added token per line, quoting unchanged), bash -n passes on bootstrap.sh, and the two new probe greps were run against that build (match) and against an installed 0.45.9 (no match). bootstrap.ps1 was not executed (no PowerShell here).

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-24T01:48:48.234706Z	3fdfb58	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3fdfb5898d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".