@bananapus/721-hook-v6 0.0.34 → 0.0.36

package/SKILLS.md

@@ -3,7 +3,7 @@
 ## Use This File For
 
 - Use this file when the task involves tiered NFT issuance, reserve minting, voting units, tier splits, or token URI resolver integration for Juicebox projects.
-- Start here, then open the hook, store, deployer, or tests that own the exact behavior you are changing.
+- Start here, then decide whether the bug is in hook runtime logic, store accounting, deployer initialization, or downstream token-URI resolution. This repo spans all four and they are easy to conflate.
 
 ## Read This Next
 
@@ -14,7 +14,8 @@
 | Tier storage and accounting | [`src/JB721TiersHookStore.sol`](./src/JB721TiersHookStore.sol) |
 | Deployment or project launch helpers | [`src/JB721TiersHookDeployer.sol`](./src/JB721TiersHookDeployer.sol), [`src/JB721TiersHookProjectDeployer.sol`](./src/JB721TiersHookProjectDeployer.sol), [`script/Deploy.s.sol`](./script/Deploy.s.sol) |
 | Shared libraries, interfaces, and resolver surface | [`src/libraries/`](./src/libraries/), [`src/interfaces/`](./src/interfaces/), [`src/structs/`](./src/structs/) |
-| Invariants, E2E flows, and regressions | [`test/invariants/`](./test/invariants/), [`test/E2E/`](./test/E2E/), [`test/regression/`](./test/regression/), [`test/TestVotingUnitsLifecycle.t.sol`](./test/TestVotingUnitsLifecycle.t.sol) |
+| Mint, pricing, voting, and checkpoint behavior | [`test/TestVotingUnitsLifecycle.t.sol`](./test/TestVotingUnitsLifecycle.t.sol), [`test/TestCheckpoints.t.sol`](./test/TestCheckpoints.t.sol) |
+| Reentrancy, forks, and pinned edge cases | [`test/TestSafeTransferReentrancy.t.sol`](./test/TestSafeTransferReentrancy.t.sol), [`test/721HookAttacks.t.sol`](./test/721HookAttacks.t.sol), [`test/Fork.t.sol`](./test/Fork.t.sol), [`test/TestAuditGaps.sol`](./test/TestAuditGaps.sol) |
 
 ## Repo Map
 
@@ -37,6 +38,11 @@ Tiered ERC-721 NFT issuance and cash-out hook for Juicebox V6. This repo control
 ## Working Rules
 
 - Start in [`src/JB721TiersHook.sol`](./src/JB721TiersHook.sol) for pay and cash-out behavior, but verify storage-side assumptions in [`src/JB721TiersHookStore.sol`](./src/JB721TiersHookStore.sol) before changing mint, burn, reserve, or supply logic.
+- The store is the source of truth for supply, reserve, removal, and tier-order invariants. Do not “fix” those concepts only in the hook layer.
+- Pending reserves are part of live economics, not deferred bookkeeping. Cash-out denominators and tier availability both depend on them before reserves are minted.
+- Pay credits, overspending protection, and tier split forwarding are economically relevant. Treat them like accounting, not just UX.
 - Treat tier splits, reserve minting, and discounted pricing as treasury-sensitive. Check both runtime code and regression coverage before assuming a change is local.
+- Discounted mint price and cash-out weight are intentionally not the same thing. Free or discounted mints can still carry full tier cash-out weight by design.
+- Changing the default reserve beneficiary is not cosmetic. It can change which tiers have pending reserves and therefore change redemption economics for existing mints.
 - When a task mentions token metadata or rendering, confirm whether the behavior lives in this repo or in an external resolver. Do not over-edit the hook when the real change belongs downstream.
 - When changing deployers or initialization, verify the hook, store, and project-launch path stay aligned. These flows are tightly coupled.

package/USER_JOURNEYS.md

@@ -1,96 +1,191 @@
 # User Journeys
 
-## Who This Repo Serves
+## Repo Purpose
+
+This repo is the standard tiered NFT hook for V6 projects.
+It owns tier issuance, reserve accounting, hook-aware mint and cash-out behavior, and deployer packaging for hook
+clones or hook-shaped project launches. It does not own collection-specific rendering or app-layer policy built on top
+of the hook.
+
+## Primary Actors
 
 - project owners selling or rewarding supporters with tiered NFTs
 - operators managing tier supply, pricing, reserves, and ruleset-aware hook behavior
 - supporters minting or cashing out tier positions through normal Juicebox flows
