Encourage agents to share discoveries and ask for team knowledge

[bruno-archastro]

Summary

• Make knowledge sharing part of the existing core agent workflow: post verified discoveries before a fix or PR exists, and ask for missing team context without waiting for a blocker.
• Add concrete triggers, evidence requirements, duplicate checks, and a valid “nothing worth sharing” outcome. No posting quotas, invented lessons, or extra stop gates.
• Keep helper findings with the parent, preserve named addressees for questions, and use ordinary room notes when ownership is unknown.
• Regenerate all eight harness skill copies and add distribution-policy regression coverage.

Verification

• npm run typecheck: passed.
• npm test in tools/plugin-gen: 116 passed.
• npm run check: all 140 generated files match.
• git diff --check: passed.
• Full explicit-placement process/configuration proof with Bash 5 and the existing locally built CLI: passed. A negative control that writes personal settings still fails the unchanged snapshot assertion.

This changes guidance, not a runtime guarantee that agents post more useful messages. Live behavioral validation remains outstanding. Companion CLI changes add the same reflection prompt to session contracts and initial reporting nudges; neither PR installs hooks, releases a binary, or updates anyone’s installed skills.

CI triage

• Generated-plugin, source-only bootstrap and installer checks pass.
• Before the fixture correction, both released-CLI placement checks failed on PR head 110ba5b and unchanged main (0f2e0534): PR run, baseline run. Both use CLI 0.54.4; Windows reports “Ordinary commands changed personal configuration.”
• Local isolated-HOME diagnosis found first-use creation of .config/archdev/install_id, not implicit hook setup. Commit df44a2513ce5a21ffa2a9396ec9ae6c6b7d13843 seeds this valid analytics identity in both fixtures, just as the product default was already seeded. The ID, every hook/settings file, and repository files remain in the byte-for-byte snapshots; no exclusions or assertions were removed. Both released-CLI placement checks now pass.
• The macOS zsh interrupt test also failed identically on the base. A single failed-job rerun on 110ba5b failed again at the same terminal-exit assertion: installer run. Local Ctrl-C probes before and during noncanonical reads both passed; no root cause or installer fix is claimed. The assertion is unchanged.
• Current head df44a2513ce5a21ffa2a9396ec9ae6c6b7d13843: 20/20 checks successful, including the unchanged macOS interrupt case. Bootstrap CI, installer CI, plugin CI. Current-head server PR and all six available code-region assessments are low. Live agent adherence remains unverified; a current-head scope assessment is unavailable.
• No review comments or review threads are present, but branch rules require one approving review. The authorized normal rebase-merge attempt was rejected by GitHub’s base-branch policy. No admin override or auto-merge was enabled.
• Verified the new question fallback against CLI help and the post builder: plain log post is an ordinary note; question/handoff still require an addressee. This PR changes guidance, not routing.

CLI companion: https://github.com/ArchAstro/firstlanding/pull/19055. Its normal pre-commit hook passed formatting/lint/build but hit known checkout-local temporary-fixture failures; the user explicitly approved bypassing that local hook for publication. CLI CI passed on 87b608b359 (15 successful checks, six conditional skips). Repository bot archdev-keep-up-with-your-agents[bot] then rebase-merged the CLI PR at 2026-10-20T13:23:06Z; this session did not request that merge or initiate a release. This skill PR is fully green but remains open, blocked on the approving review required by repository rules. Installed rollout and useful live agent behavior are not verified.

Agent session: 01a15925-c8b3-7027-bd4b-acb8a7d46be6