Add downloaded version of StateMachine link

[TaylerUva]

No description provided.

[Copilot]

Pull request overview

This PR adds a downloadable version of the StateMachine diagram by including the TLDraw file (StateMachineMap.tldr) in the repository. The changes allow users to view the state machine diagram locally in VSCode using the TLDraw VSCode extension, in addition to the existing web-based interactive link.

Key changes:

• Added the StateMachineMap.tldr file containing the state machine diagram data
• Updated README.md to include a link to view the diagram in VSCode
• Added VSCode extension recommendation for the TLDraw extension

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 3 comments.

File	Description
StateMachineMap.tldr	New file containing the TLDraw state machine diagram data in JSON format
README.md	Updated to reference the local .tldr file and added note about required VSCode extension
.vscode/extensions.json	New file recommending the TLDraw VSCode extension for viewing the diagram

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Spelling error: "eachother" should be "each other" (two words).

Suggested change

	This offseason, we chose to control our robot using a state machine! Prior to staring our code, we mapped out and dicussed every state that our robot could be in during a match and how those states should interact with eachother. This allowed us to create a framework of our commands, sort of like pseudocode, before we even opened VSCode!
	This offseason, we chose to control our robot using a state machine! Prior to staring our code, we mapped out and dicussed every state that our robot could be in during a match and how those states should interact with each other. This allowed us to create a framework of our commands, sort of like pseudocode, before we even opened VSCode!

[Copilot]

Spelling error: "staring" should be "starting".

Suggested change

	This offseason, we chose to control our robot using a state machine! Prior to staring our code, we mapped out and dicussed every state that our robot could be in during a match and how those states should interact with eachother. This allowed us to create a framework of our commands, sort of like pseudocode, before we even opened VSCode!
	This offseason, we chose to control our robot using a state machine! Prior to starting our code, we mapped out and dicussed every state that our robot could be in during a match and how those states should interact with eachother. This allowed us to create a framework of our commands, sort of like pseudocode, before we even opened VSCode!

[Copilot]

Spelling error: "dicussed" should be "discussed".

Suggested change

	This offseason, we chose to control our robot using a state machine! Prior to staring our code, we mapped out and dicussed every state that our robot could be in during a match and how those states should interact with eachother. This allowed us to create a framework of our commands, sort of like pseudocode, before we even opened VSCode!
	This offseason, we chose to control our robot using a state machine! Prior to staring our code, we mapped out and discussed every state that our robot could be in during a match and how those states should interact with eachother. This allowed us to create a framework of our commands, sort of like pseudocode, before we even opened VSCode!