chore: move 42 to final

[jcstein]

Overview

Resolves #361

[gemini-code-assist]

Summary of Changes

Hello @jcstein, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on finalizing CIP-042, the Matcha Network Upgrade, by updating its status to "Final" and removing the associated "last-call-deadline". Additionally, minor formatting adjustments were made to the metadata table in CIP-042, and a small, possibly accidental, text modification occurred in cips/cip-002.md.

Highlights

• CIP-042 Status Update: The status of CIP-042 (Matcha Network Upgrade) has been updated from "Last Call" to "Final".
• Removal of Last Call Deadline: The last-call-deadline field has been removed from CIP-042, as it is no longer in the "Last Call" phase.
• Minor Formatting Adjustment: The markdown table header formatting in CIP-042 was adjusted for consistency.
• Accidental Edit in CIP-002: A small, likely unintended, text "ci" was added to the beginning of the cips/cip-002.md file.

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
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request's main goal is to move CIP-42 to Final status, which it does correctly. However, there are two issues. First, an apparent typo in cips/cip-002.md breaks the Markdown table formatting. Second, the update to cips/cip-042.md includes minor editorial changes (whitespace adjustments) along with the status update, which goes against the process defined in CIP-1. I've provided specific feedback on both points.

[gemini-code-assist]

While updating the status to Final is correct, this change also includes whitespace adjustments to align the table columns. According to the process outlined in CIP-1, a pull request moving a CIP to Final should only contain the status update. Editorial changes like this should be submitted in a separate PR to maintain a clean history and adhere to the established process.