diff --git a/crates/cb-render-html/src/doc.rs b/crates/cb-render-html/src/doc.rs
index fca3e47..fae1353 100644
--- a/crates/cb-render-html/src/doc.rs
+++ b/crates/cb-render-html/src/doc.rs
@@ -421,24 +421,10 @@ fn pile_svg(out: &mut String, x: i32, label: &str, count: usize, face: &str, not
);
}
-/// The draw stack and the discard stack, as objects on the table.
-///
-/// Both numbers come from the projection — `solution_deck_len` and
-/// `solution_discard` — and are never recomputed here.
-///
-/// **The reshuffle is real and is the U4 default**, confirmed by
-/// ground-game on 2026-08-03: when the deck runs out, the discard is
-/// reshuffled into it deterministically; if both are empty the draw is
-/// skipped (`games/ground/src/lib.rs` `draw_solution`). So the pile shows
-/// the state in which the *next* draw will trigger it. It does not claim a
-/// reshuffle has happened — the view carries no such flag, and the event
-/// already reads out in the log.
-fn piles_svg(out: &mut String, view: &GroundView) {
+fn piles_body(out: &mut String, view: &GroundView) {
let deck = view.solution_deck_len;
let discard = view.solution_discard.len();
let will_reshuffle = deck == 0 && discard > 0;
-
- out.push_str("");
-
- // The discard is public — it has been played (GR-S04 hides only the
- // deck) — so its contents stay readable as text beside the picture.
- let _ = write!(
- out,
- "
discard {}
",
- esc(&cards(&view.solution_discard)),
- );
}
-fn relations_svg(view: &GroundView) -> String {
+/// The table, seen from above (CB-WP-0028 T03).
+///
+/// **One diagram, not three.** The seats were already placed on a circle
+/// for the relationship graph, while the Problems were a row above it and
+/// the piles a separate picture below — three views of one table, and the
+/// player had to assemble them. Now: seats around the edge, the Problems
+/// and the two stacks in the middle, each seat's played card in front of
+/// it, relations drawn between seats.
+///
+/// The existing `problem_svg` and `pile_svg` are reused rather than
+/// reimplemented — they carry the tokens the coverage gate probes for,
+/// and drawing the same thing twice is how the two drift.
+fn table_svg(view: &GroundView) -> String {
let n = view.players.len().max(1);
- let (cx, cy, r) = (200.0f64, 150.0f64, 110.0f64);
+ let (cx, cy) = (380.0f64, 300.0f64);
+ let seat_r = 240.0f64;
+
let pos: Vec<(PlayerId, f64, f64)> = view
.players
.keys()
.enumerate()
.map(|(i, p)| {
- let a = std::f64::consts::TAU * (i as f64) / (n as f64) - std::f64::consts::FRAC_PI_2;
- (*p, cx + r * a.cos(), cy + r * a.sin())
+ // Start at the bottom, not the top: the viewer sits nearest
+ // the reader, which is where you sit at a real table.
+ let a = std::f64::consts::TAU * (i as f64) / (n as f64) + std::f64::consts::FRAC_PI_2;
+ (*p, cx + seat_r * a.cos(), cy + seat_r * a.sin() * 0.72)
})
.collect();
let find = |p: PlayerId| {
@@ -495,8 +488,12 @@ fn relations_svg(view: &GroundView) -> String {
};
let mut s = String::from(
- "