feat(dns): support content-scoped record delete

[pcfreak30]

Exposes the content-scoped record delete added in ipfs-sdk v0.1.82 in the dns records delete command, and surfaces the synthesized record id in dns records list.

dns records delete now takes an optional --content selector:

• providing --content deletes only the record with that exact value
• omitting it deletes the whole RRSet (backward compatible with previous behavior)

This lets callers remove a single TXT/record value without wiping every record of that name+type.

dns records list now shows an ID column for each record, so callers can reference specific record values returned by the API. The keepWholeValue table layout is updated for the new column.

Dependency: bumps go.lumeweb.com/ipfs-sdk to v0.1.82 and absorbs the WebsiteItem.zone_id rename (DnsZoneId -> ZoneId) that shipped in that SDK release.

Tests:

• content-scoped delete forwards the --content selector to the service
• omitting content still deletes the whole RRSet
• records table renders the id column

---

Summary

This pull request adds support for content-scoped DNS record deletion, allowing users to delete a single DNS record by its exact content value rather than only deleting the entire RRSet (all records matching a name+type).

Key Changes

Content-Scoped Deletion Support

• internal/core/dns/service.go: The DeleteRecord method signature now accepts an optional content ...string variadic parameter. When a content value is provided, only the record with that exact content is deleted; otherwise, the entire RRSet (all records for the name/type) is removed as before.
• internal/catalogops/dns.go:
  • Added a new optional --content argument to the dns_records_delete operation, allowing users to specify the exact content value of the record(s) to delete.
  • The operation now forwards the content selector to the service when provided and returns it in the result (DNSRecordDeleteResult.Content), making single-record deletion more precise.
  • Updated the operation description to document the new behavior, including the distinction between content-scoped deletion and whole-RRSet deletion.
  • Added Content field to the DNSRecordDeleteResult struct (with omitempty for backward compatibility).

Improved DNS Record Table Output

• internal/cli/dns.go and internal/cli/output.go: The DNS records table now includes the record's ID as the first column (with headers changed from ["NAME", "TYPE", "CONTENT", "TTL", "STATUS"] to ["ID", "NAME", "TYPE", "CONTENT", "TTL", "STATUS"]), helping users identify individual records when a name+type group contains multiple values.

Bug Fix: Website DNS Zone ID Display

• internal/cli/catalog_websites_wiring.go and internal/cli/websites.go: Fixed the field name used to display a website's DNS Zone ID from the outdated DnsZoneId to the current ZoneId, ensuring the correct data is shown.

Testing

• internal/catalogops/tool_controls_test.go: Added TestDNSRecordsDeleteContentScoped verifying that:
  • Providing --content forwards the exact value to the service for targeted deletion.
  • Omitting content still deletes the whole RRSet (backward compatible).
• internal/cli/dns_test.go: Updated mock service signature and existing tests to account for the new ID column in the table output.

Impact

Users can now delete individual DNS records by their exact content value (e.g., a specific TXT record) without having to recreate other records that share the same name and type. The change is backward-compatible—existing behavior (whole-RRSet deletion) is preserved when no content is specified.

[github-actions]

Code Coverage Report

Total Coverage: 52.1%

Generated from commit: 26105e8
Repository: LumeWeb/pinner-cli

[kody-ai]

All new GORM operations introduced in this PR (e.g. ListRecords calls in the dns_records_delete handler) must use .WithContext(ctx) with a timeout to prevent queries from running indefinitely. This rule does not exempt these calls, so ensure each GORM query includes a context with timeout, unless they are within a db.RetryableComponentLock call.

Kody rule violation: Disallow GORM queries without timeout

[kody-ai]

All new GORM operations introduced in this PR (e.g. ListRecords calls in the dns_records_delete handler) must use .WithContext(ctx) with a timeout to prevent queries from running indefinitely. This rule does not exempt these calls, so ensure each GORM query includes a context with timeout, unless they are within a db.RetryableComponentLock call.

Kody rule violation: Disallow GORM queries without timeout

[kody-ai]

In internal/catalogops/dns.go, calls to svc.ListRecords, svc.DeleteRecord, and resolveZoneID pass the request context directly without wrapping in a timeout context, which all GORM operations should use via .WithContext(ctx) with a per-query timeout to prevent runaway queries.

Kody rule violation: Disallow GORM queries without timeout

[kody-ai]

Kody Review Complete

Great news! 🎉
No issues were found that match your current review configurations.

Keep up the excellent work! 🚀

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	✅

Access your configuration settings here.

​