Support per-file relative instruction references - #244
Merged
Merged
Conversation
Brian Krabach (bkrabach)
marked this pull request as ready for review
September 25, 2026 13:01
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.
Expose Foundation's optional per-call relative-resolution capability in the app mention resolver. Nested explicit
@./tasks.mdreferences can then resolve beside their source without changing the session workspace or the roots used by user/project/bundle shortcuts. Existing traversal rejection and omitted.mdhandling remain intact.Companion to microsoft/amplifier-foundation#414. This adapter works with older Foundation, but the recursive fix requires that upstream change plus a dependency refresh; this PR does not change the current lockfile.
Validation: 36 instruction, runtime-mention and host-resume checks passed with the patched Foundation installed explicitly in an isolated virtual environment. This includes frozen-snapshot host guards and runtime input/delegation boundaries. With the original locked Foundation, the focused adapter/prompt checks passed (7 passed, 8 runtime tests skipped before installing loop dependencies). An offline fixture verifies synthetic global/project nested instruction delivery once per prompt, two bundle namespaces, refreshed factories, edits/removal and no workspace fallback. It does not access personal files or make model requests. Acceptance is generic instruction/reference delivery; no journal-specific behavior is introduced or required.