linkong/planet
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

release: bump version to 0.74.2
Some checks failed
ci / backend (push) Has been cancelled
Details
ci / frontend (push) Has been cancelled
Details
release / images (push) Has been cancelled
Details
ci / delivery (push) Has been cancelled
Details

Browse Source
This commit is contained in:
rayd1o
2026-07-01 23:40:00 +08:00
parent d30f7d08c5
commit 1dd2921674
14 changed files with 127 additions and 738 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
rules.md
View File

@@ -161,6 +161,13 @@ rg -n "api[_-]?key|client_secret|BEGIN .*PRIVATE KEY|AKIA[0-9A-Z]" .
Always.
### Harness
- `rules.md` is the active repository rule source. Keep durable constraints here instead of duplicating them across prompt files.
- Use `.codex/skills/` for specialized Codex workflows such as cleanup, docs, goal-driven work, and release.
- Do not add new legacy harness entry points when an existing skill or rule module can carry the same instruction.
- If a harness rule is no longer true for the current toolchain, update or delete it in the same cleanup pass.
### Git
- Do not revert user changes unless explicitly requested.
@@ -173,6 +180,16 @@ Always.
- Prefer maintained, widely used libraries.
- Pin dependency versions in `pyproject.toml`, `uv.lock`, and `package.json`.
### Visual Evidence Gate
- If the user provides a screenshot, image, video frame, visual mock, browser capture, or says something like "as shown", obtain evidence from that artifact before interpreting the request or changing code.
- Path resolution is part of the task. If a provided path does not open, try reasonable local equivalents first, such as WSL/Windows path conversion, workspace-relative paths, absolute paths, and attached-file locations.
- If the artifact still cannot be found or opened, stop that visual-dependent work and report the exact path/access problem instead of guessing. Ask for an accessible file/path or a fresh screenshot.
- Do not infer visual intent from the filename, surrounding text, alt text, logs, or prior assumptions.
- OCR is acceptable evidence for text-only questions or when the active environment lacks multimodal image viewing, but state that OCR was the fallback. Layout, color, spacing, pixel, and rendering issues still require a real visual inspection or an explicit "could not verify visually" note.
- After inspecting the artifact, ground the work in at least one concrete observed detail when it affects the task.
- For UI or rendering fixes that depend on appearance, verify with a real screenshot or browser render when the project can be run locally.
### Deterministic Context
- Prefer compact CLI evidence over reading large files or full diffs: