fix(ant): add priority as an attribute on ANTs

ANTs can optionally provide a priority order of their records. This is how ar-io gateways will enforce undername limits. If no priority order is provided, records will be sorted lexigraphically

src/types/ant.ts

@@ -55,6 +55,7 @@ export const AntKeywordsSchema = z.array(z.string()); // TODO: add specific limi
 export const AntRecordSchema = z.object({
   transactionId: ArweaveTxIdSchema.describe('The Target ID of the undername'),
   ttlSeconds: z.number(),
+  priority: z.number().optional(),
 });
 export type AoANTRecord = z.infer<typeof AntRecordSchema>;
 export const AntRecordsSchema = z.record(z.string(), AntRecordSchema);
@@ -239,6 +240,7 @@ export interface AoANTWrite extends AoANTRead {
 export type AoANTSetBaseNameRecordParams = {
   transactionId: string;
   ttlSeconds: number;
+  priority?: number;
 };
 
 export type AoANTSetUndernameRecordParams = AoANTSetBaseNameRecordParams & {

tests/e2e/esm/index.test.ts

@@ -1096,7 +1096,13 @@ describe('e2e esm tests', async () => {
       it('should be able to get the ANT records', async () => {
         const records = await ant.getRecords();
         assert.ok(records);
-        // TODO: check enforcement of alphabetical order with '@' first
+        for (const record of Object.values(records)) {
+          assert(typeof record.transactionId === 'string');
+          assert(typeof record.ttlSeconds === 'number');
+          if (record.priority) {
+            assert(typeof record.priority === 'number');
+          }
+        }
       });
 
       it('should be able to get a @ record from the ANT', async () => {