fix: lint

Author: aryanjassal

docs/Getting-Started/polykey-cli/README.md

@@ -37,11 +37,10 @@ Polykey is continuously built and tested on:
 
 :::note Note
 
- Polykey is currently in beta. Its interface is at various levels of
-stability. So bear with us as we perfect its design. You can contribute by
-discussing with us on [Discord](https://discord.gg/h3UShM8WUN) or creating issue
-tickets in the
-[Polykey-CLI repo on GitHub](https://github.com/MatrixAI/Polykey-CLI). 
+Polykey is currently in beta. Its interface is at various levels of stability.
+So bear with us as we perfect its design. You can contribute by discussing with
+us on [Discord](https://discord.gg/h3UShM8WUN) or creating issue tickets in the
+[Polykey-CLI repo on GitHub](https://github.com/MatrixAI/Polykey-CLI).
 
 :::
 
@@ -53,7 +52,7 @@ Start your journey with Polykey by following the tutorials below in sequence:
 
 For a visual walkthrough, check out our
 [getting started demo video](https://vimeo.com/884649667) after installing
-Polykey. 
+Polykey.
 
 :::
 

docs/Getting-Started/polykey-cli/bootstrapping.md

@@ -26,13 +26,16 @@ key.
 
 :::note Note
 
-Remember to keep your password in a secure location as you will need it each time you start the Polykey agent.
+Remember to keep your password in a secure location as you will need it each
+time you start the Polykey agent.
 
 :::
 
 :::important
 
-Bootstrapping also returns a **recovery code**. This code is required to recover a node with the same ID, so it is critical that you store it safely and securely. If lost, node identity recovery will not be possible.
+Bootstrapping also returns a **recovery code**. This code is required to recover
+a node with the same ID, so it is critical that you store it safely and
+securely. If lost, node identity recovery will not be possible.
 
 :::
 

docs/Getting-Started/polykey-cli/claiming-digital-identities.md

@@ -8,7 +8,9 @@ cryptographic link to a publicly verifiable location.
 
 This tutorial will guide you through the steps to authenticate with GitHub and
 claim an identity using Polykey, enhancing security and streamlining identity
-verification, making it easier for other users to discover and trust your nodes. Currently, we only support github as an identity provider, but we plan to add more in the future.
+verification, making it easier for other users to discover and trust your nodes.
+Currently, we only support github as an identity provider, but we plan to add
+more in the future.
 
 ## Step 1: Authenticate with GitHub
 
@@ -33,8 +35,8 @@ polykey identities authenticate <providerId>
 
 :::note Note
 
-Since Polykey currently only supports GitHub as an IdP, this is the
-command that you will use to start the authentication process.
+Since Polykey currently only supports GitHub as an IdP, this is the command that
+you will use to start the authentication process.
 
 ```bash
 polykey identities authenticate github
@@ -74,19 +76,19 @@ identityId	maverick
 During the authentication process, here's what Polykey requests access to and
 why:
 
-- **Currently: Create Gists:** Polykey creates a gist under your GitHub account containing
-  a cryptographic link. This link is a verifiable method that proves the
-  ownership of your GitHub identity to anyone checking your Polykey gestalt
+- **Currently: Create Gists:** Polykey creates a gist under your GitHub account
+  containing a cryptographic link. This link is a verifiable method that proves
+  the ownership of your GitHub identity to anyone checking your Polykey gestalt
   graph.
 
 -:::note Note
 
- **Future Plan: Read All User Profile Data:** This enables Polykey to access your profile
-  details, including your username, followers, and public repository data. This
-  information is used to ensure that the identity you claim corresponds
-  accurately to your public digital footprint, enhancing trust and verification.
+**Future Plan: Read All User Profile Data:** This enables Polykey to access your
+profile details, including your username, followers, and public repository data.
+This information is used to ensure that the identity you claim corresponds
+accurately to your public digital footprint, enhancing trust and verification.
 
-  :::
+:::
 
 #### Security and Privacy Considerations
 
@@ -150,7 +152,7 @@ https://gist.github.com/my-github-username
 
 This gist contains the cryptographic link confirming that your Polykey identity
 is correctly linked to your GitHub profile. Viewing this gist ensures your claim
-was successful and publicly verifiable. 
+was successful and publicly verifiable.
 
 :::note Note
 

docs/Getting-Started/polykey-cli/discovering-other-users.md

@@ -38,9 +38,10 @@ polykey identities discover <gestaltId>
 ```bash
 polykey identities discover github.com:maverick
 ```
-:::note Note
-This command adds the node associated with the GitHub username "maverick" to
-your discovery queue, allowing you to initiate interactions with this user.
+
+:::note Note This command adds the node associated with the GitHub username
+"maverick" to your discovery queue, allowing you to initiate interactions with
+this user.
 
 :::
 
@@ -117,7 +118,8 @@ managed:
 
 - **Scan:** Allows the node to scan for vaults
 - **Notify:** Allows sending notifications about changes or updates.
-- **Claim** Allows a different gstalt to claim the node 
+- **Claim** Allows a different gstalt to claim the node
+
 #### Example Command to Set Permissions
 
 ```bash
@@ -192,8 +194,8 @@ polykey identities list
 
 ### Trusting and Untrusting Nodes
 
-You can explicitly trust or untrust individual nodes or entire gestalts to refine how notifications and
-access controls are handled:
+You can explicitly trust or untrust individual nodes or entire gestalts to
+refine how notifications and access controls are handled:
 
 ```bash
 polykey identities trust <gestaltId>

docs/Getting-Started/polykey-cli/installation.md

@@ -6,13 +6,17 @@ Installing the CLI can be done in different ways depending on your operating
 environment.
 
 :::info
+
 ## Polykey Core Overview
 
-The Polykey CLI and core primarily use TypeScript for service logic, domain business operations, and persistence layers. While the main codebase is in TypeScript, some supporting libraries incorporate native C++ or Rust for platform‐specific functionality. This approach combines cross‐platform convenience with native performance optimizations.
-Polykey-CLI has only been tested on Linux and macOS. We are working on
-supporting other platforms. There's minor teething problems when it comes
-supporting other platforms. Help us by reporting any issues with the CLI tool in
-our Github Repo
+The Polykey CLI and core primarily use TypeScript for service logic, domain
+business operations, and persistence layers. While the main codebase is in
+TypeScript, some supporting libraries incorporate native C++ or Rust for
+platform‐specific functionality. This approach combines cross‐platform
+convenience with native performance optimizations. Polykey-CLI has only been
+tested on Linux and macOS. We are working on supporting other platforms. There's
+minor teething problems when it comes supporting other platforms. Help us by
+reporting any issues with the CLI tool in our Github Repo
 [here](https://github.com/MatrixAI/Polykey-CLI/issues/new/choose) or by dropping
 a message to the developers in our discord server
 [here](https://discord.gg/dC32r35TeE).
@@ -134,9 +138,9 @@ We will be working on other distribution methods.
 
 :::info
 
-ARM-64 builds are not currently supported on MacOS as of **6 April 2025.** However,
-building Polykey yourself on MacOS resolves in a working binary. Follow this
-guide below to manually build and install Polykey on macOS.
+ARM-64 builds are not currently supported on MacOS as of **6 April 2025.**
+However, building Polykey yourself on MacOS resolves in a working binary. Follow
+this guide below to manually build and install Polykey on macOS.
 
 :::
 
@@ -290,7 +294,7 @@ echo 'export PATH=~/Downloads:$PATH' >> ~/.zshrc && source ~/.zshrc
 
 The path export should not pint to the Polykey executable itself, but rather to
 the directory containing the executable. Otherwise, the executable will not be
-found and will not work. 
+found and will not work.
 
 :::
 
@@ -300,7 +304,7 @@ found and will not work.
 2. Edit the Bash config to add "polykey" to your path. To streamline the
    process, run the following command, making sure to change the path to
    "polykey" if the executable is not in the downloads folder. For most users,
-   this would be `~/Downloads` 
+   this would be `~/Downloads`
 
 :::tip
 

docs/Getting-Started/polykey-cli/managing-multiple-nodes.md

@@ -2,7 +2,10 @@
 
 Managing multiple local
 
-nodes in Polykey can serve various purposes. For example, you might maintain one node for personal projects and another for professional work. This segregation ensures that the vaults and their respective contents remain distinct based on their usage context.
+nodes in Polykey can serve various purposes. For example, you might maintain one
+node for personal projects and another for professional work. This segregation
+ensures that the vaults and their respective contents remain distinct based on
+their usage context.
 
 This approach is particularly advantageous for demonstrations or training
 purposes, as it allows you to simulate sharing vaults between two nodes on the
@@ -40,8 +43,8 @@ context.
 
 :::note Note
 
- If a node has not been created before, initializing the Polykey agent
-for it will also initiate the bootstrap process. 
+If a node has not been created before, initializing the Polykey agent for it
+will also initiate the bootstrap process.
 
 :::
 

docs/Getting-Started/polykey-cli/managing-vaults.md

@@ -67,6 +67,7 @@ This operation does not produce output on successful execution, indicating the
 vault has been removed.
 
 :::note
+
 ## Viewing Vault History
 
 Each vault maintains a version history which tracks changes over time. Use the

docs/README.md

@@ -71,22 +71,22 @@ passwords or keys.
 
 For this reason, we think of secrets as "capabilities".
 
-All secrets are put into vaults. Each vault is a persistent, fully encrypted virtual
-filesystem with automatic version history. Vaults can be shared with other
-Polykey agents.
+All secrets are put into vaults. Each vault is a persistent, fully encrypted
+virtual filesystem with automatic version history. Vaults can be shared with
+other Polykey agents.
 
-Polykey's secrets management system provides users with secure communication
-and secure computation.
+Polykey's secrets management system provides users with secure communication and
+secure computation.
 
 ### Decentralized Trust
 
-Sharing secrets depends on secure communications. Secure communications depends on
-trusted identities.
+Sharing secrets depends on secure communications. Secure communications depends
+on trusted identities.
 
 Polykey introduces a concept called "Gestalt Identity".
 
-A Gestalt Identity is a collection of digital identities (i.e. social media profiles
-and Polykey nodes) that all represent the same entity.
+A Gestalt Identity is a collection of digital identities (i.e. social media
+profiles and Polykey nodes) that all represent the same entity.
 
 When you start a Polykey agent, it immediately forms its own gestalt with the
 Polykey node as its only identity. Link up your digital identities to the node

docs/reference/polykey-cli/commands/secrets.md

@@ -67,7 +67,7 @@ $ polykey secrets dir ~/test-dir vault1
 
 :::warning Warning
 
-This command does not work on Windows yet 
+This command does not work on Windows yet
 
 :::
 
@@ -89,9 +89,9 @@ I edited this secret inside an editor
 4. If no paths are specified, this command takes input from `stdin` and prints
    it to `stdout`
 
-:::tip Tip 
+:::tip Tip
 
-`^D` in the terminal stands for the key combination 'Ctrl-D' 
+`^D` in the terminal stands for the key combination 'Ctrl-D'
 
 :::
 
@@ -194,7 +194,7 @@ new-name
 
 :::note Note
 
- The mode (or file permissions) doesn't exist within a vault 
+The mode (or file permissions) doesn't exist within a vault
 
 :::
 
@@ -270,11 +270,11 @@ do not commit your keys to github
 
 :::tip Tip
 
-`stdin`, or standard input, can be either manually entered by typing, or
-piped in through another command.
+`stdin`, or standard input, can be either manually entered by typing, or piped
+in through another command.
 
 To close the input steam and save the file, press `^D`, or 'Ctrl-D' in a new
-line, or press `^D` twice on the same line. 
+line, or press `^D` twice on the same line.
 
 :::