feat(integration): show the remaining code lifetime in link create

[abhisek]

Internal testing feedback on safedep/control-tower#1137: the link code expiry printed as a raw RFC 3339 instant (2026-09-22T08:34:44Z).

Change

• The table output of integration bitbucket link create shows the remaining lifetime under an EXPIRES column: in 15 min, in 1 h 30 min, expired, or in less than a minute.
• The plain and JSON output keep expires_at in RFC 3339 for scripts.
• The command doc states the split.

Tests

• TestFormatExpiresIn covers expired, sub-minute, rounding, whole hours, and mixed durations.
• go test and golangci-lint pass.

Note on history: the branch restarts from main after #63 squash-merged. An ours merge keeps the old branch commits in ancestry without content changes, so the diff against main is only this change.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PZmWHi9y5aCpBaxxWXU6Fo

---

Generated by Claude Code

Summary by CodeRabbit

• Improvements

  • Bitbucket link expiration details are now clearer across output formats.
  • Plain and JSON output show the exact expiration time in RFC 3339 UTC format.
  • Table output displays the remaining time in a human-readable format, such as “in 15m.”
  • Missing expiration values are handled safely in plain output.

• Documentation

  • Added guidance on consistent time and duration formatting across output formats.

[safedep]

SafeDep Report Summary

No dependency changes detected. Nothing to scan.

View complete scan results →

_{This report is generated by SafeDep GitHub App}

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: QUIET

Plan: Advanced

Run ID: e4a4b580-a3d9-4bdf-a7fb-cd1594bf3930

📥 Commits

Reviewing files that changed from the base of the PR and between 0be9c27 and 198e4a3.

📒 Files selected for processing (2)

• AGENTS.md
• docs/DEVGUIDE.md

Included review availability: Your plan provides up to 10 included reviews per hour; 7 remain after this review.

---

📝 Walkthrough

Walkthrough

Bitbucket link creation now shows relative expiration durations in table output while preserving RFC 3339 timestamps in plain and JSON output. Repository guidance defines shared humanization rules for table values.

Changes

Bitbucket expiration output

Layer / File(s)	Summary
Expiration output formatting internal/cmd/integration/bitbucket/link.go, docs/cmd/integration-bitbucket-link-create.md	Table output uses humanize.Time and an EXPIRES column. Plain output handles missing expiration values. Plain and JSON output retain RFC 3339 timestamps. Documentation describes these formats.
Humanized output guidance AGENTS.md, docs/DEVGUIDE.md	The guidance requires shared humanizers for table time and duration values. It specifies exact values for plain and JSON output and render-time clocks for table output.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to 198e4

Table output now shows relative expiration lifetimes while plain and JSON output retain exact RFC 3339 timestamps. The change is mergeable with no identified production risk.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 2 files. (2 skipped: 2 …	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: showing the remaining link-code lifetime in the Bitbucket link create output.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 2 files. (2 skipped: 2 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

_{Comment @coderabbitai help to get the list of available commands.}