fix: ThreePositionStrategy class comment still advertises 1-100% anchor width (#786)

- Fix class-level NatSpec: use accurate wording (width computed from
  anchorWidth param provided by Optimizer) instead of imprecise
  LiquidityManager attribution
- Fix inline comment in _setAnchorPosition (same stale 1-100% claim)
- Update PRODUCT-TRUTH.md and ARCHITECTURE.md which had the same
  incorrect 1-100% range claim

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

onchain/src/abstracts/ThreePositionStrategy.sol

@@ -14,7 +14,7 @@ import "@uniswap-v3-core/interfaces/IUniswapV3Pool.sol";
  * @dev Provides the core logic for anti-arbitrage asymmetric slippage profile
  *
  * Three-Position Strategy:
- * - ANCHOR: Near current price, fast price discovery (width enforced by LiquidityManager)
+ * - ANCHOR: Near current price, fast price discovery (width computed from anchorWidth param provided by Optimizer)
  * - DISCOVERY: Borders anchor, captures fees (11000 tick spacing)
  * - FLOOR: Deep liquidity at VWAP-adjusted prices
  *
@@ -104,7 +104,7 @@ abstract contract ThreePositionStrategy is UniswapMath, VWAPTracker {
         internal
         returns (uint256 pulledKraiken, uint128 anchorLiquidity)
     {
-        // Enforce anchor range of 1% to 100% of the price
+        // Compute anchor spacing from anchorWidth param (range enforcement is the Optimizer's responsibility)
         int24 anchorSpacing = TICK_SPACING + (34 * int24(params.anchorWidth) * TICK_SPACING / 100);
 
         int24 tickLower = _clampToTickSpacing(currentTick - anchorSpacing, TICK_SPACING);