feat(v2): M3 activation/weight/result buffers, real BRAM mapping

Implements M3: three parametric dual-port buffers for the §12
data-plane (Input/Weight/Result), reusing the proven BRAM-inference
idiom from the frozen hardware/v1/rtl/act_buffer.v (synchronous write,
synchronous REGISTERED read, no reset on the read register -- keeps
Yosys off the LUT-RAM path).

Verified with Verilator: 10/10 tests pass (write-then-read
correctness, extreme INT8 round-tripping, weight_buffer's full 64-bit
tile width round-tripping, undisturbed re-reads).

Real synthesis at two depths per module (6 configs total): 0 CHECK
problems, every configuration correctly infers DP16KD (never
LUT-RAM). Non-obvious real finding: weight_buffer's BRAM cost is
driven by its P_IN*DATA_WIDTH tile width, not its DEPTH -- an 8x depth
reduction (512->64) left DP16KD usage unchanged at 2, while
activation_buffer/result_buffer (byte-wide) scale as naively expected
(2->1). All default-depth configs PASS at 80MHz with large margin
(287-367 MHz) via real nextpnr-ecp5 place&route.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013xXuuRUWZScuo1DeYJxs3v

hardware/v2/rtl/result_buffer.v

@@ -0,0 +1,47 @@
+`timescale 1ns/1ps
+
+// ================================================================
+// FPGA-Neural V2 -- Result Buffer (M3, docs/v2-description.md §14)
+//
+// Holds the "Result Buffer" of the §12 data-plane diagram: one INT8
+// slot per node id, written by a Neural Processor's result_data (at
+// its result_node_id address) once its job's tile_last has drained
+// through the pipeline (M1), and read by whichever consumer needs it
+// next -- a downstream layer's Weight/Activation Buffer producer, the
+// Dependency Manager (M6, dependency resolution), or the host
+// (READ_RAM-equivalent path, M4/M8).
+//
+// Same BRAM-inference idiom as activation_buffer.v (dual-port, Port A
+// sync write, Port B sync REGISTERED read, no reset on the read
+// register). DEPTH is fully parametric. Deliberately NOT tracking
+// "has this id been written yet" here -- that bookkeeping belongs to
+// the Dependency Manager (M6), not this buffer.
+// ================================================================
+
+module result_buffer #(
+    parameter DEPTH       = 4096,
+    parameter DATA_WIDTH  = 8,
+    localparam ADDR_WIDTH = $clog2(DEPTH)
+)(
+    input wire clk,
+
+    input wire                          wr_en,
+    input wire [ADDR_WIDTH-1:0]         wr_addr,
+    input wire signed [DATA_WIDTH-1:0]  wr_data,
+
+    input  wire [ADDR_WIDTH-1:0]        rd_addr,
+    output reg  signed [DATA_WIDTH-1:0] rd_data
+);
+
+    reg signed [DATA_WIDTH-1:0] mem [0:DEPTH-1];
+
+    always @(posedge clk) begin
+        if (wr_en)
+            mem[wr_addr] <= wr_data;
+    end
+
+    always @(posedge clk) begin
+        rd_data <= mem[rd_addr];
+    end
+
+endmodule