Add devlogs to taxonomy and activity feeds

AGENTS.md

@@ -52,12 +52,17 @@ making changes; it is the authoritative operations and deployment runbook.
 - Preserve normal links to dedicated tag pages as the no-JavaScript baseline.
   Client-side filtering must remain a progressive enhancement with semantic
   buttons, keyboard support, and an announced result count.
-- Tag-directory counts and dedicated tag pages must include projects, blog
-  entries, and articles in the same discovery feed.
+- Tag-directory counts and dedicated tag pages must include projects, their
+  devlog entries, blog entries, and articles in the same discovery feed.
 - For remote projects, keep repository language labels and project-declared
   technology labels separate from their derived controlled tag slugs. Approved
   labels link to tag pages; unapproved labels remain visible, non-clickable, and
   mustard-colored but do not affect tag feeds or counts.
+- Apply that same controlled mapping to remote devlog topics. Approved topics
+  link to tag pages and populate `topic_tag_slugs`; unapproved topics remain
+  mustard labels and are excluded from discovery.
+- Keep project devlog entries in the homepage Recent Activity feed alongside
+  projects, blog entries, and articles, ordered by publication date.
 - When `README.md` changes, keep the README-derived example blog entry aligned
   with the runbook content it demonstrates.
 
@@ -78,9 +83,9 @@ making changes; it is the authoritative operations and deployment runbook.
   the relevant cache-busting version in the template and verify that generated
   pages reference the new asset URL.
 - For taxonomy changes, verify every entry tag has a matching `content/tags/`
-  record, tag counts match rendered project/blog/article usage, dedicated tag
-  URLs build, and listing filters work with valid, absent, and unknown query
-  values.
+  record, tag counts match rendered project/devlog/blog/article usage,
+  dedicated tag URLs build, and listing filters work with valid, absent, and
+  unknown query values.
 - Run `git diff --check` and review the exact diff before committing.
 - If a push was requested, verify the Gitea Action result, deployed revision,
   and site health instead of treating a successful `git push` as completion.