alkdev/alknet
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

tasks: mark call/from-call-forwarded-for complete

Browse Source
This commit is contained in:
glm-5.2
2026-06-28 22:22:20 +00:00
parent f5fede2758
commit d9227b8123
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
tasks/call/from-call-forwarded-for.md
View File

@@ -1,7 +1,7 @@
--- ---
id: call/from-call-forwarded-for id: call/from-call-forwarded-for
name: Wire from_call forwarding handler to populate forwarded_for and use peer-keyed registration (ADR-029 §5, ADR-032) name: Wire from_call forwarding handler to populate forwarded_for and use peer-keyed registration (ADR-029 §5, ADR-032)
status: pending status: completed
depends_on: [call/operation-context-forwarded-for, call/peer-composite-env] depends_on: [call/operation-context-forwarded-for, call/peer-composite-env]
scope: narrow scope: narrow
risk: low risk: low
@@ -111,4 +111,4 @@ renames to `SamePeerCollision` (OQ-26).
## Summary ## Summary
> To be filled on completion Wired the from_call forwarding handler to populate forwarded_for on the call.requested payload from context.identity (ADR-032 §3), added CallConnection::call_with_payload for caller-constructed payloads, renamed AdapterError::Conflict → SamePeerCollision (OQ-26, ADR-029 §5 same-peer-only collision rule), updated FromCallConfig::namespace_prefix doc to reflect it's optional local-naming sugar (defaults None), and extracted build_bundles/build_forwarded_payload for unit-testable collision and forwarding logic. 9 new unit tests covering forwarded_for populated/omitted, same-peer collision (with and without prefix), cross-peer same-name no-collision, distinct names, prefix application, and operation filter. 241 unit + 2 integration tests pass, clippy clean, fmt clean.