Deeka's Devlog

Sun, 16 Aug 2026 02:16:19 +0530

Launch developer journal as a Hugo site

Summary

Converted the centralized developer journal into a responsive Hugo site with project and tag archives, RSS output, normalized entry metadata, clean production builds, and compatibility with the Hugo version used by Cloudflare Pages.

Decisions

Keep the site deployment-agnostic and store generated journal entries under Hugo’s content directory
Use custom Hugo layouts and local styling instead of adding an external theme dependency
Use the backward-compatible Language.Lang template field for hosted builds

Learnings

Hugo uses taxonomy.html for individual tag result pages and terms.html for the tag index
Hosted build environments should pin the Hugo version or avoid APIs unavailable in older releases

Sun, 16 Aug 2026 02:15:32 +0530

Add configurable journal directory

Summary

Added a per-command directory option for generated Markdown, retained persistent environment-based configuration, documented location precedence, and updated the local shell configuration.

Decisions

Make the per-command directory option override DEVLOG_HOME
Keep DEVLOG_HOME as the persistent configuration and the existing developer-journal directory as the fallback

Learnings

Shell profile environment changes apply automatically to new shell sessions

Improve lent tracker mobile UX

Sun, 16 Aug 2026 01:21:44 +0530

Summary

Made the lent tracker responsive by collapsing the entry form behind an Add record button, expanding the outstanding card on mobile, and enabling horizontal table scrolling.

Decisions

Keep the lent list compact by hiding the entry form until explicitly opened.
Preserve table readability on narrow screens with a horizontally scrollable minimum-width table.

Add chit JSON export and import

Sun, 16 Aug 2026 01:21:15 +0530

Summary

Added bounded versioned JSON export and atomic append-only import for chit funds with nested installments, full-account and per-chit export actions, frontend preview, and raw archive submission.

Decisions

Use a nested versioned JSON archive that omits ownership and derived fields.
Preserve BOM-stripped raw JSON text for submission so backend lexical money validation rejects exponent notation and over-precision.
Use batched parent and installment inserts inside one transaction while re-imports intentionally create fresh duplicates.

Learnings

Browser JSON parsing can normalize numeric syntax before transport, so parsed preview data must remain separate from the submitted archive text.

Add lent archive export and import

Sun, 16 Aug 2026 01:20:51 +0530

Summary

Implemented versioned lent archive export and additive import with strict validation, atomic writes, ID remapping, frontend controls, cache invalidation, and test coverage.

Decisions

Use nested repayments in a versioned JSON archive so lent histories round-trip losslessly.
Make imports additive with new IDs instead of adding restore-specific conflict or idempotency storage.
Normalize money as exact decimal strings and enforce archive size and record limits before persistence.

Create three-month product roadmap

Wed, 12 Aug 2026 23:33:33 +0530

Summary

Reviewed Pennywise’s current personal-finance capabilities and created a dated three-month roadmap focused on faster transaction capture, flexible financial-data imports, recurring transactions, and a unified obligations view. Added the local roadmap directory to Git ignore.

Decisions

Prioritize smart repeat entry, flexible CSV import with duplicate protection, recurring transaction confirmation, and a unified obligations view
Keep roadmap documents local by ignoring the roadmap directory

Speed up transaction autocomplete suggestions

Wed, 12 Aug 2026 22:49:21 +0530

Summary

Reduced the transaction-name autocomplete debounce from 250 ms to 200 ms, updated the frontend documentation, and excluded the local devlog.md file from Git tracking.

Decisions

Use a 200 ms debounce to make autocomplete feel more responsive while retaining request throttling

Learnings

A previously tracked file must be removed from the Git index before a new ignore rule takes effect

Polish record and dashboard card UI

Mon, 10 Aug 2026 16:50:10 +0530

Summary

Removed redundant Record and Credit Card Usage chrome, clarified over-budget tile copy as rounded Nx budget, moved Daily Spend by Day under its chart without repeating the month, and scaled Monthly Cost so large totals stay inside narrow cards.

Decisions

Show over-budget utilisation as a whole-number multiplier of budget instead of a percentage above 100%
Use Math.round half-up on the multiplier so values like 5.6 read as 6x
Scale Monthly Cost with a container-query clamp instead of a fixed 52px font

Build Centralized Devlog CLI and Agent Skill

Sun, 09 Aug 2026 22:27:24 +0530

Summary

Built a Go CLI that accepts structured JSON from coding agents, validates and renders entries as Markdown, stores them safely by project, initializes local Git storage, and includes user and agent documentation.

Decisions

Keep devlog add plus its JSON schema as the stable contract between agents and storage
Use standard-library UUIDv7 generation for stable time-sortable entry identities without adding dependencies
Use exclusive file creation and numbered suffixes to prevent collision overwrites
Keep the agent skill focused on invoking the CLI instead of reproducing storage behavior

Learnings

A narrow CLI contract lets agent workflows remain stable while storage implementation details evolve
Agent-facing skill instructions benefit from a concise bundled reference separate from the human-facing project manual

Document forgot/reset password integration for external app

Sun, 09 Aug 2026 22:16:51 +0530

Summary

Explored the forgot-password and reset-password flow (handler, service, tokens, mailer, migrations, config) and wrote docs/forgot-reset-password-integration.md covering endpoints, request/response schemas, error matrix, token lifecycle, email link contract, and integration checklist for wiring another app to the API.

Decisions

Reset email links must point to the consuming frontend app’s /auth/reset-password page (which POSTs token + new_password to the API), not the raw API endpoint

Learnings

No CORS middleware exists in the codebase; cross-origin browser calls to /auth/forgot-password and /auth/reset-password need go-chi/cors added
forgot-password and reset-password have no rate limiting, unlike /auth/login and /auth/resend-verification

Add forgot-password flow, remove dead reset-password page

Sun, 09 Aug 2026 22:14:40 +0530

Summary

Added a forgot-password entry point on sign-in with a request-link page calling Goauth’s proxied /api/auth/forgot-password endpoint. Built a matching reset-password page/route/backend log-redaction first, then removed all of it after confirming Goauth’s emailed reset link goes straight to Goauth’s own domain and never routes back into Pennywise. Repositioned the Forgot password link below the Sign in button, bumped frontend to 5.0.2, and pushed three commits to main.

Decisions

Password reset is entirely Goauth’s responsibility end-to-end (its own hosted page, its own domain) — Pennywise only ever handles the forgot-password request step
Forgot-password success copy is always the same anti-enumeration message regardless of whether the email exists, matching Goauth’s own 200-always behavior

Learnings

An initial plan assumption (that the reset email links back into the app’s own frontend route) turned out to be wrong once the external auth service’s actual mailer behavior was confirmed — worth verifying live link/redirect behavior for any email-based flow before building UI around an assumed URL contract