-- integrators composing custom token URI resolvers on top of the standard 721 hook
+- integrators composing custom token URI resolvers or downstream products on top of the hook
+
+## Key Surfaces
+
+- `JB721TiersHook`: project-facing hook behavior for minting, reserves, metadata, and cash out
+- `JB721TiersHookStore`: tier definitions and accounting backend
+- `JB721TiersHookDeployer`: clone factory for existing projects
+- `JB721TiersHookProjectDeployer`: project-launch packaging for new hook-backed projects
 
 ## Journey 1: Add A Tiered 721 Hook To An Existing Project
 
-**Starting state:** the project already exists in Juicebox and needs tiered NFT issuance without relaunching.
+**Actor:** project owner or deployer.
+
+**Intent:** attach tiered NFT behavior to an existing project without relaunching it.
+
+**Preconditions**
+- the project already exists in Juicebox
+- the owner knows the tier config, reserve behavior, and resolver assumptions it wants
+- the next ruleset metadata can be updated safely
+
+**Main Flow**
+1. Use `JB721TiersHookDeployer` to clone a hook for the project.
+2. Define tier config, reserve behavior, resolver choice, and per-ruleset flags.
+3. Queue or install ruleset metadata that points at the hook.
+4. Future payments can now mint tiers under the configured constraints.
 
-**Success:** a hook clone is deployed, initialized, and attached to the project's ruleset metadata.
+**Failure Modes**
+- the hook is deployed correctly but the ruleset metadata does not actually activate it
+- teams treat the resolver as cosmetic when it is part of the trusted surface
 
-**Flow**
-1. Use `JB721TiersHookDeployer` to clone a hook for the target project.
-2. Define tier config, reserve behavior, token URI resolver, and per-ruleset flags.
-3. Queue or install ruleset metadata that tells the project when the hook should participate in pay and cash-out flows.
-4. Future payments into the project can now mint tiers under the configured constraints.
+**Postconditions**
+- the project has an attached hook and future rulesets can mint tiers under the configured constraints
 
 ## Journey 2: Launch A New Project With A 721 Hook Already Wired In
 
-**Starting state:** the product wants its project treasury and NFT logic created in one operation.
+**Actor:** product team or deployer.
 
-**Success:** the project launches with the hook, terminals, and initial tiers already aligned.
+**Intent:** launch a project whose treasury and tiered NFT logic are aligned from the first ruleset.
 
-**Flow**
-1. Use `JB721TiersHookProjectDeployer` with launch config, rulesets, and hook config.
-2. The deployer launches the project through the core protocol and deploys the hook in the same packaged flow.
-3. The initial ruleset metadata points at the newly created hook so there is no post-launch rewiring gap.
-4. The project starts life as a tiered 721 project instead of becoming one later.
+**Preconditions**
+- the team has launch config, terminal config, and initial tier config ready
+
+**Main Flow**
+1. Use `JB721TiersHookProjectDeployer` with launch and hook config.
+2. Launch the project and deploy the hook in the same packaged flow.
+3. Ensure the first ruleset already points at the created hook.
+4. Start life as a hook-backed project instead of converting later.
+
+**Failure Modes**
+- deployers assume the package is purely convenience and miss the initial ruleset implications
+- launch-time metadata drifts from the actual hook config
+
+**Postconditions**
+- the project launches with tiered NFT logic active from the first ruleset
 
 ## Journey 3: Mint Specific Tiers Through A Payment
 
-**Starting state:** the project has live tiers and the payer knows which tiers they want.
+**Actor:** payer.
 
-**Success:** the treasury receives funds and the beneficiary receives the intended NFT tiers plus any accompanying project-token behavior.
+**Intent:** mint one or more tiers through a normal payment flow.
 
-**Flow**
-1. The payer submits a payment with metadata encoding the desired tier selections.
-2. `JB721TiersHook` validates tier availability, quantity rules, discounts, category constraints, and any ruleset flags affecting minting.
+**Preconditions**
+- the project has live tiers
+- the payer submits metadata encoding the intended tier selections
+
+**Main Flow**
+1. Submit a payment with tier-selection metadata.
+2. `JB721TiersHook` validates availability, quantity rules, discounts, and ruleset flags.
 3. `JB721TiersHookStore` updates supply and reserve accounting.
