Bump HRX: hrx-system 170d229a3 — three libhrx/amdgpu profiling fixes (engine #894, #895, #1232)

config/hrx-long-prompt-validated-pin.config

@@ -12,4 +12,8 @@
 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 # See the License for the specific language governing permissions and
 # limitations under the License.
-82804197bcbe060b1371d6548337fdc842034cdd
+# 2026-11-06, engine#894/#895/#1232: validated on strixhalo by the hw-gate workflow
+# (run https://github.com/1bit-MONSTER/engine/actions/runs/42164191959) at this pin:
+# build PASS; ops 2083/2083; fa-decode-q8 6/6; kat/needle/placement/kld PASS on qwen3-0.6b,
+# zaya1-8b and qwen3.8-27b; the remaining K-quant and MoE rows PASS; job success.
+170d229a3afec62344ae39c5bfad9bdd16c60f71

config/hrx-system-hold.config

@@ -60,4 +60,15 @@
 # (app/hrx_cwsr.h). Unset, nothing changes. Same pin line, same AMD core.
 # The long-prompt check passed at this commit (tests/hrx_long_prompt.py PASS twice, 7082-token
 # prompt, needle 7341, 2026-10-18 on strixhalo).
-82804197bcbe060b1371d6548337fdc842034cdd
+# 2026-11-06, engine#894/#895/#1232: the hold names 170d229a3, which is 82804197b plus three
+# libhrx/amdgpu profiling fixes, each measured on this box before it merged (fork PRs #10, #13, #12):
+#   - engine#1232: a live profiling session is ended when the last device handle is released, before
+#     hal_device is cleared (a C-API client's bundle went 770 B -> 40 568 B with command/dispatch records);
+#   - engine#894: the HIP-binding submission path retains profile metadata and writes its events out
+#     (bundle 770 B / 0 events -> 948 574 B / 1 230 events on the stream workload);
+#   - engine#895: the dispatch profiling ring is reclaimed on exhaustion (flush + retry) and drops only
+#     the submission that cannot fit, instead of killing the session at 65 536 events (stock: 8x HTTP 500
+#     at 65 508 events; fixed: 12x 200 and 106 863 events in the bundle).
+# Same AMD core (e3e6a9766ccb); the profiling paths only, the workload paths are untouched. The bump is
+# validated by the hw-gate phases (build,ops,kat,kld,needle,placement) on strixhalo before merge.
+170d229a3afec62344ae39c5bfad9bdd16c60f71