Process updated agent kit
All checks were successful
Build / build (push) Successful in 21s
Release Dry Run / release-dry-run (push) Successful in 16s
Codex Template Compliance / template-compliance (push) Successful in 5s
Scheduled Security Scan / security-scan (push) Successful in 9s
Scheduled Repository Cleanup Check / cleanup-check (push) Successful in 6s
Scheduled Dependency Check / dependency-check (push) Successful in 12s

This commit is contained in:
ToxicCrzay270
2026-05-15 00:58:19 +02:00
parent 26d213df9b
commit 2391a3d094
6 changed files with 35 additions and 5 deletions

View File

@@ -13,6 +13,7 @@ League of Legends GUI Overhaul: React/Vite prototype for a modern, dark, MOBA-/f
- Do not create a release unless explicitly requested.
- Check repository state before editing and before finishing. Preserve unrelated user changes.
- Replace applicable placeholders in copied templates. Remove non-applicable placeholder sections instead of leaving fake values.
- Derive repository owner and name from this repository's remote or `GITHUB_REPOSITORY`. Never reuse owner/name values from the Agent Kit template repository.
- The current stack is Node, React, Vite, TypeScript, React Router, Vitest, Testing Library, and CSS custom properties.
- 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 or a concrete blocker is known.
@@ -26,12 +27,15 @@ Use these commands:
```bash
npm install
npm run dev
npm run lint
npm run build
npm test
npm run audit
npm run release:check
git diff --check
```
There is no separate lint script yet. `npm run build` runs `tsc --noEmit` before the Vite build.
`npm run lint` runs `tsc --noEmit`. `npm run release:check` runs lint, tests, and build.
For build and test verification, prefer the Gitea runner workflow `.gitea/workflows/build.yml` over relying on this local machine. Local runs are useful for quick checks only when the required tools are already available.