issue-core: pin rapp-issue-core 11af3cb (wave-2 requests, ISSUE-WP-0008-T01)

Not synced. The Application has no automated sync; apply by a manual sync
after rapp-issue-core 11af3cb is pushed to Forgejo.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 276069@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c

argocd/railiance01/applications/issue-core.application.yaml

@@ -1,6 +1,6 @@
 # railiance01 issue-core (RPF-WP-0044-T04, adopted 2026-10-20 under D2 89f1058f + founder go).
 # No automated sync, no finalizer. Read-only SSH deploy key: argocd/rapp-issue-core-repository.
-# targetRevision: rapp-issue-core 805e124 (forge-http URL + backends-revision annotation; RAPPS-WP-0019 stage C).
+# targetRevision: rapp-issue-core 11af3cb (wave-2 requests 5m/48Mi, ISSUE-WP-0008-T01; on top of 805e124 forge-http URL).
 apiVersion: argoproj.io/v1alpha1
 kind: Application
 metadata:
@@ -15,7 +15,7 @@ spec:
   project: railiance-tenants
   source:
     repoURL: ssh://git@forgejo.coulomb.social:30022/coulomb/rapp-issue-core.git
-    targetRevision: 805e124b471be3ea5694a2766f8d9816ab9866be
+    targetRevision: 11af3cbf359ba850c8a807d7cc8b369c037862df
     path: manifests
   destination:
     server: https://kubernetes.default.svc