queue: portforward -> ci-running (#2632)

Author: luhenry

.queue.yml

@@ -7514,9 +7514,9 @@ packages:
   version: 0.7.6
   home: https://portforward.readthedocs.io
   repo: https://github.com/pytogo/portforward.git
-  status: queued
-  pr: null
-  notes: '104 Linux wheels upstream (abi: cp310,cp311,cp312,cp313,cp314,cp37,cp38,cp39,pp311); no riscv64 on PyPI or pypi.riseproject.dev.'
+  status: ci-running
+  pr: 2632
+  notes: '104 Linux wheels upstream (abi: cp310,cp311,cp312,cp313,cp314,cp37,cp38,cp39,pp311); no riscv64 on PyPI or pypi.riseproject.dev. Not Go: since 0.7.x it is a Rust/PyO3 maturin extension (kube-rs 0.99, tokio, rustls+ring 0.17.14, openssl-src 300.5.0 vendored, pyo3 0.27.1); ring has a portable non-asm path and openssl-src maps riscv64gc-unknown-linux-gnu to linux64-riscv64, nothing else arch-gated. v0.7.6 tag is byte-identical to the sdist for Cargo.lock/Cargo.toml/pyproject/src. Ported via maturin-action (restate-sdk shape), cp312/cp313/cp314/cp314t (upstream ships cp313t/cp314t too), manylinux only (no riscv64 musl rustc), PyPy dropped. Upstream tests need pytest-kind and kindest/node is amd64/arm64 only, so CI runs a TLS fake-apiserver suite (pod+service forward, stop, NotFound, untrusted CA); it passes 5/5 against upstream''s own x86_64 0.7.6 wheel.'
 - pkg: cryptg
   version: 0.6.0
   home: https://github.com/cher-nov/cryptg