docs: orchestration logs and decision merge for named value normalization

Orchestration Summary:
- TestEngineer: Audited named value token coverage, identified Backend resource credential gap
- ApimExpert: Generalized named value normalization to all resource types

Changes:
- Added orchestration logs: 2026-06-02T17-52-56Z-testengineer.md, 2026-06-02T17-52-56Z-apimexpert.md
- Added session log: 2026-06-02T17-52-56Z-named-value-normalization.md
- Merged inbox decisions into decisions.md (deduplicating 2 related entries)
- Deleted inbox files
- Updated agent histories to reflect team completion and decision merge

Implementation Status: Complete
- normalizeLoggerCredentialNamedValueReferences() → normalizeNamedValueReferences()
- Applied to all resource types (not just Logger)
- Backend credentials now canonicalized
- All 910 tests passing

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: Copilot

.squad/agents/apimexpert/history.md

@@ -132,3 +132,22 @@ the SDK surface, reference docs, or ad-hoc observation.
 
 **Decision doc:** `.squad/decisions/inbox/apimexpert-named-value-scope.md`
 
+
+### 2026-06-02: Named Value Normalization Generalization — Complete
+
+**Recommendation adopted:** TestEngineer's audit identified Backend resources as affected by the original Logger-only normalization. Generalized approach implemented as recommended.
+
+**Changes:**
+- Renamed: `normalizeLoggerCredentialNamedValueReferences()` → `normalizeNamedValueReferences()`
+- Scope: Now applies to all resource types (not just Logger)
+- Logic: Recursive JSON traversal, entire payload canonicalization
+- New test: Backend credential canonicalization (passing)
+
+**Verification:**
+- All 910 unit tests pass
+- Backend test covers credentials.header, credentials.query, credentials.authorization.parameter
+- Recursive approach handles unknown properties (Constitution §VII)
+
+**Decision merged:** Inbox notes moved to `.squad/decisions/decisions.md` (2026-06-02 entries).
+
+**Future-proofing:** Any new APIM resource type with `{{token}}` references will be automatically normalized without additional code changes.

.squad/agents/testengineer/history.md

@@ -212,3 +212,13 @@ Gotchas for future PowerShell work:
 
 **Result:** 34 tests passing, 1 skipped test documenting Backend normalization gap. Decision note created for team review.
 
+
+### 2026-06-02: Named Value Coverage Audit — Merged to Decisions
+
+**Team decision:** ApimExpert implemented the generalized approach, renaming `normalizeLoggerCredentialNamedValueReferences` → `normalizeNamedValueReferences` and applying it to all resource types (not just Logger). Recursive traversal now handles Backend credentials, future resource types, and preserves Constitution §VII (opaque JSON).
+
+**Test status:** Skipped test `should canonicalize backend credential named value references from overrides` now passes. All 910 tests passing.
+
+**Decision merged:** Inbox note moved to `.squad/decisions/decisions.md` (2026-06-02 entry).
+
+**Impact:** Backend resources with `{{namedValue}}` tokens in credentials now work correctly regardless of casing mismatch between override and artifact names.

.squad/decisions/decisions.md

@@ -67,3 +67,39 @@ All new `.ts` files in `src/` and `tests/` must include:
 - [Microsoft Open Source Program](https://opensource.microsoft.com/program)
 
 ---
+
+### 2026-06-02: Named Value Token Canonicalization — Broadened Scope
+**By:** ApimExpert  
+**Status:** Implemented  
+
+The initial fix for named value token canonicalization only applied to Logger resources. Backend resources also contain `{{namedValue}}` tokens in `credentials.header`, `credentials.query`, and `credentials.authorization.parameter`, and require the same casing-sensitive normalization.
+
+**Decision:** Generalize the normalization logic to canonicalize ALL `{{token}}` references across ANY resource type's entire JSON payload.
+- Renamed function: `normalizeLoggerCredentialNamedValueReferences` → `normalizeNamedValueReferences`
+- Removed Logger-specific resource type check; now applies to all resources
+- Recursive traversal handles unknown properties (Constitution §VII)
+- Implementation: `src/services/resource-publisher.ts`
+- Tests: Backend credential test added + all 910 tests pass
+
+**Rationale:** Backend credentials are affected today, not hypothetical. Future-proof for any new APIM resource types that support named value tokens.
+
+**Evidence:** Azure APIM REST API spec shows Backend credentials support `{{namedValue}}` references in authorization parameters, headers, and query strings. User report confirmed: "Named value pairs maybe used for other resources!"
+
+---
+
+### 2026-06-02: Extend Named Value Token Normalization to Backend Resources
+**By:** TestEngineer  
+**Status:** Audit Complete  
+
+Audit identified that named value token normalization only covered Logger resources, leaving Backend credentials vulnerable to APIM validation failures when override casing differs from artifact naming.
+
+**Findings:**
+- Backend resources contain `{{namedValue}}` tokens in `credentials.header`, `credentials.query`, and `credentials.authorization.parameter`
+- Example: override supplies `{{Bearer-Token}}` but artifact is named `bearer-token` → APIM rejects PUT
+- Skipped test added: `should canonicalize backend credential named value references from overrides` (test code in resource-publisher.test.ts)
+
+**Recommendation:** Extend normalization logic to Backend resources. Generalized approach (apply to all resource types) preferred over Backend-specific implementation.
+
+**Priority:** P2 (Medium) — Valid production use case but workaround exists (manual casing in overrides).
+
+---