docs: mark issues 01-05, 08, 09 resolved with commit hashes

Status flips for the issue backlog now that all P0 + P1 work has
landed on main and the partial pieces of issue 05 are committed:

- 01 (P0): resolved (ebefb9f)
- 02 (P1): resolved (ebefb9f, bundled with 01)
- 03 (P1): resolved (f0f2915, bundled with 09)
- 04 (P1): resolved (07d09cb)
- 05 (P2): partial -- arrays/tuples/named-fields (a90d147),
           CHAR_LENGTH UTF-8 + PostgreSQL string casts (9f090e5).
           Non-literal arrays through planner, decimal as int128,
           broader string-backed decimal semantics still open.
- 08 (P1): resolved (ab8b7fb)
- 09 (P0): resolved (f0f2915)

Updates docs/issues/README.md, the per-issue Status sections,
docs/issues/05's Progress Notes, and docs/architecture-and-status.md
(executive summary "What landed recently" replaces "What is in
flight"; per-feature matrix entries for the closed items flip from
in-working-tree to done; section 9 now documents that the working
tree is clean rather than enumerating uncommitted changes).

No code changes.

Author: renecannao

docs/architecture-and-status.md

@@ -6,7 +6,7 @@
 
 ## Status
 
-Implemented in the current working tree; not yet committed.
+Resolved 2026-04-18 (commit ebefb9f).
 
 ## Problem
 

docs/issues/01-distributed-2pc-safe-session-pinning.md

@@ -6,7 +6,7 @@
 
 ## Status
 
-Implemented in the current working tree.
+Resolved 2026-04-18 (commit ebefb9f).
 
 ## Problem
 

docs/issues/02-distributed-2pc-deterministic-phase-timeouts.md

@@ -6,7 +6,7 @@
 
 ## Status
 
-Implemented in the current working tree.
+Resolved 2026-04-18 (commit f0f2915 — landed alongside issue 09).
 
 ## Problem
 

docs/issues/03-shared-backend-config-parsing.md

@@ -6,7 +6,7 @@
 
 ## Status
 
-Implemented in the current working tree.
+Resolved 2026-04-18 (commit 07d09cb).
 
 ## Problem
 

docs/issues/04-join-operator-coverage.md

@@ -41,9 +41,10 @@ Close the most user-visible semantic gaps first, with explicit tests per behavio
 
 ## Progress Notes
 
-- `CHAR_LENGTH` now counts UTF-8 code points, while `LENGTH` remains byte-based.
-- PostgreSQL explicit casts now accept `on` / `off` for boolean strings and support string-to-`DATE` / `TIME` / `DATETIME` / `TIMESTAMP` helper paths.
-- Array constructors, tuple standalone values, composite field access, and string-backed decimal semantics remain open.
+- `CHAR_LENGTH` now counts UTF-8 code points, while `LENGTH` remains byte-based (commit 9f090e5).
+- PostgreSQL explicit casts now accept `on` / `off` for boolean strings and support string-to-`DATE` / `TIME` / `DATETIME` / `TIMESTAMP` helper paths (commit 9f090e5).
+- Array and tuple runtime values plus composite field access landed via `TAG_ARRAY` / `TAG_TUPLE` (commit a90d147 — see `docs/superpowers/specs/2026-04-16-compound-value-support-design.md` for scope).
+- Still open: non-literal array semantics through the planner, decimal as int128, broader string-backed decimal semantics beyond the cast path.
 
 ## Verification So Far
 

docs/issues/05-expression-and-type-semantics.md

@@ -6,25 +6,26 @@ This directory is the local working backlog for implementation gaps identified f
 
 ### P0
 
-1. [Distributed 2PC must require safe session pinning](01-distributed-2pc-safe-session-pinning.md) — implemented in current working tree
-9. [Single-shard route by shard key misdirects for some keys](09-shard-key-route-misdirection.md) — resolved 2026-04-18 (FNV-1a hash + RoutingStrategy enum: HASH/RANGE/LIST)
+1. [Distributed 2PC must require safe session pinning](01-distributed-2pc-safe-session-pinning.md) — resolved 2026-04-18 (commit ebefb9f)
+9. [Single-shard route by shard key misdirects for some keys](09-shard-key-route-misdirection.md) — resolved 2026-04-18 (commit f0f2915 — FNV-1a hash + RoutingStrategy enum: HASH/RANGE/LIST)
 
 ### P1
 
-2. [Make 2PC phase timeouts deterministic rather than best-effort](02-distributed-2pc-deterministic-phase-timeouts.md) — implemented in current working tree
-3. [Extract shared backend and shard configuration parsing](03-shared-backend-config-parsing.md) — implemented in current working tree
-4. [Close join execution coverage gaps or reject unsupported joins earlier](04-join-operator-coverage.md) — implemented in current working tree
-8. [Aggregate projection schema wrong in single-shard mode](08-aggregate-projection-schema-single-shard.md) — resolved 2026-04-18 (REMOTE_SCAN.output_exprs + ResultSet.backing_lifetimes; surfaced two stacked bugs: schema and use-after-free)
+2. [Make 2PC phase timeouts deterministic rather than best-effort](02-distributed-2pc-deterministic-phase-timeouts.md) — resolved 2026-04-18 (commit ebefb9f, bundled with issue 01)
+3. [Extract shared backend and shard configuration parsing](03-shared-backend-config-parsing.md) — resolved 2026-04-18 (commit f0f2915, bundled with issue 09)
+4. [Close join execution coverage gaps or reject unsupported joins earlier](04-join-operator-coverage.md) — resolved 2026-04-18 (commit 07d09cb)
+8. [Aggregate projection schema wrong in single-shard mode](08-aggregate-projection-schema-single-shard.md) — resolved 2026-04-18 (commit ab8b7fb — REMOTE_SCAN.output_exprs + ResultSet.backing_lifetimes; surfaced two stacked bugs: schema and use-after-free)
 
 ### P2
 
-5. [Tighten expression and type semantics](05-expression-and-type-semantics.md)
+5. [Tighten expression and type semantics](05-expression-and-type-semantics.md) — partial; arrays/tuples/field-access landed (commit a90d147), CHAR_LENGTH UTF-8 + PostgreSQL string casts landed (commit 9f090e5); non-literal arrays through planner, decimal int128, broader decimal semantics still open
 6. [Close parser gaps around MySQL `SELECT ... INTO` and recursive CTE handling](06-parser-gaps-select-into-and-recursive-cte.md)
 7. [Integrate CTE handling into the main `Session` query path](07-session-cte-integration.md)
 
 ## Notes
 
 - CTE work is intentionally held at `P2` per current priority guidance.
-- `P0` (issue 01) plus all original `P1` items (02–04) are implemented in the working tree.
-- Issues 08 and 09 were surfaced by `scripts/test_sqlengine.sh` and remain open.
-- Each issue file includes evidence, scope, acceptance criteria, and suggested verification.
+- All `P0` and original `P1` items resolved as of 2026-04-18. Issues 08 and 09 (surfaced by `scripts/test_sqlengine.sh`) also resolved the same day.
+- Issue 05 is partial; remaining work continues per the compound-value spec and tracked in this README.
+- Open: 06, 07, and the remaining items in 05.
+- Each issue file includes evidence, scope, acceptance criteria, suggested verification, and resolution notes once closed.