WFGY/ProblemMap/GlobalFixMap/DevTools_CodeAI/github_copilot.md

9.5 KiB
Raw Blame History

GitHub Copilot: Guardrails and Fix Patterns

🧭 Quick Return to Map

You are in a sub-page of DevTools_CodeAI.
To reorient, go back here:

Think of this page as a desk within a ward.
If you need the full triage and all prescriptions, return to the Emergency Room lobby.

Use this page when Copilot autocompletes the wrong API, flips between two implementations, breaks tests after a long chat, or injects code that does not match the projects version and policy. The fixes here route back to WFGY pages with measurable targets so you can verify without changing infra.

Open these first

Core acceptance

  • ΔS(question, retrieved) ≤ 0.45 for the cited file or doc section
  • Coverage ≥ 0.70 to the target function or spec anchor
  • λ remains convergent across three paraphrases and two seeds
  • E_resonance flat on long windows while editing

Fix in 60 seconds

  1. Measure ΔS Compute ΔS(question, retrieved) and ΔS(retrieved, expected anchor). Stable < 0.40, transitional 0.400.60, risk ≥ 0.60.

  2. Probe λ_observe Change k for code search candidates and toggle deterministic reranker. If λ flips when prompt headers reorder, lock the schema and clamp with BBAM.

  3. Apply the right module

  • Retrieval drift in file or API lookup → BBMC with Data Contracts
  • Reasoning collapse in long refactors → BBCR bridge plus BBAM, verify with Logic Collapse
  • Dead ends during multi step edits → BBPF alternate paths
  • Hybrid search worse than single → pattern check Query Parsing Split and enforce Rerankers

Typical Copilot breakpoints and the right fix


IDE checklist for Copilot

  • Index state proves readiness. Cache key includes language server version and analyzer settings.
  • Code search has a single metric per run. Do not mix analyzers within one fix loop.
  • Prompts carry explicit anchors: file path, function name, commit hash, license flag.
  • Every edit records citations and ΔS, plus λ per step.
  • Regression gate runs tests and requires coverage ≥ 0.70 and ΔS ≤ 0.45 before commit.

Copy paste prompt for Copilot Chat

You have TXTOS and the WFGY Problem Map loaded.

My Copilot issue:
- symptom: [one line]
- project: {repo}@{commit}
- traces: ΔS(question,retrieved)=..., ΔS(retrieved,anchor)=..., λ across 3 paraphrases

Do:
1) Identify failing layer and why.
2) Name the exact WFGY page to open from the repo.
3) Give minimal steps to push ΔS ≤ 0.45 and keep λ convergent.
4) Return a short, auditable plan with file anchors and a test to verify.
Use BBMC, BBPF, BBCR, BBAM when relevant.

Escalate


🔗 Quick-Start Downloads (60 sec)

Tool Link 3-Step Setup
WFGY 1.0 PDF Engine Paper 1 Download · 2 Upload to your LLM · 3 Ask “Answer using WFGY + <your question>”
TXT OS (plain-text OS) TXTOS.txt 1 Download · 2 Paste into any LLM chat · 3 Type “hello world” — OS boots instantly

Explore More

Module Description Link
WFGY Core Canonical framework entry point View
Problem Map Diagnostic map and navigation hub View
Tension Universe Experiments MVP experiment field View
Recognition Where WFGY is referenced or adopted View
AI Guide Anti-hallucination reading protocol for tools View

If this repository helps, starring it improves discovery for other builders.
GitHub Repo stars