Agent workspace clones commit as '<Display Name> <slug@roboco.tech>';
the emails map to no GitHub account, so CLA Assistant identifies those
committers by display name and reds any PR carrying agent-authored
commits with a signature no agent can post (live on PR #333). The
fleet is the org's own machinery, not an external contributor — the
roster names are allowlisted, wildcarded per team family.
- cla.yml granted contents:read, but CLA Assistant commits the signature
file to the cla-signatures branch in this repo, so GITHUB_TOKEN needs
contents:write. Under read-only it 403s ('Resource not accessible by
integration') and a contributor's signature is never recorded even after
they post the sign comment.
- greetings.yml passed issue-message/pr-message/repo-token (hyphens), but
actions/first-interaction@v3 uses issue_message/pr_message/repo_token
(underscores), so the required issue_message was 'not supplied'.
- Add full AGPL-3.0 LICENSE (canonical GNU text)
- Switch README and pyproject.toml from MIT to AGPL-3.0
- Add CLA.md (individual + entity) granting relicensing rights
- Add CONTRIBUTING.md explaining workflow and why the CLA exists
- Add CLA Assistant GitHub workflow to enforce signing on PRs
- Document licensing stance in CLAUDE.md
Renn F