````instructions
# GitHub Copilot Instructions

**Never use the unicode multiplication symbol (×, U+00D7) in any documentation, code, or markdown.**

Always use a plain lowercase 'x' for dimensions and multiplication.

- WRONG: `25mm × 25mm × 25mm`
- CORRECT: `25mm x 25mm x 25mm`

# Git Instructions

- If a git command fails due to authentication reasons, retry the command exactly once.

# Wiki Tagging Standards

All wiki pages should use YAML frontmatter for tagging.

## Challenge Tags
All challenge pages must include the following tags:
- `challenge`: Identifies the page as a challenge.
- `challenge-NNN`: A unique sequential identifier.
   - `challenge-001`: October 2025
   - `challenge-002`: November 2025
   - `challenge-003`: December 2025
   - Increment for subsequent months.
- `archive`: (Optional) Use this tag when the challenge is no longer active.

## Visibility Tags
- `hidden`: Use this tag to prevent the page from being published to the fargo3d.com website.

# Challenge Lifecycle

Challenges follow a specific monthly cycle:
1. **Announcement**: A challenge is announced at the meetup in Month X.
2. **Execution**: Participants work on the challenge between Month X and Month X+1.
3. **Judging**: Results are brought to and judged at the meetup in Month X+1.

**Example:**
- **November Challenge**: Announced in November, Judged in December.
- **December Challenge**: Announced in December, Judged in January.

**Wiki Page Roles:**
- **Current-Challenge.md**: Displays the challenge currently in the "Execution" phase (announced last month, to be judged at the upcoming meetup).
- **Upcoming-Challenge.md**: Displays the challenge to be announced at the upcoming meetup.

# Content Synchronization

The `wiki-fargo3d` submodule contains the official documentation. Some content is mirrored in the main repository root and `wiki-content-gitea`.

## Synchronization Matrix
When updating monthly challenges, dates, or announcements, update all corresponding locations:
- **Root `Readme.md` vs `wiki-fargo3d/Home.md` (and `wiki-content-gitea/Home.md`)**:
  - Keep active challenge name, upcoming challenge name, and general descriptions in sync.
- **Root `challenges.md` vs `wiki-fargo3d/Current-Challenge.md` (and `wiki-content-gitea/Current-Challenge.md`)**:
  - Keep active challenge details, requirements, judging, timeline, and challenge archive table in sync.
- **Root `itinerary.md` vs `wiki-fargo3d/Itinerary.md` (and `wiki-content-gitea/Itinerary.md`)**:
  - Keep meeting schedules and segment timelines in sync.
- **`wiki-fargo3d/Upcoming-Challenge.md` vs `wiki-content-gitea/Upcoming-Challenge.md`**:
  - Keep upcoming challenge announcement details in sync.
- **`wiki-fargo3d/Important-Dates.md` vs `wiki-content-gitea/Important-Dates.md`**:
  - Keep upcoming meetup dates, completed statuses, and challenge milestones in sync.
- **`announcements/<MonthYear>.md` vs `challenges/<Month-Year>/readme.md`**:
  - Keep announcement email texts, meeting dates/locations, and challenge folders in sync.

## Meeting Location Standards
- **Primary / Standard Location**:
  ```text
  West Fargo Public Library
  215 Third St. E.
  West Fargo, ND 58078
  ```
- All regular meetings, `Important-Dates.md`, and announcements should reflect the West Fargo Public Library unless a specific one-off meeting venue is designated.

## "Last Updated" Date Policy
- Any page containing a `**Last Updated**: <Date>` footer (e.g., `Home.md`, `Important-Dates.md`) **must** be updated to reflect the current date whenever changes or reviews occur.

## Git Workflow for Wiki Updates
1. Make changes in `wiki-fargo3d/` (and mirror to `wiki-content-gitea/` if applicable).
2. Commit and push changes in `wiki-fargo3d`.
3. Update root documentation (`Readme.md`, `challenges.md`, `itinerary.md`, `announcements/`).
4. Go to root `/home/espoon/photos/3dPrintMeetup` (or `P:\3dPrintMeetup`).
5. Commit root changes including the submodule pointer update.
6. Push root changes.

## Example Front Matter

```yaml
---
tags:
 - challenge
 - challenge-002
---
```
````