-4. The hook mints the correct NFTs and the underlying terminal completes treasury accounting.
+4. The hook mints the intended NFTs and the terminal completes treasury accounting.
+
+**Failure Modes**
+- sold-out tiers, malformed metadata, or cross-currency pricing mistakes
+- pay-hook participation flags do not match the user's assumptions
+- split-routing or hook behavior changes what part of the payment actually mints
 
-**Failure cases that matter:** sold-out tiers, bad metadata, cross-currency pricing mistakes, paused pay-hook behavior, and split-routing edge cases when part of the payment should bypass normal minting assumptions.
+**Postconditions**
+- the intended tiers are minted and store accounting reflects the updated supply and reserve state
 
 ## Journey 4: Mint Reserves And Operate Tier Inventory Over Time
 
-**Starting state:** the collection is live and the owner needs to manage what exists for future minters versus reserve recipients.
+**Actor:** owner or authorized operator.
+
+**Intent:** manage tier inventory and reserve behavior after launch.
 
-**Success:** reserves, new tiers, removed tiers, and editable fields evolve without corrupting ownership or supply history.
+**Preconditions**
+- the collection is live
+- the operator has the required permission surfaces to mutate tiers or mint reserves
 
-**Flow**
-1. Authorized operators use the hook's tier-management surfaces to add, remove, or adjust tiers.
-2. Reserve minting uses the configured reserve frequency and reserve beneficiary settings instead of ad hoc treasury actions.
-3. The store keeps historical tier state coherent so existing token IDs continue to resolve correctly.
-4. Downstream products such as Croptop, Banny, and Revnets can continue assuming stable tier semantics.
+**Main Flow**
+1. Use tier-management surfaces to add, remove, or adjust tiers.
+2. Mint reserves through the configured reserve logic.
+3. Let the store preserve historical tier state so old token IDs still resolve correctly.
+4. Keep downstream products assuming stable tier semantics whenever possible.
+
+**Failure Modes**
+- tier mutations surprise downstream products or resolvers
+- reserve accounting is misread as ordinary minting
+
+**Postconditions**
+- live tier inventory and reserve state match the operator's configured collection policy
 
 ## Journey 5: Let Holders Cash Out Tier Positions
 
-**Starting state:** a holder owns one or more NFTs from a hook-enabled project and the active ruleset allows surplus-backed exits.
+**Actor:** holder.
+
+**Intent:** exit a tier position through the project's cash-out path.
 
-**Success:** the holder burns the intended tier exposure and receives the correct reclaim value through the core terminal.
+**Preconditions**
+- the holder owns one or more NFTs from the hook-enabled project
+- the active ruleset allows a surplus-backed exit
 
-**Flow**
-1. The holder calls the project's cash-out path on the terminal.
-2. The hook participates in the cash-out calculation so tier-specific weight and store state are reflected correctly.
-3. The terminal settles reclaim value and the NFT position is burned or otherwise marked as consumed by the exit path.
+**Main Flow**
+1. Call the project's cash-out path on the terminal.
+2. Let the hook participate in cash-out calculation so tier state is reflected.
+3. Burn or consume the tier exposure as required by the exit path.
+4. Receive the reclaim value through the terminal that holds the asset.
 
-**Edge conditions that change user experience:** ERC-20 cash-out surfaces, tier splits, reserve accounting drift, broken downstream terminals, and projects that use the hook for metadata only versus economically binding flows.
+**Failure Modes**
+- the project uses the hook for metadata only and the holder assumes an economic cash-out path exists
+- terminal behavior or reserve drift changes reclaim expectations
+
+**Postconditions**
+- the holder exits the tier position through the hook-aware terminal path or learns that no such economic path is active
 
 ## Journey 6: Compose A Custom Product On Top Of The Standard Hook
 
-**Starting state:** the team wants product-specific rendering or business rules but does not want to fork tier issuance.
+**Actor:** integrator or downstream product team.
+
+**Intent:** build collection-specific behavior without reimplementing hook economics.
+
+**Preconditions**
+- the team wants custom presentation or app-layer logic
+- the team does not want to fork pricing, reserve, and treasury behavior
 
-**Success:** the product resolver or wrapper composes with the hook instead of reimplementing pricing, tier accounting, and treasury logic.
+**Main Flow**
+1. Plug a custom resolver or wrapper into the hook.
+2. Keep collection-specific behavior outside this repo.
+3. Audit hook-store interactions here first, then audit the downstream wrapper.
 
