Fixed Content Info panel showing "Unknown" for timestamp fields

[everscending]

Description

In admin-content-form.template.ts, the Content Info panel is showing "Unknown" for Created/Modified/Published
because its referencing data.data?.created_at, data.data?.updated_at, and data.data?.published_at, instead
of data.created_at, data.updated_at, data.published_at.

Fixes # 688

Changes

• .gitignore
  -- added .history folder which is used by the local history vscode plugin
• packages/core/src/routes/admin-content.ts, lines 675-677
  -- added created_at/updated_at/published_at fields to contentForm object
• packages/core/src/templates/pages/admin-content-form.template.ts, lines 282 - 295
  -- Now pulling timestamp values from data instead of data.data

Testing

1. Create content
2. Go to Edit Content form for newly created content
3. Verify values appear for timestamp fields

Unit Tests

• Added/updated unit tests
• All unit tests passing

E2E Tests

• Added/updated E2E tests
• All E2E tests passing

Screenshots/Videos

Checklist

• Code follows project conventions
• Tests added/updated and passing
• Type checking passes
• No console errors or warnings
• Documentation updated (if needed)

---

Generated with Claude Code in Conductor

[everscending]

Fyi, the tests/e2e/39-slug-generation.spec.ts E2E test is failing for me on this branch and also the main branch:

Error: locator.click: Test timeout of 30000ms exceeded.
Call log:

• waiting for locator('a:has-text("Edit Mode Test Page")').first()

227 | // Click on the content to edit it
228 | const contentLink = page.locator(a:has-text("Edit Mode Test Page")).first()

229 | await contentLink.click()
| ^
230 | await page.waitForTimeout(1000)
231 |
232 | const titleField = page.locator('input[name="title"]')
at /Users/Shared/Projects/sonicjs/tests/e2e/39-slug-generation.spec.ts:229:23

[lane711]

Hey @everscending — thank you for this fix! Your Content Info panel timestamp fix was cherry-picked and merged as PR #703. It shipped in v2.8.3. Appreciate you digging into the template data path issue. 🙏

For context: we cherry-pick fork PRs into our own branches to work around GitHub Actions CI limitations with fork secrets. Your authorship is preserved in the git history.