chore: migrate GitHub org references from always-further to nolabs-ai

[SequeI]

Linked Issue

Closes #

Summary

Update all GitHub URLs, CI repository guards, container image tags, downstream repo targets, and tooling references to reflect the org transfer from always-further/nono to nolabs-ai/nono.

Registry package namespaces (always-further/claude, always-further/codex, etc.) are intentionally unchanged — these are identifiers in the nono package registry and in users on-disk installs. Changing them would silently break existing user configurations without a migration path.

Test Plan

Checklist

• An issue exists and is linked above
• All commits are signed-off, using DCO
• All new code follows the project's coding standards (CLAUDE.md) and is covered by tests
• Public-facing changes are paired with documentation updates
• Release note has been added to CHANGELOG.md if needed

[github-actions]

PR Review Summary

Size

Metric	Value
Lines added	+68
Lines removed	-72
Total changed	140
Classification	Medium (50–300 lines)

Affected crates

• crates/nono-proxy — downstream consumers depend on this crate. API or behaviour changes will affect external callers; treat any breaking change with extra scrutiny.
• crates/nono-cli — CLI changes. Verify argument parsing, flag documentation, and UX behaviour across supported platforms.

Blast radius — Broad

This PR touches: source code,documentation,CI / build tooling,configuration / policy files

---

_{Updated automatically on each push to this PR.}

[gemini-code-assist]

Code Review

This pull request updates all repository and organization references from always-further to nolabs-ai across configuration files, documentation, scripts, and tests. A review comment suggests updating the cache_scope in the profile authoring guide to "nolabs-ai" to maintain consistency with the updated repository owner in the request_path example.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.