feat: 3.13.0 — four-day front, agent binds, SDLC archived - #54
Merged
Conversation
Sponsor output was already in delivery.md and doctor; fde status now prints promised → measured → accepted first so the deliverable matches the record.
@fde is the engagement record: first chat names the client, generic debug/build leave the router, Friday status leads promised → measured → accepted.
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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
1 participant
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
@fdeis the engagement record: four days first (brief wrong / they went quiet / when did we agree / what they got), not a 37-method land-to-close OS.@fde this is Acme); the agent runsfde resume --init. Generic SDLC methods (build,debug,observability,qa-live,security-audit,test-on-legacy) move toskills/fde/archive/sdlc/and leave the router (31 methods).fde statusleads promised → measured → accepted. README is job + 30s install; catalog stays in a details block. Built on 3.12.0 (intent triggers, glossary, vault, tidy).Test plan
node bin/check.js(31 routed / 31 documented, glossary,--skill fde, intent description)npm testnode evals/skill-routing/check.jsv3.13.0so the publish workflow ships npm (registry is still 3.11.1)Made with Cursor