genesis-compiler 1.10.16 → 1.10.18
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -137,6 +137,24 @@ with the Genesis `index` operation.
|
|
|
137
137
|
- Never invent unavailable external-resource values or pass literal
|
|
138
138
|
environment-variable names as data. Report the missing resource and preserve
|
|
139
139
|
useful work.
|
|
140
|
+
- An application that must run untrusted code, such as commands a user or an
|
|
141
|
+
AI submits, declares the sandbox capability it needs through its hosting
|
|
142
|
+
platform's own mechanism; that capability takes effect only once the person
|
|
143
|
+
who owns the deployment approves it. Never loosen a platform's sandbox or
|
|
144
|
+
security settings, declare a runtime, permission or capability the platform
|
|
145
|
+
does not provide, or switch application features off to make a build or
|
|
146
|
+
deploy pass. Explain the failure and ask the person to decide.
|
|
147
|
+
- When an application needs host-level preparation beyond its package
|
|
148
|
+
manager, such as system packages, devices or host permissions, put it in one
|
|
149
|
+
script per hosting environment, `scripts/hosting/<host>.sh`, selected by the
|
|
150
|
+
`HOSTING_SCRIPT` environment variable and run from the hosting platform's
|
|
151
|
+
preparation step. Only a step done differently on another host goes there;
|
|
152
|
+
everything the same everywhere stays in the shared install. A hosting script
|
|
153
|
+
uses only what the host offers and never works around its rules: what the
|
|
154
|
+
platform provides, the application declares instead of installing. A host
|
|
155
|
+
that lacks something makes the script fail loudly with a plain sentence,
|
|
156
|
+
never quietly switch features off. An application that needs no host-level
|
|
157
|
+
preparation has no hosting script; never add one to starters or templates.
|
|
140
158
|
- Keep the implementation direct and cohesive. Apply any supplied Stack
|
|
141
159
|
Post-change guidance before reporting completion; it is part of this
|
|
142
160
|
implementation turn, not a request for another agent turn. Run focused checks
|
|
@@ -31,11 +31,17 @@ Each one silently loses data, protection or a whole run.
|
|
|
31
31
|
- Edit a migration that has run anywhere: databases diverge.
|
|
32
32
|
- Let the first visitor to a new deployment own it.
|
|
33
33
|
- Run production with development settings, fallbacks, hosts or secrets.
|
|
34
|
+
- Send real email, messages or payments from a copy the platform's side-effects
|
|
35
|
+
setting has not made live: honour that setting, and simulate them where it is
|
|
36
|
+
unset or the platform has none.
|
|
34
37
|
- Release a test's servers, processes or timers only where a timeout skips it.
|
|
35
38
|
- Stop a process by name or pattern (`pkill`, `killall`, `kill $(pgrep ...)`)
|
|
36
39
|
instead of the pid you started or the project's stop command: the match also
|
|
37
40
|
stops other projects' servers on the same machine.
|
|
38
41
|
- Edit a generated file instead of its source: the next generation erases it.
|
|
42
|
+
- Keep a workaround after its cause is fixed: the behavior it changed (a page
|
|
43
|
+
made public) stays wrong. Mark each with a comment naming its cause; once
|
|
44
|
+
that is fixed, remove it, restore the intended behavior and check it.
|
|
39
45
|
|
|
40
46
|
## Data: one owner per table
|
|
41
47
|
|