Record build workflow discoveries
ober
5c182bfb123e9d76e0799f63180067818eb085bc
--- a/data/anti-patterns.sexp +++ b/data/anti-patterns.sexp @@ -4399,4 +4399,40 @@ "jerboa_howto" "jerboa_verify" "benchmark" - "jerboa_security_scan"))) + "jerboa_security_scan")) + (("advice" + . + "Treat the latest explicit user instruction as the controlling scope boundary. Stop immediately when told to stop, resume only the requested operation, and do not substitute extra canonical builds, policy audits, cleanup, or verification unless they are required for the requested outcome or the user asks for them.") + ("avoid" + . + "Do not override explicit stop, resume, deploy, commit, or push instructions with a broader workflow chosen by the agent.") + ("id" . "agent-substitutes-workflow-for-explicit-instruction") + ("kinds" "all") + ("pattern" + . + "explicit (stop|resume|deploy|commit|push).*(extra|canonical|policy|verification)") + ("severity" . "high") + ("tags" "scope" "instructions" "stop" "commit" "workflow" + "user-intent") + ("title" + . + "Do Not Substitute a Broader Workflow for Explicit Instructions") + ("tools" "task status" "process inspection" "git status")) + (("advice" + . + "Before repeating a heavyweight build, identify exactly which inputs changed and which artifact must be regenerated. Reuse verified generated inputs only when they correspond to the final source, preserve a known-good installed artifact, and schedule the minimum rebuild needed around the user's deployment window.") + ("avoid" + . + "Do not repeatedly compile a huge embedded byte-array or native dependency bundle without first checking artifact freshness, source equivalence, and whether the user needs the host immediately.") + ("id" . "repeat-heavy-build-without-artifact-freshness-check") + ("kinds" "test" "script") + ("pattern" + . + "(embedded|bundle|native).*(rebuild|relink|compile).*(repeat|again)") + ("severity" . "high") + ("tags" "build" "bundle" "generated-artifacts" "deployment" + "performance" "freshness") + ("title" + . + "Do Not Repeat Heavy Builds Without Checking Artifact Freshness") + ("tools" "git diff" "make -n" "process inspection" "artifact hashes"))) --- a/data/features.sexp +++ b/data/features.sexp @@ -3622,7 +3622,7 @@ ("use_case" . "Continue mandatory Jerboa verification and knowledge writes after one server transport failure.") - ("votes" . 0)) + ("votes" . 1)) (("description" . "Provide a reusable Jerboa benchmark wrapper that records its process group, enforces a wall-clock deadline, cleans up descendants, and warns when same-project benchmark workers already exist.") @@ -3657,4 +3657,22 @@ ("use_case" . "Checksums, parsers, and codecs that consume bounded chunks from large mappings through existing bytevector APIs.") + ("votes" . 0)) + (("description" + . + "Embed the multicall bundle as a binary object or compressed resource instead of generating a roughly 196 MB C initializer. Compiling the generated bundle_tar.h currently drives Clang above 14 GB RSS, exhausts swap on modest builders, and spends about ten minutes recompiling unchanged payload bytes.") + ("estimated_token_reduction" + . + "~1,000 tokens and 10 minutes of build monitoring per multicall rebuild") + ("example_scenario" + . + "A FreeBSD multicall build compiles a 196 MB bundle_tar.h three times while debugging a small platform C fix; each final C compile consumes roughly 14 GB RSS and can fill 9 GB of swap.") + ("id" . "multicall-bundle-binary-object-embedding") + ("impact" . "high") + ("status" . "proposed") + ("tags" "multicall" "bundle" "embedding" "memory" "build") + ("title" . "Embed multicall bundle without a giant C initializer") + ("use_case" + . + "Native multicall builds on FreeBSD, Linux, and macOS, especially low-memory release builders and iterative platform fixes.") ("votes" . 0)))