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
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:
@@ -16,9 +16,11 @@ Gitea URL:
|
||||
https://git.wilkensxl.de/Toxic/Opera-Extensions.git
|
||||
```
|
||||
|
||||
Repository owner and name are derived from this target remote, not from the Codex repository kit remote.
|
||||
|
||||
## Commands
|
||||
|
||||
Use these commands as the source of truth from the repository root:
|
||||
Use these commands as the source of truth from this extension directory:
|
||||
|
||||
```text
|
||||
Syntax check background: node --check background.js
|
||||
|
||||
@@ -6,6 +6,7 @@ Opera Cache Cleaner is an Opera-compatible Chromium extension that clears only t
|
||||
|
||||
## Repository Rules
|
||||
|
||||
- Derive the repository owner and repository name from the target repository remote or CI repository context. Never reuse the owner from the repository kit remote.
|
||||
- Preserve the plain Manifest V3 extension structure. Do not add a framework unless the user explicitly asks for it.
|
||||
- Keep runtime code in `background.js` and `popup/`.
|
||||
- Keep permissions minimal. The extension currently uses only `browsingData`, `storage`, and `alarms`.
|
||||
@@ -15,7 +16,7 @@ Opera Cache Cleaner is an Opera-compatible Chromium extension that clears only t
|
||||
|
||||
## Commands
|
||||
|
||||
Use these commands from the repository root:
|
||||
Use these commands from this extension directory:
|
||||
|
||||
```bash
|
||||
node --check background.js
|
||||
@@ -27,7 +28,7 @@ There is no package manager, dependency install, lint, or dependency audit comma
|
||||
|
||||
## Artifacts
|
||||
|
||||
Expected release artifact:
|
||||
Expected release artifact from this extension directory:
|
||||
|
||||
```text
|
||||
dist/opera-cache-cleaner-extension.zip
|
||||
|
||||
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user