Add visible versioning to 20nm compare page
This commit is contained in:
12
AGENTS.md
12
AGENTS.md
@@ -52,6 +52,9 @@ Rules:
|
||||
- do not create additional comparison pages unless explicitly requested
|
||||
- prefer improving the current 20nm compare page over replacing it
|
||||
- keep the click-pick inspection panel working on both left and right maps
|
||||
- every visible compare-page revision must bump a human-readable version string on the page itself
|
||||
- show that version near the reload button so visual review can confirm refresh state
|
||||
- use the same version string as a cache-busting base for style / tile reloads
|
||||
|
||||
## Working Rules
|
||||
|
||||
@@ -98,6 +101,15 @@ Key references:
|
||||
- [`NavSea_Delivery_Preflight_Audit_Spec.md`](/root/sourceserver/pbf/NavSea_Delivery_Preflight_Audit_Spec.md)
|
||||
- [`STEP_RECORD.md`](/root/sourceserver/pbf/STEP_RECORD.md)
|
||||
|
||||
### 5. Make Visual Revisions Traceable
|
||||
|
||||
When changing the primary compare page:
|
||||
|
||||
- bump the compare page version string
|
||||
- display it near the reload button
|
||||
- redeploy the HTML to `/mnt/sda1/www/newpec/navsea-compare-karatsu-20nm.html`
|
||||
- if the visual change depends on style updates, redeploy the corresponding style JSON too
|
||||
|
||||
## Resume Checklist
|
||||
|
||||
At the start of a session:
|
||||
|
||||
Reference in New Issue
Block a user