-**Flow**
-1. Plug a custom resolver into the hook for metadata and product-specific presentation.
-2. Keep collection-specific behavior in the downstream repo while leaving pay, reserve, and cash-out semantics in this repo.
-3. Audit hook-store interactions here first, then audit the downstream resolver or wrapper.
+**Failure Modes**
+- downstream products reimplement hook behavior and drift from canonical accounting
+- teams blame the hook for bugs that actually live in the resolver or wrapper
+
+**Postconditions**
+- the custom product reuses canonical hook economics while isolating collection-specific behavior downstream
 
 ## Journey 7: Mint NFTs To The Correct Beneficiary During Cross-Chain Payments
 
-**Starting state:** a sucker pays the project on behalf of a remote user via `payRemote`, and the 721 hook needs to mint NFTs and accrue credits to the real user instead of the sucker contract.
+**Actor:** cross-chain payer or integrator.
+
+**Intent:** preserve the real remote beneficiary when a sucker relays a payment.
+
+**Preconditions**
+- a sucker or relay path pays on behalf of a remote user
+- relay-beneficiary metadata is encoded correctly
+
+**Main Flow**
+1. The sucker calls `terminal.pay()` with relay-beneficiary metadata.
+2. `_mintAndUpdateCredits` resolves the relay beneficiary when `payer == beneficiary`.
+3. NFT minting and credit accounting use the resolved remote user.
+
+**Failure Modes**
+- relay metadata is missing or malformed
+- downstream systems attribute NFTs or credits to the sucker instead of the user
+
+**Postconditions**
+- NFT minting and credit accounting attribute the remote payment to the correct beneficiary
 
-**Success:** NFTs mint to and pay credits accrue to the real remote user.
+## Trust Boundaries
 
-**Flow**
-1. The sucker calls `terminal.pay()` with itself as both payer and beneficiary, embedding the real user's address in the `JB_RELAY_BENEFICIARY` metadata key.
-2. `_mintAndUpdateCredits` detects that `payer == beneficiary` and finds relay-beneficiary metadata.
-3. All NFT minting and credit accounting uses the resolved relay beneficiary instead of the sucker address.
+- `JB721TiersHookStore` is the accounting backend and should be treated as part of the same economic surface as the hook
+- custom token URI resolvers are part of the trusted collection surface
+- core terminals remain the source of treasury accounting truth around the hook
 
 ## Hand-Offs
 

package/foundry.toml

@@ -13,6 +13,8 @@ runs = 1024
 depth = 100
 fail_on_revert = false
 
+[lint]
+exclude_lints = ["pascal-case-struct", "mixed-case-variable"]
 [fmt]
 number_underscore = "thousands"
 multiline_func_header = "all"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bananapus/721-hook-v6",
