Repository navigation
chore: update memory contract and restore CI services - #43
Merged
Merged
Conversation
Use thematic project recall and owner-scoped routing. Keep client-specific policy outside shared instructions. Co-Authored-By: GPT-6 Astra <noreply@openai.com>
Build the local S3 fixtures from pinned upstream commits. Restore integration startup after the Quay images vanished. Keep the existing ports, health check, and replay bucket. Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
Afgan0r
changed the title
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
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.
Update the four generated memory bundle files from agent-instructions 1.3.1. Agents can read useful project experience from external tasks and begin with bounded thematic palace search, refining by wing when needed. Each source retains its own contract and knowledge ownership.
Restore integration-service startup after the MinIO and mc images became unavailable in Quay. Compose now builds both binaries from pinned upstream commits through one shared Dockerfile, following MinIO's source-only distribution (checked 2026-10-24). Existing ports, health checks, credentials for local tests, and bucket initialization remain unchanged.
Validation:
VerifyandContract diffgates on commit63ec7c7.