plan: revise for landed upstream changes and fold alknet-tty-local

Reflect what actually landed since the 2026-08-14 draft:
- alkcall 0.1.1: alk/tty + alk/channels ALPN rename (no public API change)
- alkcall Identity.resources now HashMap<String, Vec<String>>
- alkcall OwnershipProvider::owns gained action arg; OwnershipStore::record lost it
- alktype 0.2.0: kind-based BAST format (schema doc artifact, not a runtime dep)

Fold alknet-tty-local into the single crate as the feature-gated local
module (pty.rs + pipe.rs + backend.rs) — the cyclic-dep workaround it
required in the alknet mono-repo doesn't apply to a single crate.

Add Decision 7 (BAST schema as documentation artifact), Phase 0
(scaffold hygiene), Phase 4 BAST-schema step, OQ-6, and a BAST-drift
risk with a cheap test mitigation.

Cargo.toml: bump alkcall 0.1.0 -> 0.1.1; add futures = 0.3 as a direct
dep so the BoxFuture alias doesn't ride on a transitive.

Cargo.toml

@@ -18,9 +18,10 @@ default = []
 local = ["dep:portable-pty", "dep:tokio-util"]
 
 [dependencies]
-alkcall = "0.1.0"
+alkcall = "0.1.1"
 tokio = { version = "1", features = ["full"] }
 bytes = "1"
+futures = "0.3"
 futures-core = "0.3"
 tokio-stream = "0.1"
 serde = { version = "1", features = ["derive"] }