-  "version": "0.0.34",
+  "version": "0.0.36",
   "license": "MIT",
   "repository": {
     "type": "git",

package/references/operations.md

@@ -9,7 +9,9 @@
 ## Change Checklist
 
 - If you edit hook initialization, verify deployer config structs and project-launch helpers still encode the same assumptions.
-- If you edit tier config or metadata behavior, inspect [`src/structs/`](../src/structs/) and the corresponding interfaces in [`src/interfaces/`](../src/interfaces/).
+- If you edit tier config or metadata behavior, inspect the corresponding structs and interfaces in `src/structs/` and `src/interfaces/`.
+- If you edit reserve behavior, verify pending reserve counts, default reserve beneficiary semantics, and cash-out denominator effects together.
+- If you edit discount behavior, verify mint price and cash-out weight separately. They are intentionally not the same quantity.
 - If you touch permissions, verify the caller path and permission constants still line up with the downstream ecosystem package that defines them.
 - If you touch URI behavior, confirm whether the issue belongs in this repo or in a downstream resolver contract that the hook calls.
 
@@ -24,5 +26,7 @@
 
 - [`test/Fork.t.sol`](../test/Fork.t.sol) for live-integration assumptions.
 - [`test/TestAuditGaps.sol`](../test/TestAuditGaps.sol) for known edge cases the repo authors considered worth pinning down.
-- [`test/unit/`](../test/unit/) when you need a narrow function-level proof before editing a broad runtime path.
-- [`script/helpers/`](../script/helpers/) when a deployment or launch question is really about config assembly rather than contract behavior.
+- [`test/TestCheckpoints.t.sol`](../test/TestCheckpoints.t.sol) when you need a narrow function-level proof before editing a broad runtime path.
+- [`test/invariants/TierLifecycleInvariant.t.sol`](../test/invariants/TierLifecycleInvariant.t.sol) and [`test/invariants/TieredHookStoreInvariant.t.sol`](../test/invariants/TieredHookStoreInvariant.t.sol) when a local patch may have broken store-level relationships.
+- [`test/audit/CodexRetroactiveReserveBeneficiaryDilution.t.sol`](../test/audit/CodexRetroactiveReserveBeneficiaryDilution.t.sol) when reserve-beneficiary or pending-reserve behavior changes.
+- [`script/Deploy.s.sol`](../script/Deploy.s.sol) when a deployment or launch question is really about config assembly rather than contract behavior.

package/references/runtime.md

@@ -22,11 +22,12 @@
 - Discount behavior: price discounts affect mint eligibility but cash-out weight still tracks the original tier price. Do not conflate the two.
 - Voting units: verify whether a tier uses explicit voting units or falls back to price-based voting power before changing governance-facing math.
 - Tier removal and cleanup: removing tiers is not the same as cleaning the sorted tier list. Storage cleanup behavior matters.
+- Default reserve beneficiary changes: they affect which tiers count pending reserves unless a tier-specific beneficiary overrides it. That is an economic change, not just an admin update.
 
 ## Tests To Trust First
 
-- [`test/invariants/`](../test/invariants/) for broad accounting invariants.
-- [`test/E2E/`](../test/E2E/) for launch and end-to-end payment flows.
-- [`test/regression/`](../test/regression/) for previously broken edge cases.
+- [`test/Fork.t.sol`](../test/Fork.t.sol) for launch and live integration flows.
 - [`test/TestVotingUnitsLifecycle.t.sol`](../test/TestVotingUnitsLifecycle.t.sol) for voting-unit lifecycle behavior.
-- [`test/TestSafeTransferReentrancy.t.sol`](../test/TestSafeTransferReentrancy.t.sol) and [`test/721HookAttacks.t.sol`](../test/721HookAttacks.t.sol) for reentrancy and attack-surface checks.
+- [`test/TestCheckpoints.t.sol`](../test/TestCheckpoints.t.sol) for checkpoint/module behavior.
+- [`test/invariants/TierLifecycleInvariant.t.sol`](../test/invariants/TierLifecycleInvariant.t.sol) and [`test/invariants/TieredHookStoreInvariant.t.sol`](../test/invariants/TieredHookStoreInvariant.t.sol) for store-level lifecycle invariants.
+- [`test/TestSafeTransferReentrancy.t.sol`](../test/TestSafeTransferReentrancy.t.sol), [`test/721HookAttacks.t.sol`](../test/721HookAttacks.t.sol), [`test/audit/CodexRetroactiveReserveBeneficiaryDilution.t.sol`](../test/audit/CodexRetroactiveReserveBeneficiaryDilution.t.sol), and [`test/TestAuditGaps.sol`](../test/TestAuditGaps.sol) for reentrancy and attack-surface checks.

package/src/JB721TiersHook.sol

@@ -110,7 +110,7 @@ contract JB721TiersHook is JBOwnable, ERC2771Context, JB721Hook, IJB721TiersHook
     uint256 internal _packedPricingContext;
 
     /// @notice The checkpoint module that manages IVotes-compatible checkpointed voting power for this hook's NFTs.
-    /// @dev Set once during `initialize()`. Pass this to JBTokenDistributor as the IVotes token.
+    /// @dev Lazily deployed on the first transfer. Pass this to JBTokenDistributor as the IVotes token.
     IJB721Checkpoints public override CHECKPOINTS;
 
     //*********************************************************************//
@@ -307,9 +307,6 @@ contract JB721TiersHook is JBOwnable, ERC2771Context, JB721Hook, IJB721TiersHook
                 || flags.preventOverspending || flags.issueTokensForSplits
         ) STORE.recordFlags(flags);
 
-        // Deploy the checkpoint module for IVotes-compatible voting power.
-        CHECKPOINTS = CHECKPOINTS_DEPLOYER.deploy({hook: address(this), store: STORE});
-
         // Transfer ownership to the initializer.
         _transferOwnership(_msgSender());
     }
@@ -460,9 +457,7 @@ contract JB721TiersHook is JBOwnable, ERC2771Context, JB721Hook, IJB721TiersHook
         string calldata baseUri,
         string calldata contractUri,
         IJB721TokenUriResolver tokenUriResolver,
-        // forge-lint: disable-next-line(mixed-case-variable)
         uint256 encodedIPFSUriTierId,
