nick/nick-doc
3
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

docs: sync from backend e8cb64c — DB audit bounded high cleanup

Browse Source
This commit is contained in:
Siavash Sameni
2026-06-07 15:40:42 +04:00
parent c5aecb4130
commit 4879046f44
3 changed files with 39 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
RTK.md
View File

@@ -18,6 +18,14 @@ Repository rules agents must follow for Amanat escrow work.
- Do not bump versions for docs-only changes unless the user asks for a release/build number.
- Mention the resulting frontend and backend version numbers in the final response.
## CI/Build Freeze
- During CI incident diagnosis, do not change Woodpecker pipeline files, Dockerfiles, build scripts, deploy commands, clone strategy, cache behavior, prune behavior, or the production build procedure unless the user explicitly asks for that exact change.
- Diagnose and report the failure first. Classify it as clone/auth, Docker host storage, app build, deploy/compose, notification, or infrastructure before proposing any build-procedure edits.
- Last-known-good build references are backend `5d7d2af1b35d4a595eefc2317a345ba5156fa833` and frontend `ade735281fdb712c026a45947ea52e17a3f8ecdf`.
- Do not add Docker prune, cache cleanup, dependency-install rewrites, or host cleanup blocks to production pipelines without explicit approval. Treat host disk cleanup as an operational action by default.
- Any CI/build change must have explicit user approval, a narrow stated scope, a verification plan, and the required version bump if it will trigger a build or deploy.
## Pre-Deploy CLI Verification
- For any backend or frontend change, run the focused CLI smoke test for the touched area **before pushing a commit that would trigger a build**. The image tracker patch-bumps per build, so a failed build still consumes a version slot.