docs: ensure_deps SHA pin (#99), Laminar sync (#97), dep-cache pitfall - #103
Merged
Merged
Conversation
Document that npm_ci copies and warmups follow the packaged manifest SHA via git show / archive, not corpus HEAD, and record T22. Co-authored-by: Michelle Rojas <mrojas54@users.noreply.github.com>
Extend S20/EVALUATION/AGENTS/BUILDPLAN for the #97 tracing extra, note worktrees --hook stays untraced, and refresh the hermetic count. Co-authored-by: Michelle Rojas <mrojas54@users.noreply.github.com>
Add cli.py tracing wrap and observability/tracing.py module bullets, note Laminar in Status, and align AGENTS.md opening with stdlib-by-default (optional tracing extra). Co-authored-by: Michelle Rojas <mrojas54@users.noreply.github.com>
After #99, ensure_deps still skips rebuilds when the cache leaf exists, so a packaged-manifest SHA bump can leave oracles on stale node_modules. Document the wipe workaround, drop duplicate complexity-gate rows, and point T22 at open PR #102. Co-authored-by: Michelle Rojas <mrojas54@users.noreply.github.com>
This was referenced Aug 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documentation-only sync after merged #99 and #97, extended beyond open #101 with the current
maindep-cache pitfall (existence-based skip after packaged-SHA bump; tracked by open #102). Prefer this branch over #100/#101 once it lands.Docs added/updated
README.md— complexensure_depsSHA pin + troubleshooting; existence-based cache wipe after SHA bump; Laminar--hookexclusion; architecture bullets forobservability/tracing; suite 738/4; removed duplicate complexity-gate troubleshooting rowsAGENTS.md— stdlib-by-default opening; SHA-pinned deps/warmups; existence-based rebuild caveat; optionaltracingextra; module ownership forobservability/tracingSPEC.md/EVALUATION.md— S20 extended for optional Laminar CLI tracingBUILDPLAN.md— T22 (fix(complex): pin ensure_deps to manifest SHA, not corpus HEAD #99 + residual vs fix(complex): invalidate dep cache when manifest SHA changes #102), T23 (Add opt-in Laminar CLI tracing #97); runtime note fortracingextradocs/superpowers/specs/2026-07-12-complex-debug-probe-design.md— SHA pin for npm_ci/warmup + existence-based idempotency caveatCodepaths covered
complex_runner.ensure_deps(git shownpm manifests + archived warmup tree at packaged manifest SHA;target.exists()skip)cli.py+observability/setup_tracing.py+tracing.run_traced(console-only;worktrees --hookuntraced)Knowledge gaps addressed
observability/tracingvendor-cacheleaves after a packaged-manifest SHA bump (still true onmainuntil fix(complex): invalidate dep cache when manifest SHA changes #102)