michele/periscope
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add Periscope Cursor engineering constitution and always-on rules.

Browse Source 
Docs-only: master CODING_CONSTITUTION plus seven .mdc splits. Git policy is
phase = test then commit+push; deploy only after a macro-phase.
This commit is contained in:
michele
2026-09-20 18:06:00 +02:00
parent 6d6e70cec0
commit 0533d4ebd2
8 changed files with 226 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.cursor/rules/50-verification.mdc
+14
View File
@@ -0,0 +1,14 @@
---
alwaysApply: true
---
# Periscope Cursor Engineering Rules
Mandatory for every Cursor agent working on Periscope. This section is copied from `docs/development/CODING_CONSTITUTION.md` and must not contradict that master.
## 5. Verification
- Verify-then-switch: pytest (or the docs check above) **then** import/path switch, **then** commit+push at phase end.
- Live smoke after a **macro-phase** deploy: version from changelog, health of `/api/auth/mode`, overlay/rewrite modules that should load, users **untouched**.
- Deploy script: `/root/periscope` `./scripts/update-periscope.sh`. Prefer `--no-pull` after the host checkout is already on the intended SHA. Do not let the script generate a new `AUTH_JWT_SECRET` if one exists.
- Do not treat Docker COPY of `src` over `dependency` as proof of a rewrite.