testscripts/commands: Update 'future' date to far future

[toddy15]

In Debian, we've tested a rebuild of all packages at a given date in the future. The date is estimated to be three years after the release of our next stable distribution. The system clock of the building machine has been set to 2030-08-09. On that date, the test of the 'hugo list' command fails.

See https://bugs.debian.org/1127121 for details.

Fixes #14486

[gemini-code-assist]

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

[github-actions]

AI Detection Analysis 🔍

Confidence Score: 25%

Reasoning:
The pull request is straightforward and context-specific, reflecting knowledge of Debian packaging practices and referencing a real-world bug report. The language is precise, functional, and targeted towards fixing a specific failure in a test script due to a future system clock configuration. There is no verbosity, hedging, or filler content often found in AI-generated text. Moreover, the clear linkage between the issue (test failure due to a future date), the external reference (Debian bug tracker), and the specific fix indicates purposeful human action based on domain knowledge.

Key Indicators:

• Precise reference to Debian testing context and forthcoming stable release.
• Citation of a specific bug (https://bugs.debian.org/1127121), demonstrating situational awareness.
• Targeted change in a test script intended to ensure compatibility with future system dates.
• Absence of generic or overly verbose language typical of AI-generated content.
• Logical, goal-oriented writing tied to a pragmatic issue (calendar date in testing environments).

This suggests a human author with understanding of system testing and practical software maintenance.

✅ No strong indicators of AI generation detected