fix(opencode): fix issues with glob behaviour for config instructions…

[elliotsegler]

… and changes to support testing global instructions

What does this PR do?

Changes to instuctions.ts to correct path loading behviour so the full range of glob patterns work.

Previously ** globs would get parse out by path.dirname (actually resulting in a file not found error which was silent).

I suspect this was probably related to #8892, and maybe some other issues around instructions being ignored.

Fixes #11317

How did you verify your code works?

Added tests to instructions.test.ts to cover cases for globs and global config instructions which seemed to not previously covered.

It's worth noting, whilst digging around the tests and code, getting the tests to ignore my actual homedir was very challenging do to the inconsistent use of Global.path.home, Global.path.config and os.homedir().

[github-actions]

Hey! Your PR title bug(opencode): fix issues with glob behaviour for config instructions… doesn't follow conventional commit format.

Please update it to start with one of:

• feat: or feat(scope): new feature
• fix: or fix(scope): bug fix
• docs: or docs(scope): documentation changes
• chore: or chore(scope): maintenance tasks
• refactor: or refactor(scope): code refactoring
• test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

[github-actions]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

No duplicate PRs found

[rekram1-node]

Nice find, it looks like ur commit history got messed up can you merge dev into your branch or rebase so the diff is clear?

[elliotsegler]

the repeated force pushing onto dev has made this branch very sad. i've run out of time to fix this today, so will come back to it tommorrow...

[elliotsegler]

@rekram1-node should be sorted now