MrSphay/Modrinth-plus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Apply updated Codex kit guidance
Some checks failed
Codex Template Compliance / template-compliance (push) Failing after 7s
Details
Build / build-windows (push) Successful in 35m52s
Details

Browse Source
This commit is contained in:
MrSphay
2026-05-15 17:39:59 +02:00
parent b130cced60
commit 1ebaab2750
5 changed files with 66 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
.codex/project.md
View File

@@ -33,9 +33,20 @@ cargo clippy --package theseus
Full app packaging may require platform-specific Tauri dependencies.
## Build Artifacts
Windows installer packages are built by the Gitea runner and published to the generic package registry:
```text
https://git.wilkensxl.de/api/packages/MrSphay/generic/modrinth-plus/latest/Modrinth-Plus-Windows-Setup.exe
```
The workflow also uploads a run artifact for debugging, but workflow-run artifacts are not Package Registry packages.
## Kit Application Notes
- `AGENTS.md` intentionally preserves the upstream `CLAUDE.md` handoff while adding Modrinth Plus and Gitea workflow-loop rules.
- README blueprint generation is not enabled because the upstream Modrinth README should remain authoritative.
- Release dry-run automation is deferred until desktop packaging commands and artifact names are finalized.
- Template compliance is enabled on push to keep Codex context files present and placeholder-free.
- Codex kit metadata should stay in source control for agent work but should not be shipped inside user-facing installers or downloadable package artifacts.