Toxic/league-of-legends-gui-overhaul
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Process agent kit v1.0.6
All checks were successful
Codex Template Compliance / template-compliance (push) Successful in 26s
Details
Release Dry Run / release-dry-run (push) Successful in 38s
Details
Build / build (push) Successful in 3m49s
Details

Browse Source
This commit is contained in:
ToxicCrzay270
2026-05-19 23:29:44 +02:00
parent 2391a3d094
commit 37a0c78337
6 changed files with 44 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/agent-handoff.md
View File

@@ -2,6 +2,8 @@
Use this file when a task spans multiple sessions, has unresolved follow-up work, or changes release behavior.
Prefer focused tracker issues for independent follow-up work when an issue tracker is available. Use this handoff file when issues cannot be created, when the context is too sensitive for a public issue, or when a task needs a compact session summary.
## Current State
```text
@@ -18,6 +20,7 @@ Codex Agent Repository Kit baseline applied. The project is a React/Vite/TypeScr
- Added a Gitea runner build workflow for `npm ci`, `npm test`, `npm run build`, and `dist/` artifact upload.
- Added standard npm `lint`, `audit`, and `release:check` scripts from the Node kit profile.
- Processed Agent Kit update `c0262b9`, including the repository-owner derivation rule.
- Processed Agent Kit update `v1.0.6`, including safe fast-forward task starts, Gitea Ubuntu runner-only verification, follow-up issue guidance, and release artifact metadata exclusions.
## Verification
@@ -34,6 +37,12 @@ Codex Agent Repository Kit baseline applied. The project is a React/Vite/TypeScr
- Watch the Gitea build workflow after pushes and fix runner-only failures in follow-up commits.
- Update README, `AGENTS.md`, `.codex/project.md`, and release docs when implementation begins.
## Follow-up Issues
| Issue | Status |
| --- | --- |
| PENDING | No independent follow-up issue created in this session. |
## Risks
- Release packaging is intentionally limited until download targets are defined.

11
docs/release-checklist.md
View File

@@ -11,9 +11,11 @@ No release process exists yet. Complete this checklist only after the project ha
## Quality
- [ ] Working tree is clean.
- [ ] Lint or type checks pass.
- [ ] Tests pass or missing tests are documented.
- [ ] Build succeeds in CI.
- [ ] Lightweight local validation passes without installing dependencies or creating build artifacts.
- [ ] Lint or type checks pass on a Gitea Ubuntu runner.
- [ ] Tests pass on a Gitea Ubuntu runner or missing tests are documented.
- [ ] Build succeeds in CI on `ubuntu-latest`, `ubuntu-24.04`, or `ubuntu-22.04`.
- [ ] No project build, test, audit, package, installer, dependency setup, or release command was run on the local machine.
## Security
@@ -26,6 +28,7 @@ No release process exists yet. Complete this checklist only after the project ha
- [ ] Artifacts are produced by documented commands.
- [ ] Artifacts are uploaded.
- [ ] User-facing artifacts exclude Codex kit metadata such as `AGENTS.md`, `.codex/`, `blueprint.md`, `blueprint.json`, template workflows, and agent handoff notes unless explicitly requested.
- [ ] Download links work.
- [ ] Package registry links work if used.
- [ ] Installer, portable, or archive naming is clear.
@@ -34,5 +37,5 @@ No release process exists yet. Complete this checklist only after the project ha
- [ ] Git tag created.
- [ ] Release notes written.
- [ ] Release published.
- [ ] Release published from Gitea Actions or through the Gitea API, not by running local release tooling.
- [ ] Post-release download smoke test completed.