Skip to content

Add freshness validation and the required docs pull-request check #162

Description

@lastobelus

Target

Implement this ticket in lastobelus/lastcode-docs after the first content and media set exists.

Acceptance

  • Add one repository command and one GitHub check named docs / validate.
  • Check the covered LastCode commit, registry hash, affected feature IDs, acknowledgements, docs evidence, and enabled capture commits.
  • Check page structure, internal links, media, privacy patterns, accessibility, README references, vendored-skill hashes, frozen dependencies, focused tests, and the production build.
  • Report external-link failures as warnings.
  • Enforce the approved media and repository budgets.
  • Require one maintainer approval, dismiss it after a push, disable auto-merge, and block Merge until docs / validate passes.
  • Seed the first freshness record against the shared LastCode release commit.
  • Do not generate or rewrite captures in GitHub CI.

This check protects publication. It does not promise continuous freshness, security, uptime, or concurrent-writer safety.

Activity

  1. lastobelus commented on Oct 6, 2026

    @lastobelus
    OwnerAuthor

    Carry forward the docs Action setup that remained incomplete after #172 merged.

    Before relying on the docs project's Wait for PR Action, import the merged t3.json Action in the lastcode-docs project, enable agent resume, and confirm resumeEligible: true. The product project's Action does not target the docs repository.

    When adding the required docs / validate check, update the docs waiter's readiness rules and focused tests to require it. Reassess a local-validation Action only after actual validation repeatedly requires three or more waits. It was deliberately deferred rather than implemented speculatively.

    This archive handoff does not complete freshness validation or reopen media work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions