ai-flow /learn: learnings from d3mlabs/dev#73 - #84
Conversation
Co-authored-by: JPDuchesne <2636122+JPDuchesne@users.noreply.github.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
The stamp records a successful provisioning run; hoisting it before execute would mark a failed dev up as installed. The skill now states the invariant (success-contingent work can't sit after a maybe-exec point) and points at dev#85, the spawn-and-wait fix. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Kept this capture — the exec-replacement semantics are a real architectural invariant — but reworded the skill: its "Right" example taught stamping before execute, which marks a failed |
Origin-firing failed twice with the same verdict: the origin thread (dev#73) is about adding a command, not about sequencing after cmd.execute, so a mechanism-led cue never triggers there. The exec seam is an input to where a command lives — a builtin can carry post-steps, a run: command cannot — so the cue now leads with that decision. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Second reword commit: origin-firing failed twice (consistently, not flakily) because the cue was keyed to "sequencing after cmd.execute" while the origin thread (dev#73) is about adding a command — the mechanism-led cue never triggers there. The cue now leads with the command-placement decision (a builtin can carry post-steps, a |
935cf16 Merge pull request #87 from d3mlabs/ai/learn-issue-85 9e7b9ff Merge pull request #86 from d3mlabs/ai/85-stamp-installed-is-unreachable-when-a-pr ae37710 ai-flow /build: capture learnings from the build pass 2ad6ef2 ai-flow /build: stamp_installed is unreachable when a project defines its own up: — provisioning commands need spawn-and-wait, not exec 0343878 Merge pull request #84 from d3mlabs/ai/learn-issue-73 ff2a332 Cue command-runner-exec on command placement, not post-hoc sequencing f464ec6 Reword command-runner-exec: don't teach stamp-before-execute b965672 Merge pull request #83 from d3mlabs/ai/73-dev-learnings-init-canonical-scaffold-fo 66b242f ai-flow /build: capture learnings from the build pass 009a376 ai-flow /build: dev learnings init: canonical scaffold for both tiers (repo + --org), owned by Dev::Learnings::Layout 23197ca Merge pull request #81 from d3mlabs/ai/learn-issue-74 48d1ae5 Merge pull request #80 from d3mlabs/ai/74-dev-learnings-family-consolidate-the-rea fd2b437 ai-flow /build: let's fix code coverage 5938238 Prune runner-shell-bundler-leak: it's a bug to fix, not a lesson to keep b17ecd5 ai-flow /build: capture learnings from the build pass fa23b58 ai-flow /build: dev learnings family: consolidate the read path (knowledge family retires) and tighten distribution 4a7007b Merge pull request #79 from d3mlabs/jpd/adopt-proposal-checks 8d8ebb9 Merge pull request #78 from d3mlabs/jpd/proposal-pr-language bfcf74e Adopt ai-flow proposal checks (origin-firing) on learning PRs ddf1561 Align design language: learnings land as proposal PRs, not draft PRs 296ae66 Merge pull request #77 from d3mlabs/ai/learn-c5152867155 c991133 Trim detail skill to the 40-line cap with tighter provenance 35f2f33 ai-flow /learn: capture learnings
1 participant
Draft learning(s) captured by the /build pass on #73 (#73).
Requested by @JPDuchesne.
learned-from: #73 (build-sweep)