Name: Kasino Dengan Pengeluaran Malaysia Selamat
Rating: 4.4 (32408 reviews)
@@ -679,6 +679,7 @@ ack duplication 73b08512b41c61f2 101 E1 follow-up (CodeRabbit on #214, threads 1
 ack duplication 73e06cf71f4ea8bc 38 now=38 was=0 p=src/ingest_binds.h:1263 lane FE-B (receiver evidence): lexical clone pairs, not shared logic — the per-language predicates (implicitReceiverLang, classNameReceiverLang, memberNeverReachesFreeFunction, isReceiverEvidenceKind, callableKind, classLike, isThisRoot) are one-line OR-lists over different enum sets that share only the shape with quality.h/model.h/slice.h predicates asking other questions; keyOf/typeKey build different keys into a reused buffer; classAt (innermost class span by byte) vs flipimpact innermostAtLine (by line, other table); impactViaColumn vs lintrules dependencyCapableMask share a bitmask idiom; the JS fixture encode|stringify is a deliberate twin (test/receiverevidencefix: same-named near misses); pargates.py is unchanged since cd87e30e (a regrouped pre-existing pair). The one real clone, the enclosing-function walk, was merged into innermostEnclosingFn instead of acked
 ack duplication 7589afcf46d892d1 38 by=src/* now=38 was=0 prov=recon rung 3 flow-sensitive reaching definitions (docs/EVALS.md 'Flow-sensitive slice in the small', 2026-09-03, lane/n6-b). edgesOf: the contract change IS the point — the diff now reads the scan's reach table (scan, rowOfOcc, cap) so rows/flow/diff share one edge oracle. sliceEmitBody +4 cx: the rd= emission per use row (its formatting already factored into sliceAppendReachAttr). The three duplication rows are the idiomatic tree-sitter named-child loop (seq/hasStructureBelow vs ingest helpers) and a two-way family ternary — no shared logic to lift. short-horizon-churn = self-churn of the two files this lane owns. sliceLegendText +11 lines = the registered per-construct disclosures the band requires on the first screen.
 ack duplication 75b5d63d5a992e21 44 now=44 was=0 prov=recon DISCLOSE sinks: a reason-to-field switch is the shape every multi-reason sink shares; -Wswitch exhaustiveness over DisclosureWhy is the point (Diagnostics.h 4b)
+ack duplication 766a783b149a945a 49 now=49 was=0 p=src/forreexport.h:751 idiom: collect one field per element (chainFiles over a re-export chain, resolvedNames over pattern programs); a shared helper would name neither
 ack duplication 767f5200ffbdb095 54 now=54 was=0 prov=recon E1 answer grader + questions task source + claude-runner control isolation (F3). churn=self on run_one/main/build_prompt/_claude_metrics/_harness_metrics/_execute/prepare_codex_environment/prepare_opencode_environment is this one change's own edit window on bench/agentloop/run_agentloop.py, which the opencode round touched days ago: the three preparers now share ephemeral_run_home()+link_credential() and the three command builders share build_harness_command(), so every one of those symbols is edited by the same commit that introduces the claude preparer. run_one's complexity regression was FIXED rather than acked (25->under the bar, by extracting build_harness_command/question_timeout/prepare_environment) and the two dead-code rows were fixed by restoring explicit dispatch — a dict of callables had hidden the codex/opencode preparers from the resolver. The remaining duplication row (prepare_claude_environment | prepare_codex_environment, 101 tokens, down from 282) is DELIBERATE and not further factored: the residue is 'ephemeral home named by one env var + credentials symlinked + set the var', and collapsing it would need a nine-parameter helper that opencode still could not use (it derives every path from xdg-basedir at module load, so five dirs plus HOME must move). Each preparer is asserted independently by its own canary gate — agentloopclaudecheck/agentloopopencodecheck/agentloopcodexcheck — and keeping the three recipes separately readable is the point of those gates. grade_answers.py's new-symbol rows are the six protocol grader types plus the closed accept-rule clause grammar; apply_clauses is a flat per-clause-kind dispatch with no nesting, and transcript_answer_text's error-masking row is the deliberate 'schema drift degrades to nulls, never raises' contract the retained transcript makes safe. Gates: agentloopgradercheck (new, born red on origin/main at exit 2) and agentloopclaudecheck (new, born red at exit 1) both green; codex/opencode canaries and analyze.py --self-test unchanged and green.
 ack duplication 77278c286d945470 22 now=22 was=0 prov=recon timsort vendoring: every row is the vendored src/infra/timsort.hpp (upstream v3.0.1 + the recorded workspace patch) plus the facade forwarder it needs. The complexity/verbosity/params/duplication rows are UPSTREAM's shape — mergeLo/mergeHi, gallopLeft/gallopRight and the timsort/timmerge overload pairs are twins in the release itself — and restructuring them would destroy the property that makes the file auditable: that it can be re-derived byte-for-byte from a public tag plus one described patch. The one preexisting-worse row, infra::sort::stable vs infra::sort::unstable at 22 tokens, is what a facade IS: each entry is a one-line forward to a DIFFERENT algorithm, and collapsing them into one algorithm-parameterised template would hide the explicit named choice the layer exists to make (G5). Nothing is routed to timsort; test/timsortcheck.sh is what keeps the file honest.
 ack duplication 774b8194ffdecea7 59 by=src/* rung 3 flow-sensitive reaching definitions (docs/EVALS.md 'Flow-sensitive slice in the small', 2026-09-03, lane/n6-b). edgesOf: the contract change IS the point — the diff now reads the scan's reach table (scan, rowOfOcc, cap) so rows/flow/diff share one edge oracle. sliceEmitBody +4 cx: the rd= emission per use row (its formatting already factored into sliceAppendReachAttr). The three duplication rows are the idiomatic tree-sitter named-child loop (seq/hasStructureBelow vs ingest helpers) and a two-way family ternary — no shared logic to lift. short-horizon-churn = self-churn of the two files this lane owns. sliceLegendText +11 lines = the registered per-construct disclosures the band requires on the first screen.
 
@@ -2141,9 +2141,9 @@ wrong, and it has. These are the results that say so, all in-tree, all published
 ### In the tests
 
 <details>
-<summary><b>751 gate scripts</b>, five contracts no unit test can hold, and the house rule: write the gate before the code it measures</summary><!-- gatecount -->
+<summary><b>752 gate scripts</b>, five contracts no unit test can hold, and the house rule: write the gate before the code it measures</summary><!-- gatecount -->
 
-`test/regression.sh` names **751 gate scripts** and is the authoritative list;<!-- gatecount -->
+`test/regression.sh` names **752 gate scripts** and is the authoritative list;<!-- gatecount -->
 `python3 test/pargates.py . ./build/ripwire -j 6` runs the same setin parallel. On top of them sit the
 contracts that do not fit a unit test: two runs byte-identical, warm output identical to cold, output
 that pipes clean through `xmllint --noout`, a sanitizer build with `-fno-sanitize-recover=all`, and a
@@ -2901,7 +2901,7 @@ python3 test/pargates.py . ./build/ripwire -j 6
 A new gate script must be added to `test/regression.sh` in the same change. The gate
 `test/manifestcheck.sh` enforces this rule.
 
-Another gate derives the cap inventory. The tool has 367 compile-time caps and 8 ranking parameters.
+Another gate derives the cap inventory. The tool has 368 compile-time caps and 8 ranking parameters.
 `docs/LIMITS.md` lists each cap, its value, and whether the file discloses a truncation when the cap
 fires, and `python3 docs/limits_build.py --check` proves that list against `src/`. `docs/TUNING.md`
 lists the measured cost of each cap.
 
@@ -0,0 +1,6 @@
+### Fixed — `--for` follows TS/JS namespace re-exports, checks every segment of a written qualifier, and gives an unresolved name a fallback ladder
+
+-`--for``<reexports>`: a TS/JS namespace hop is now a row. `import * as X from './m'` followed by a local `export { X }` (or `export { X as Y }`), and `export * as X from './m'`, publish the whole module under `X`; the row says `ns="X"`. Behaviour change: `export * as ns from` used to be no row at all (the old legend said so); it is now an `ns=` row, and `test/reexportcheck.sh` arm T2 was rewritten with it.
+- `--for` `<reexports>` on a qualified subject (`Q.leaf`, `Q::leaf`): every segment of `Q` must be accounted for. Full proofs: the file stem or a dot-suffix of it (`Completions` for `ts.Completions.ts`), the path's own tail (`utils.legacy` for `src/utils/legacy.ts`), a package index file's directories (`utils` for `src/utils/index.ts`), the whole owner path, or a namespace hop that publishes the definition under `Q`. Three weaker proofs only hedge: a directory elsewhere on the path (`src/utils/legacy/old.ts` for `utils`, `q_by="dir"`), a consumer's own `import * as Q from …` (`q_by="alias"`), and a path proof the tree contradicts (a file does `import * as Q from M` and no such `M` reaches the definition, so a `tests/utils.ts` stem proves nothing; `q_by="path"`); a hedged definition is listed only when nothing proves `Q` fully. The definition carries `q=` and its proving chain prints first. When one definition proves `Q` fully, a same-named one that cannot is no longer listed, so such a task may print fewer definitions than before. When none does and a cue word asks where the name comes from (`where is utils.formatDate defined`), every chain still prints, marked `q_unmatched="1"`. A subject that is one code-shaped name (the whole task) now prints its chain without a cue word; a bare `Q.leaf` prints only chains with some proof. A `this.X` / `self.X` subject is a member access and gets no block. A namespace re-export cycle (`a.ts: export * as B from './b'`, `b.ts: export * as A from './a'`) now ends without reaching the spelling cap.
+- `--for`: a name-exact route that resolved no definition (`reason="no_candidates"`, empty `<sigs>`) now prints a `<shortkey>` block with a fallback ladder, each rung named: `leaf` (a dotted key's last segment, filtered by the same qualifier proof; exactly one fully proven definition is `exact="1"` and its body is printed, several are hedged with `cands=`, hedged-only proofs say `q_by="alias"`, `q_by="path"` or `q_by="dir"` and are never exact, a method or nested function gets only its owner-path proof, never its file's, none is `q_unmatched="1"`; C++ stores only the innermost owner, so a namespace segment stays unproven), `substring` (definition names containing the key, never exact) and `literal` (declaration-shaped source lines the index does not store as definitions: `using X =`, `typedef … X;`, `type X`, `#define X`, `… as X` on an import line, `const`/`let`/`var`/`static X`, `X =` at column 0; comment lines are never rows). Every block carries `next=`; rows are capped at 6 per rung with `total=`, a printed body is cut past 8192 bytes with `truncated="1"`, and `floor="1"` marks a literal scan that could not read every file. The rungs can all be empty (`total="0"`). Only XML answers on a single root carry the block: `--json`, `--format=candidates` and multi-root answers print neither the block nor a marker; under `--token-budget` a held marker prints instead. A `this.X` / `self.X` subject gets no ladder. `RIPWIRE_NO_SHORT_KEY=1` turns it off.
+- Measured on the practice questions this targets: `--for=Completions.getCompletionsAtPosition` on TypeScript went from a 1.3 KB answer with no definition to the namespace hop and the definition's body; `--for=ColumnPtr` (ClickHouse) and `--for=ExprType` (RisingWave) now name the `using` / `use … as` lines that declare them. Gate: `test/barrelshortkeycheck.sh`.
@@ -21,7 +21,7 @@ section, and it is not an afterthought.
 | **Co-change / known-item evals** | `--eval`, `--eval-retrieval` (see `bench/ANSWERQUALITY.md`) | Whether the tool surfaces the other files a real historical commit touched; and known-item retrieval across four rankers. |
 | **Ensemble calibration harness** | `bench/ensemblecal/` | Whether `--ensemble`'s four evidence families are actually orthogonal, how often each fires, how stable each is across commits — and the preset ladder derived from that (§9). |
 | **Differential argv harness** | `test/argvdiffcheck.sh` | That a refactor changed *nothing observable*: two binaries, every argv vector, stdout + stderr + exit code byte-identical. |
-| **The gate suite** | `test/regression.sh`, `test/pargates.py` | 751 gate scripts plus the determinism, cache-transparency and golden contracts. <!-- gatecount --> |
+| **The gate suite** | `test/regression.sh`, `test/pargates.py` | 752 gate scripts plus the determinism, cache-transparency and golden contracts. <!-- gatecount --> |
 | **`--quality-delta`** | `src/quality.h` | Ten measured code-quality failure modes, reported only where a change made them worse. |
 
 ### The labeling protocol (why the held-out eval is allowed to disagree with the ranker)
@@ -5888,7 +5888,7 @@ copy here would be exactly the dialect divergence that gate exists to catch. Com
 tags, wrap, stable-order defaults), seven individually invoked standalone gates (`g1freshcheck`,
 `skillscan`, `htmlexport`, `compresscheck`, `handoffcheck`, `releaseinstallcheck`,
 `taskroutecheck`), and a single loop
-naming **751 gate scripts**, all of which exist on disk. <!-- gatecount -->
+naming **752 gate scripts**, all of which exist on disk. <!-- gatecount -->
 
 `python3 test/pargates.py . ./build/ripwire -j 6` runs the same scripts in parallel so a full
 verification fits in one sitting. It does not modify `regression.sh`.
@@ -7005,7 +7005,7 @@ Listed because the reason is more useful than the silence.
  shipped**. See `bench/locbench/anchorhop_calib.json`. The mention anchor's reproducible numbers are
  the ablations in §4.
 - **A single round gate-count.** Two in-tree numbers disagree (`test/pargates.py`'s docstring says
- ~210; `test/argvdiffcheck.sh` says 200+), while the loop in `test/regression.sh` names 751. The <!-- gatecount -->
+ ~210; `test/argvdiffcheck.sh` says 200+), while the loop in `test/regression.sh` names 752. The <!-- gatecount -->
  loop is the authority; the stale docstrings are a known drift. Since 2026-09-10 the number is not
  written by hand anywhere: `docs/gatecount_build.py` derives it from the loop and rewrites every
  published site, `test/gatecountcheck.sh` fails if any of them drifts, and `test/manifestcheck.sh`
 
@@ -30,10 +30,10 @@ a small explicit bound" is safe only when nothing inside the group repeats; it i
 
 | total caps | files | caps whose file discloses | caps whose file discloses NOTHING |
 | --- | --- | --- | --- |
-|367| 128 |243|**124**|
+|368| 128 |244|**124**|
 
 Plus 8 ranking and apportionment parameters, in their own table below: they are not caps, they
-are not counted as caps, and 367 + 8 is the 375 constants this generator parses out of `src/`.
+are not counted as caps, and 368 + 8 is the 376 constants this generator parses out of `src/`.
 
 ## INDEXING, OUTPUT or BOUNDARY — which half of the answer a cap bounds
 
@@ -51,8 +51,8 @@ None of them truncates anything, so none can be judged by `shown=`/`total=` and
 a disclosure — labelling them OUTPUT would ask for a `capped="1"` that could never honestly fire.
 The distinction was named in review on #108 and the rows below now carry it.
 
-The `class` column below carries that answer where it is known. **143 of 367 caps are classified
-(50 INDEXING, 46 OUTPUT, 47 BOUNDARY); the remaining 224 render `—`, which means NOT YET
+The `class` column below carries that answer where it is known. **143 of 368 caps are classified
+(50 INDEXING, 46 OUTPUT, 47 BOUNDARY); the remaining 225 render `—`, which means NOT YET
 CLASSIFIED — never "neither".** Classifications live in `docs/limits_classes.tsv`, a sidecar with
 a known expiry:
 the tag belongs on the declaration itself, and this file exists only because the round that
@@ -103,7 +103,7 @@ refuse to write, so the column cannot be satisfied by pointing at nothing.
 
 ## Caps, by file
 
-One table for each of the 128 files that declare a cap — the 367 caps counted above, and no parameter.
+One table for each of the 128 files that declare a cap — the 368 caps counted above, and no parameter.
 
 ### `src/abicheck.h`
 
@@ -528,6 +528,7 @@ Discloses: `capped`
 |`kReexportRowCap`|`8`| — | hop rows per definition (BFS order); the rest counted in total= |
 |`kReexportSpellingCap`|`256`| — | spellings one walk visits; past it total= is a floor (capped="1") |
 |`kReexportUseCap`|`2`| — | use-site rows per definition, from task-named files |
+|`kShortKeyRows`|`6`| — | rows per rung (a runaway guard; total= counts all) |
 
 ### `src/forselfhook.h`
 
 
@@ -14,25 +14,25 @@ to production at defaults; that control is what makes these numbers mean anythin
 
 | cap declarations | distinct names | tunable | must stay `constexpr`| move >= 1 invocation | move nothing measurable |
 | --- | --- | --- | --- | --- | --- |
-|257|256| 112 | 12 |**37**| 75 |
+|258|257| 112 | 12 |**37**| 75 |
 
-The first two columns are not the same number, and the gap is not a rounding: `src/` holds **257 cap
-declarations** under **256 distinct names** (`kRowCap` declared in more than one file). The sweep
+The first two columns are not the same number, and the gap is not a rounding: `src/` holds **258 cap
+declarations** under **257 distinct names** (`kRowCap` declared in more than one file). The sweep
 patches by NAME, so its own population is NAMES and not declarations — and the two columns beside
 those are frozen at the commit named under Provenance while this census is re-read from `src/` on
-every run, which makes them a third population again. Enumerated over the 256 names `src/` declares
-today: **111 tunable**, **12 must stay `constexpr`**, and **133 declared since the sweep was
+every run, which makes them a third population again. Enumerated over the 257 names `src/` declares
+today: **111 tunable**, **12 must stay `constexpr`**, and **134 declared since the sweep was
 prepared, which no measurement has touched** (`kAliasPeelDepth`, `kBackHopWidth`,
-`kBaseScopeScanCap`, `kBridgeMaxHops`, `kCallSitesPerRowCap`, `kCallersBandMaxBytes`, +127 more).
-111 + 12 + 133 = 256, and `emit` refuses to render a partition that does not add up. The `tunable`
+`kBaseScopeScanCap`, `kBridgeMaxHops`, `kCallSitesPerRowCap`, `kCallersBandMaxBytes`, +128 more).
+111 + 12 + 134 = 257, and `emit` refuses to render a partition that does not add up. The `tunable`
 column above reads 112 rather than 111 because one name the sweep classified is no longer declared
-in `src/` at all: `kSituTestRowsShown`. Quoting "113 of 257" would be wrong in both halves at once,
+in `src/` at all: `kSituTestRowsShown`. Quoting "113 of 258" would be wrong in both halves at once,
 which is the shape of error a generated table exists to prevent.
 
 ## Read this ratio before the tables
 
 **37 of 112 tunable caps move any invocation at all. 75 move nothing measurable.** That is the
-finding, and it says what NOT to do: this is not a 257-cap audit. Most of these constants are
+finding, and it says what NOT to do: this is not a 258-cap audit. Most of these constants are
 inert on real invocations and should be left alone. The work worth doing is the small set below,
 plus the caps that fire SILENTLY — a cap that bites without disclosing is a defect independent of
 whether its value is right, and that fix is both cheaper and larger than any retuning.