-        // forge-lint: disable-next-line(mixed-case-variable)
         bytes32 encodedIPFSUri
     )
         external
@@ -794,6 +789,11 @@ contract JB721TiersHook is JBOwnable, ERC2771Context, JB721Hook, IJB721TiersHook
         // slither-disable-next-line reentrency-events,calls-loop
         STORE.recordTransferForTier({tierId: tierId, from: from, to: to});
 
+        // Deploy the checkpoint module lazily on the first transfer.
+        if (address(CHECKPOINTS) == address(0)) {
+            CHECKPOINTS = CHECKPOINTS_DEPLOYER.deploy({hook: address(this), store: STORE});
+        }
+
         // Notify the checkpoint module to update checkpointed voting power.
         CHECKPOINTS.onTransfer({from: from, to: to, tokenId: tokenId});
     }

package/src/JB721TiersHookProjectDeployer.sol

@@ -124,7 +124,6 @@ contract JB721TiersHookProjectDeployer is ERC2771Context, JBPermissioned, IJB721
         returns (uint256 rulesetId, IJB721TiersHook hook)
     {
         // Get the project's projects contract.
-        // forge-lint: disable-next-line(mixed-case-variable)
         IJBProjects PROJECTS = DIRECTORY.PROJECTS();
 
         // Enforce permissions.

package/src/JB721TiersHookStore.sol

@@ -66,7 +66,6 @@ contract JB721TiersHookStore is IJB721TiersHookStore {
     /// @custom:param hook The 721 contract that the tier belongs to.
     /// @custom:param tierId The ID of the tier to get the encoded IPFS URI of.
     /// @custom:returns The encoded IPFS URI.
-    // forge-lint: disable-next-line(mixed-case-variable)
     mapping(address hook => mapping(uint256 tierId => bytes32)) public override encodedIPFSUriOf;
 
     /// @notice Returns the largest tier ID currently used on the provided 721 contract.
@@ -1344,7 +1343,7 @@ contract JB721TiersHookStore is IJB721TiersHookStore {
     /// @notice Record a new encoded IPFS URI for a tier.
     /// @param tierId The ID of the tier to set the encoded IPFS URI of.
     /// @param encodedIPFSUri The encoded IPFS URI to set for the tier.
-    // forge-lint: disable-next-line(mixed-case-function, mixed-case-variable)
+    // forge-lint: disable-next-line(mixed-case-function)
     function recordSetEncodedIPFSUriOf(uint256 tierId, bytes32 encodedIPFSUri) external override {
         encodedIPFSUriOf[msg.sender][tierId] = encodedIPFSUri;
     }

package/src/abstract/JB721Hook.sol

@@ -49,7 +49,6 @@ abstract contract JB721Hook is ERC721, IJB721Hook {
     //*********************************************************************//
 
     /// @notice The ID of the project that this contract is associated with.
-    // forge-lint: disable-next-line(mixed-case-variable)
     uint256 public override PROJECT_ID;
 
     //*********************************************************************//

package/src/interfaces/IJB721TiersHook.sol

@@ -234,9 +234,7 @@ interface IJB721TiersHook is IJB721Hook {
         string calldata baseUri,
         string calldata contractUri,
         IJB721TokenUriResolver tokenUriResolver,
-        // forge-lint: disable-next-line(mixed-case-variable)
         uint256 encodedIPFSUriTierId,
-        // forge-lint: disable-next-line(mixed-case-variable)
         bytes32 encodedIPFSUri
     )
         external;

package/src/interfaces/IJB721TiersHookStore.sol

@@ -247,7 +247,7 @@ interface IJB721TiersHookStore {
     /// @notice Record a new encoded IPFS URI for a tier.
     /// @param tierId The ID of the tier to set the encoded IPFS URI of.
     /// @param encodedIPFSUri The encoded IPFS URI to set for the tier.
-    // forge-lint: disable-next-line(mixed-case-function, mixed-case-variable)
+    // forge-lint: disable-next-line(mixed-case-function)
     function recordSetEncodedIPFSUriOf(uint256 tierId, bytes32 encodedIPFSUri) external;
 
     /// @notice Record a newly set token URI resolver.

package/src/libraries/JB721Constants.sol

@@ -8,6 +8,5 @@ library JB721Constants {
     /// @notice The metadata ID used to identify the 721 beneficiary entry in payment metadata.
     /// @dev When a sucker pays on behalf of a remote user, the real user's address is embedded under this key
     /// so NFTs mint to the correct recipient.
-    // forge-lint: disable-next-line(mixed-case-variable)
     bytes4 public constant BENEFICIARY_METADATA_ID = bytes4(keccak256("JB_721_BENEFICIARY"));
 }

package/src/structs/JB721InitTiersConfig.sol

@@ -8,7 +8,6 @@ import {JB721TierConfig} from "./JB721TierConfig.sol";
 /// @custom:member tiers The tiers to initialize the hook with.
 /// @custom:member currency The currency that the tier prices are denoted in. See `JBPrices`.
 /// @custom:member decimals The number of decimals in the fixed point tier prices.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JB721InitTiersConfig {
     JB721TierConfig[] tiers;
     uint32 currency;

package/src/structs/JB721Tier.sol

@@ -21,7 +21,6 @@ import {JB721TierFlags} from "./JB721TierFlags.sol";
 /// an NFT from this tier is minted. Out of `JBConstants.SPLITS_TOTAL_PERCENT`.
 /// @custom:member resolvedUri A resolved token URI for NFTs in this tier. Only available if the NFT this tier belongs
 /// to has a resolver.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JB721Tier {
     uint32 id;
     uint104 price;
@@ -30,7 +29,6 @@ struct JB721Tier {
     uint104 votingUnits;
     uint16 reserveFrequency;
     address reserveBeneficiary;
-    // forge-lint: disable-next-line(mixed-case-variable)
     bytes32 encodedIPFSUri;
     uint24 category;
     uint8 discountPercent;

package/src/structs/JB721TierConfig.sol

@@ -23,14 +23,12 @@ import {JB721TierConfigFlags} from "./JB721TierConfigFlags.sol";
 /// an NFT from this tier is minted. Out of `JBConstants.SPLITS_TOTAL_PERCENT`.
 /// @custom:member splits The splits to use for this tier's split group. These define where the split portion of the
 /// tier's price gets routed when an NFT from this tier is minted.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JB721TierConfig {
     uint104 price;
     uint32 initialSupply;
     uint32 votingUnits;
     uint16 reserveFrequency;
     address reserveBeneficiary;
-    // forge-lint: disable-next-line(mixed-case-variable)
     bytes32 encodedIPFSUri;
     uint24 category;
     uint8 discountPercent;

package/src/structs/JB721TierConfigFlags.sol

@@ -14,7 +14,6 @@ pragma solidity ^0.8.0;
 /// @custom:member cantIncreaseDiscountPercent If the tier cannot have its discount increased.
 /// @custom:member cantBuyWithCredits If true, this tier cannot be purchased using accumulated pay credits. Only fresh
 /// payment value counts toward this tier's price.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JB721TierConfigFlags {
     bool allowOwnerMint;
     bool useReserveBeneficiaryAsDefault;

package/src/structs/JB721TierFlags.sol

@@ -7,7 +7,6 @@ pragma solidity ^0.8.0;
 /// @custom:member cantBeRemoved A boolean indicating whether attempts to remove this tier will revert.
 /// @custom:member cantIncreaseDiscountPercent If the tier cannot have its discount increased.
 /// @custom:member cantBuyWithCredits If true, this tier cannot be purchased using accumulated pay credits.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JB721TierFlags {
     bool allowOwnerMint;
     bool transfersPausable;

package/src/structs/JB721TiersHookFlags.sol

@@ -11,7 +11,6 @@ pragma solidity ^0.8.0;
 /// the NFTs being minted will revert.
 /// @custom:member issueTokensForSplits A boolean indicating whether payers receive token credit for the portion of
 /// their payment that is routed to tier splits. When false (default), weight is reduced proportionally.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JB721TiersHookFlags {
     bool noNewTiersWithReserves;
     bool noNewTiersWithVotes;

package/src/structs/JB721TiersMintReservesConfig.sol

@@ -3,7 +3,6 @@ pragma solidity ^0.8.0;
 
 /// @custom:member tierId The ID of the tier to mint from.
 /// @custom:member count The number of NFTs to mint from that tier.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JB721TiersMintReservesConfig {
     uint32 tierId;
     uint16 count;

package/src/structs/JB721TiersRulesetMetadata.sol

@@ -6,7 +6,6 @@ pragma solidity ^0.8.0;
 /// @custom:member pauseTransfers A boolean indicating whether NFT transfers are paused during this ruleset.
 /// @custom:member pauseMintPendingReserves A boolean indicating whether pending/outstanding NFT reserves can be minted
 /// during this ruleset.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JB721TiersRulesetMetadata {
     bool pauseTransfers;
     bool pauseMintPendingReserves;

package/src/structs/JB721TiersSetDiscountPercentConfig.sol

@@ -3,7 +3,6 @@ pragma solidity ^0.8.0;
 
 /// @custom:member tierId The ID of the tier to set the discount percent for.
 /// @custom:member discountPercent The discount percent to set for the tier.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JB721TiersSetDiscountPercentConfig {
     uint32 tierId;
     uint16 discountPercent;

package/src/structs/JBBitmapWord.sol

@@ -5,7 +5,6 @@ pragma solidity ^0.8.0;
 /// `JBBitmap` matrix is a "word".
 /// @custom:member The information stored at the index.
 /// @custom:member The index.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JBBitmapWord {
     uint256 currentWord;
     uint256 currentDepth;

package/src/structs/JBDeploy721TiersHookConfig.sol

@@ -12,7 +12,6 @@ import {IJB721TokenUriResolver} from "../interfaces/IJB721TokenUriResolver.sol";
 /// @custom:member contractUri The URI where this contract's metadata can be found.
 /// @custom:member tiersConfig The NFT tiers and pricing config to launch the hook with.
 /// @custom:member flags A set of boolean options to configure the hook with.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JBDeploy721TiersHookConfig {
     string name;
     string symbol;

package/src/structs/JBLaunchProjectConfig.sol

@@ -10,7 +10,6 @@ import {JBPayDataHookRulesetConfig} from "./JBPayDataHookRulesetConfig.sol";
 /// @custom:member rulesetConfigurations The ruleset configurations to queue.
 /// @custom:member terminalConfigurations The terminal configurations to add for the project.
 /// @custom:member memo A memo to pass along to the emitted event.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JBLaunchProjectConfig {
     string projectUri;
     JBPayDataHookRulesetConfig[] rulesetConfigurations;

package/src/structs/JBLaunchRulesetsConfig.sol

@@ -9,7 +9,6 @@ import {JBPayDataHookRulesetConfig} from "./JBPayDataHookRulesetConfig.sol";
 /// @custom:member rulesetConfigurations The ruleset configurations to queue.
 /// @custom:member terminalConfigurations The terminal configurations to add for the project.
 /// @custom:member memo A memo to pass along to the emitted event.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JBLaunchRulesetsConfig {
     uint56 projectId;
     JBPayDataHookRulesetConfig[] rulesetConfigurations;

package/src/structs/JBPayDataHookRulesetConfig.sol

@@ -32,7 +32,6 @@ import {JBPayDataHookRulesetMetadata} from "./JBPayDataHookRulesetMetadata.sol";
 /// its balance in each payment terminal while the ruleset is active. Amounts are fixed point numbers using the same
 /// number of decimals as the corresponding terminal. The `payoutLimit` and `surplusAllowance` parameters must fit in
 /// a `uint232`.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JBPayDataHookRulesetConfig {
     uint48 mustStartAtOrAfter;
     uint32 duration;

package/src/structs/JBPayDataHookRulesetMetadata.sol

@@ -28,7 +28,6 @@ pragma solidity ^0.8.0;
 /// during
 /// this ruleset.
 /// @custom:member metadata Metadata of the metadata, up to uint8 in size.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JBPayDataHookRulesetMetadata {
     uint16 reservedPercent;
     uint16 cashOutTaxRate;

package/src/structs/JBQueueRulesetsConfig.sol

@@ -6,7 +6,6 @@ import {JBPayDataHookRulesetConfig} from "./JBPayDataHookRulesetConfig.sol";
 /// @custom:member projectId The ID of the project to queue rulesets for.
 /// @custom:member rulesetConfigurations The ruleset configurations to queue.
 /// @custom:member memo A memo to pass along to the emitted event.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JBQueueRulesetsConfig {
     uint56 projectId;
     JBPayDataHookRulesetConfig[] rulesetConfigurations;

package/src/structs/JBStored721Tier.sol

@@ -13,7 +13,6 @@ pragma solidity ^0.8.0;
 /// purchased.
 /// @custom:member packedBools Packed boolean flags: allowOwnerMint, transfersPausable, useVotingUnits,
 /// cantBeRemoved, cantIncreaseDiscountPercent, cantBuyWithCredits.
-// forge-lint: disable-next-line(pascal-case-struct)
 struct JBStored721Tier {
     uint104 price;
     uint32 remainingSupply;