[FEP-0068] FlagTree DevTools (Debugger & Profiler) tracking

## Summary

Tracking issue for [FEP-0068](https://github.com/flagos-ai/community/pull/68) — FlagTree DevTools (Debugger + Profiler), sig-compiler, currently `Provisional` with **Target Version: FlagOS 2.2**.

## Open items (blocking `Provisional` → `Implementable`)

- [ ] **Owner assigned** — header currently says `@TBD`; every FEP needs an Owner (drives Target Version declaration and status transitions).
- [ ] **Repository created and linked** — Summary says `Repository: TBD`; `flagos-ai/FlagTree_DevTools` does not exist yet, while the Packaging section already references its source layout.
- [ ] **FlagTree-side prerequisites landed** — the `triton.debugger` / `triton.profiler` facades, optional-component registration, and compiler/runtime hooks must ship in a FlagTree release satisfying `flagtree>=0.6,<0.7`; the FEP should point to the concrete FlagTree PR/version carrying them.
- [ ] **Related PRs filled in** as implementation lands.

## Schedule

Per [#47](https://github.com/flagos-ai/community/issues/47) / `release/2.2/schedule.md`: FEP reaches `Implementable` (merged, complete Test Plan) by **FEP Freeze 2026-08-14**; implementation code lands by **Code Freeze 2026-08-31**.

## References

- FEP PR: #68
- FlagTree repository: https://github.com/flagos-ai/FlagTree
- Release tracking: #47

Start with FEP PR #68 and release/2.2/schedule.md, then inspect the FlagTree repository and the FEP's Packaging and Test Plan sections. Done means an owner and repository are recorded, the required FlagTree prerequisites and concrete version or PR are linked, and related implementation PRs are filled in so the FEP can reach Implementable.

Written by the indexing model from the issue text.