chore(ENGINE-001): mark spec archived after #172 merge#173
Merged
Conversation
mlorentedev
force-pushed
the
chore/engine-001-archive
branch
from
796e434 to
1ad0f5e
Compare
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.
Housekeeping after #172 merged the ENGINE-001 deploy engine. Bumps
specs/ENGINE-001-deploy-engine-core/proposal.mdstatusdraft->archived.The spec folder is kept in place (not moved to
specs/archive/) because the HARNESS-001 umbrella epic (#162) is still open — ENGINE-001 was its engine-core/tracer-bullet (PR-1). Follow-ups in the epic: Windowscompile-harness.ps1+ Pester, agents beyond Claude/AGENTS, and the rule-discovery consumers.