@jutge.org/toolkit 4.4.48 → 4.4.51

package/docs/getting-started-guide.md

@@ -84,7 +84,7 @@ Before using the toolkit, you should configure it with your preferences:
 2. **Set a configuration value:**
 
     ```bash
-    jtk config set defaultModel "google/gemini-2.5-flash"
+    jtk config set defaultModel "openai/gpt-6-luna"
     ```
 
 3. **Edit configuration interactively:**

package/docs/problem-anatomy.md

@@ -120,7 +120,7 @@ This optional section describes the output of the problem.
 
 The `\Sample` section will contain the sample test cases. It is possible to adjust the formatting of the sample test cases: `\SampleOneCol` places input and output test cases one below the other, while `\SampleTwoCol` places them side by side.
 
-`RunPython` users should use `\SampleSession` to get their sample test cases properly formatted as interactive Python sessions using `sample.dt`. The `sample.dt` file should contain the sample test cases using the [doctest](https://docs.python.org/3/library/doctest.html) format and currently must be generated by hand.
+It is also possible to use `\SampleSession` to get their sample test cases properly formatted as interactive Python sessions using `sample.dt`. The `sample.dt` file should contain the sample test cases using the [doctest](https://docs.python.org/3/library/doctest.html) format and currently must be generated by hand. Using `sample.dt` for compilers different than Python is not explicetely supported, but many users do so.
 
 The title inside the `\Problem{}` macro should match the title in the metadata given in the `problem.lang.yml` file, but the title in the LaTeX file can contain math or LaTeX macros whereas the title in the YAML file should be plain text.
 
@@ -355,7 +355,7 @@ In addition, there must be no spaces before a line break. In particular, there m
 
 ### Sample test cases
 
-Sample test cases that contain `sample` in their filename and will be revealed to users in the problem statement. As such, they should make clear the format of the input and the output for the problem and should be reasonably short.
+Sample test cases contain `sample` (yes: _contain_, no _start with_) in their filename and will be revealed to users in the problem statement. As such, they should make clear the format of the input and the output for the problem and should be reasonably short.
 
 ### Public test cases
 

package/package.json

@@ -1,7 +1,7 @@
 {
     "name": "@jutge.org/toolkit",
     "description": "Toolkit to prepare problems for Jutge.org",
-    "version": "4.4.48",
+    "version": "4.4.51",
     "homepage": "https://jutge.org",
     "author": {
         "name": "Jutge.org",