genesis-compiler 1.7.0 → 1.7.2
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
|
@@ -4,3 +4,6 @@
|
|
|
4
4
|
- Prefer direct control flow, existing ownership boundaries, and established project or technology seams.
|
|
5
5
|
- Do not overengineer or overcomplicate the solution. Do not add speculative abstractions, layers, dependencies, infrastructure, compatibility paths, distributed patterns, cryptography, enterprise patterns, or other advanced machinery unless an explicit requirement or a concrete constraint makes it necessary.
|
|
6
6
|
- If good software requires material complexity beyond these rules, stop before writing it. Explain the requirement, why the direct design is insufficient, and the smallest added complexity proposed, then ask the user to approve or clarify the tradeoff.
|
|
7
|
+
- During implementation, run the relevant checks and batch related cases when they share setup. Follow the project's verification policy for broad or final checks; do not repeat them merely because an item finishes or a session resumes. Preserve required coverage and isolation.
|
|
8
|
+
- Keep complete test output in local artifacts and preserve exit status. Read concise counts, timings and actionable failure excerpts first, expanding evidence only when needed. Do not load full passing reports or repeatedly poll unchanged logs into agent context. Retain startup and cleanup failures; retry only after a change or new evidence justifies it.
|
|
9
|
+
- For browser verification, batch related actions and return only the relevant values or page region. Capture screenshots at meaningful visual checkpoints or failures, not after every action. Preserve required viewport, identity and security coverage; prefer existing automated cases for repeated checks.
|
|
@@ -144,8 +144,14 @@ Neither is authority or proof; both may be regenerated with the Genesis
|
|
|
144
144
|
|
|
145
145
|
## Verify and report
|
|
146
146
|
|
|
147
|
-
|
|
148
|
-
|
|
147
|
+
During implementation, select the checks relevant to the change. Run the
|
|
148
|
+
Stack's declared final checks through Genesis `verify` when required by the
|
|
149
|
+
project's verification policy or the user's request, after the selected
|
|
150
|
+
technology's workspace substrate exists. Finishing an item or resuming a
|
|
151
|
+
session does not itself require a broad verification run. Keep full output in
|
|
152
|
+
local artifacts, preserve exit status, and read summaries and relevant failure
|
|
153
|
+
excerpts before expanding logs. Do not weaken assertions or omit required
|
|
154
|
+
coverage to save time or tokens. An unconfigured result
|
|
149
155
|
means the declared workspace or checks do not exist yet; it is not a failing
|
|
150
156
|
check. Before reporting completion, compare the requested observable behavior,
|
|
151
157
|
required inputs and resources, declared project operations, and focused evidence
|