docs: align contribution requirements

[smiggleworth]

Askr context

This updates the CLI contribution guide to follow the organization policy in askrjs/.github#1.

Problem

The CLI has a local CONTRIBUTING.md, so GitHub will not inherit the new organization-wide guide. Its existing technical requirements need the same interested-party and automation expectations as the rest of Askr.

Change

• link the CLI guide to the organization policy
• require concrete Askr use, integration, community-resource, or evaluation context
• welcome disclosed, personally reviewed AI and automation
• reject unattended and mass-generated contributions without genuine Askr interest
• add Askr context and automation disclosure to the existing change checklist

Verification

• npm ci
• npm audit: 0 vulnerabilities
• npm run fmt -- --check
• npm run check: lint, typecheck, 224 coverage tests, changelog, build, publint, and package gates
• git diff --check

Automation disclosure

Codex assisted with inventory, policy drafting, editing, validation, and pull request creation. The maintainer directed the policy and reviewed its intended requirements.

[Copilot]

Pull request overview

Updates the repository-local contribution guide so it aligns with the Askr organization-wide contribution policy described in askrjs/.github#1, ensuring contributors see consistent requirements even though this repo has its own CONTRIBUTING.md.

Changes:

• Adds an “Organization contribution requirements” section that links to the org policy and summarizes its expectations.
• Introduces explicit requirements for concrete Askr context and AI/automation disclosure in the change checklist.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.