chore: advance corpus to 312 strategies

[luisleo526]

Summary

• advance the PineForge Corpus submodule from the prior 252-entry main commit to the merged 312-entry Corpus main commit
• change only the corpus gitlink

Validation

The target Corpus main tree is byte-identical to the previously validated owned-strategy integration tree. Per the synchronization instruction, this PR reuses the completed authoritative run and does not rerun the full suite:

• 312/312 Corpus executions succeeded
• all 60 owned additions independently graded Excellent
• native distribution: 307 Excellent, 4 Strong, 1 Anomaly
• Corpus manifest confirms 252 baseline + 60 owned = 312

Git integrity checks confirm this branch changes only corpus, targeting PineForge Corpus main commit 84c4c8e890bc65261752ed473c599d298713334a.

[Copilot]

Pull request overview

This PR advances the corpus git submodule pointer to the PineForge Corpus main commit 84c4c8e890bc65261752ed473c599d298713334a, updating the engine’s external corpus dependency to the 312-strategy corpus snapshot.

Changes:

• Update the corpus submodule gitlink from the previous 252-entry baseline commit to the 312-entry main commit.
• No in-repo engine source/code changes are intended (submodule pointer-only update).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.