chore(docs): refresh README + env.example for phases 4–5 shipped#77
Merged
Conversation
- Phase status table flips 4 + 5 from ⬜ to 🟢 with one-line per-spec
summaries.
- "What works today" gains Phase 4 (deployments — workflow runs
storage + timeline UI + Overview success-rate widget) and Phase 5
(website monitoring — monitor MVP + scheduled checks + Overview
uptime KPI + Reverb live updates) sections.
- composer dev callout notes the scheduler tick is what drives spec
024's monitor probes — without it (or a real cron), monitors stay
on whatever state the last manual probe left them in.
- Repository layout adds the new bounded contexts + directories that
shipped (Domain/Monitoring with its Probes/, Events/ for the three
broadcast classes, Policies/, Pages/Deployments + Pages/Monitoring,
lib/{workflowRunStyles,websiteStyles}.ts).
- env.example BROADCAST_CONNECTION comment lists all three live
broadcast events (ActivityEventCreated, WorkflowRunUpserted,
WebsiteCheckRecorded) instead of just spec 019. No new env keys
shipped in phases 4 or 5; AGENT_SHARED_SECRET stays as the
placeholder for phase 6.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Catches up the user-facing docs after phase 4 + phase 5 closed out. No code changes.
Summary
composer devcallout now notes the scheduler tick is what drives spec 024's monitor probes — without it (or a real cron), monitors stay on whatever state the last manual probe left them in.app/Domain/Monitoring/(withProbes/for the result DTO),app/Events/(the three broadcast classes —ActivityEventCreated,WorkflowRunUpserted,WebsiteCheckRecorded),app/Policies/(Project / Repository / Website),Pages/Deployments/+Pages/Monitoring/Websites/,lib/workflowRunStyles.ts+lib/websiteStyles.ts(shared tone helpers)..env.exampleBROADCAST_CONNECTIONcomment lists all three live broadcast events instead of just spec 019. No new env keys shipped in phases 4 or 5;AGENT_SHARED_SECRETstays as the pre-seeded placeholder for phase 6.Test plan
Note
Pure documentation. Squash-merging this is fine without the usual self-review pass; the diff is two files and ~50 lines.