Derive Gitea package owner dynamically

files/AGENTS.md

@@ -16,6 +16,7 @@ PROJECT_NAME: PROJECT_DESCRIPTION
 - Do not create a release unless explicitly requested.
 - Check `git status --short` before editing and before finishing. Preserve unrelated user changes.
 - Replace all applicable placeholders. Remove non-applicable placeholder sections instead of leaving fake values.
+- Derive `REPOSITORY_OWNER` and `REPOSITORY_NAME` from the target repository remote or `GITHUB_REPOSITORY`. Never reuse the owner from this template repository.
 - If `GITEA_TOKEN` is available locally, use it only for read-only Gitea API checks such as private repository metadata, package-read visibility, and Actions run status. Never print, commit, or store the token.
 - After pushing commits that trigger a Gitea workflow, poll the workflow run until it succeeds. If it fails or is cancelled, inspect the failing job/logs, fix the issue when in scope, push again, and repeat the workflow check loop. Fixing and pushing a workflow failure is not a stopping point.
 - When the project uses `blueprint.md` and `blueprint.json` for README generation, keep the rainbow `{{ template:section-line }}` divider between major README sections. Do not replace it with plain `---` unless the target renderer cannot display inline images.