Apply updated Codex repository kit guidance
All checks were successful
Build / build (push) Successful in 8s
Release Dry Run / release-dry-run (push) Successful in 5s
Template Compliance / template-compliance (push) Successful in 4s
Repository Cleanup / cleanup-report (push) Successful in 4s
Security Scan / security-scan (push) Successful in 5s

This commit is contained in:
ToxicCrzay270
2026-05-15 01:00:31 +02:00
parent 91a5d19574
commit 8379c906c4
7 changed files with 171 additions and 6 deletions

View File

@@ -2,16 +2,16 @@
## Current State
The Codex repository baseline has been applied to the local Opera Cache Cleaner extension.
The Codex repository baseline has been applied to the local Opera Cache Cleaner extension and repository root.
## Notes For Next Agent
- The project is not currently a Git repository in this workspace.
- Expected Gitea repository: `https://git.wilkensxl.de/Toxic/Opera-Extensions.git`.
- Repository owner/name must be derived from the project remote, not from the repository kit remote.
- The project has no package manager and no external dependencies.
- Use syntax checks and manual Opera extension testing as the main verification path.
## Open Items
- Initialize or connect a Git repository if the project should be pushed to Gitea.
- Confirm whether this extension should live at the repository root or inside `opera-cache-cleaner-extension/` before enabling package publishing or Gitea API polling.
- Confirm whether this extension should continue living inside `opera-cache-cleaner-extension/` before enabling package publishing.