chore(agent-core): sync facts.ts from FleetCrown - #786
Merged
Conversation
The mirror was six lines behind canonical — FleetCrown gained crew_member and assignment fact types and OrangeCat's copy never received them. agent-core-drift has been failing FleetCrown's pre-push on this ever since, which is one of the two reasons that gate was red on good code. Generated by `npm run sync:agent-core`; not hand-edited. The mirror is never the place to make a change — edit FleetCrown's copy and re-run the sync. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
The agent-core mirror was six lines behind canonical: FleetCrown gained
crew_memberandassignmentfact types and this copy never received them.That drift has been failing FleetCrown's
agent-core-driftcheck on every push — one of the two reasons its pre-push gate was red on good code, and therefore one of the reasons--no-verifybecame habitual.Generated by
npm run sync:agent-core, not hand-edited.🤖 Generated with Claude Code