Repository navigation
Description
Release decision remains not decided.
Summary
Candidate evidence and unresolved release gates — 24 October 2026
PR #457’s identified Netlify preview passes the tested rendering and journal deep-link/reload checks. This is candidate evidence—not production acceptance or a release decision.
Before deciding readiness:
- Determine whether the newsletter 404 and empty ebook reader block the agreed release scope.
- Review the broader Sentry, dependency and edge-function changes, including missing operational validation.
- Confirm effective production configuration, deployed SHA and required production checks.
- Identify the decision-maker, release approver, accepted exceptions, rollback owner, trigger and known-good deployment.
No human PR approval was established. PR prose/changelog still describe a superseded source-map redirect and need alignment with the current edge implementation.
Decision remains not decided. This update authorises no merge, deployment, rollback or issue closure.
Decide the evidence, approvals, blocking conditions and rollback arrangements required before Website v1.0 release. No decision deadline is established.
Context
The parent epic requires production routing, metadata, artwork, accessibility and build checks to pass. Existing newsletter and retained-form work remains independently assessed. A merged change or successful build alone does not establish production acceptance.
Options Considered
These are proposals for evaluation, not approved choices. Effort and commercial cost are unassessed.
- Release after all agreed gates pass: provides a clear acceptance boundary but keeps release dependent on outstanding evidence.
- Release with explicitly accepted exceptions: permits bounded deferrals but requires recorded risk acceptance and responsibilities.
- Hold release: avoids releasing with unresolved acceptance gaps but postpones availability.
Unanswered clarification questions
- Which production URLs and redirects require verification?
- Which metadata and social-sharing previews require verification?
- Which build checks and release evidence are required before launch?
- Which existing reader, newsletter and retained-form outcomes must be verified as launch-ready?
- Who approves editorial content and the final release, and how should those approvals be recorded?
- Which unresolved defects would prevent launch, and what rollback arrangements are required?
Decision
Proposed Netlify evidence requirements
Evaluate these as release gates—not an approved readiness decision:
- Built-site rendering and module-loading evidence from the build issue.
- Direct-load, refresh and asset acceptance from the routing issue.
- Identified deployment/SHA and effective Netlify configuration.
- Recorded unresolved failures, accepted exceptions, release approver and rollback responsibilities.
A successful build, preview HTTP response or merged PR alone does not establish production readiness.
Decision-maker
Not yet identified; confirmation required.
Outcome
Not decided.
Decision date
Not recorded.
Consequences
Pending the decision. Record release gates, accepted or rejected exceptions, evidence requirements, approval responsibilities and rollback arrangements. This record does not authorise deployment or rollback execution.
Linked Work
Proposed Sentry activation gates
Research findings and recommended options — 25 October 2026
Research recommendation: an errors-only launch configuration, with replay, performance tracing and preview monitoring disabled until separately approved. These recommendations are not an activation decision.
Repository snapshot: PR #457 has merged into develop (f99275b085cffd209b9bd42f6e463c0af643099a). This does not establish deployment or Sentry activation. At that revision, source enables replay at 10% of sessions / 100% of error sessions, with production trace sampling at 20% when a DSN is configured. Environment attribution derives from Vite mode rather than verified deployment context; the build plugin omits an explicit telemetry opt-out.
| Decision | Recommended proposal | Still unverified |
|---|---|---|
| Replay | Both replay rates 0; omit the replay integration initially | Deployed configuration |
| Performance | tracesSampleRate: 0 initially; consider 1% production sampling later | Traffic, quotas and approved budget |
| Environments | Leave preview DSN/upload credentials unset initially; later use a separate preview project and explicit environment labels | Existing projects and Netlify variable scopes |
| Build telemetry | Explicit plugin telemetry: false | Effective build configuration |
| Access | Name one monitoring owner and backup; restrict production access | Members, roles and organisation membership settings |
| Retention | Approve the account’s actual retention before activation | Plan, effective retention, region and available controls |
| Privacy | Review disclosure, consent approach and minimised payload settings before activation | Responsible reviewer and approved policy |
Current Sentry JavaScript v11 documentation describes richer data-collection defaults. Masking replay text alone is insufficient. Proposed safeguards: explicitly disable user information, cookies, HTTP headers/bodies and URL query collection, and review error and breadcrumb redaction. These measures do not guarantee anonymity.
Official documentation confirms that retention depends on subscription, environment labels are not equivalent to separate projects, and sampling is not a spending cap.
Sources:
- Retention periods
- SDK configuration and data collection
- Replay privacy
- Source-map upload configuration
- Repository instrumentation at inspected revision
- Vite configuration at inspected revision
Next: obtain the account plan/retention, authorised users, monitoring owner and budget; then approve an exact configuration proposal. Controlled event and source-map verification require separate permission.
Research was static: no records, code or deployments changed during research; no builds or test events were run. Saving these findings does not authorise implementation, activation, test events or deployment. The release outcome remains not decided.
These are proposals for approval, not authorised configuration changes or production activation.
Privacy and replay
- Verify and disclose Sentry’s purpose, collected data, processing arrangements, retention and access controls.
- Confirm the applicable consent approach before activation; masking alone does not establish anonymity.
- Disable session replay initially in production and previews, including error-triggered recording.
- Require separate approval before enabling replay, covering sampling, masking, consent, retention and usage budget.
Environment and credential separation
- Attribute events to the actual deployment environment; previews must not default to
production. - Agree and verify isolation between preview and production telemetry, alerts and reporting.
- Restrict upload credentials to authorised build contexts; exclude secrets from browser bundles, logs and untrusted previews.
- Associate events and source maps with the correct release revision.
Required activation evidence
- Review privacy disclosure and configuration together.
- Obtain separate permission for a controlled test of environment attribution, payload redaction and source-map symbolication.
- Record monitoring ownership, access arrangements and the disable/rollback procedure.
- Assess build-plugin telemetry separately from application monitoring.
Unresolved decisions
Account evidence required before Sentry activation
Sentry
- Plan, hosting region and effective retention period
- Organisation/project names and preview-isolation approach
- Monitoring owner, backup and authorised users/roles
- Event allowance, usage budget and billing alerts
- Approved privacy disclosure, consent approach and payload-redaction requirements
- Explicit decisions on replay, tracing and build-plugin telemetry
Netlify
- Site/project, connected repository and production branch
- Current production deployment URL and commit SHA
- Presence—not values—of
SENTRY_AUTH_TOKEN,SENTRY_ORG,SENTRY_PROJECTandVITE_SENTRY_DSN - Each variable’s build scope and production/branch/Deploy Preview contexts
- Authorised operators for configuration, deployment and monitoring disablement
Implementation handoff requirement
Before implementation proceeds, prepare exact, repository-verified instructions under #206, covering:
- Approved configuration values, file paths and code changes
- Netlify settings and variable scopes, without exposing secrets
- Ordered implementation, deployment and separately authorised test steps
- Expected results, evidence to capture and troubleshooting
- Disablement and rollback instructions
Recheck current repository instructions and account settings when preparing that handoff. Unresolved choices must remain explicit; saving requirements does not authorise implementation, deployment or test events.
- Retention period and verified account capabilities.
- Monitoring owner and authorised access.
- Consent approach.
- Preview/production isolation method.
- Performance sampling and usage budget.
- Build-plugin telemetry policy.
Decision remains not decided. This section authorises no implementation, test-event transmission, merge, deployment or activation.
- Related epic: epic: website - Launch Website v1.0 and reading experience #373
- Newsletter coordination: epic: newsletter - Deliver the book newsletter subscription journey #374
- Retained-form coordination: epic: netlify-forms - Capture website submissions #16
- Related pull requests and decision-record files: none proposed
- Superseded decisions: none identified
Definition of Ready (DoR)
- Decision needed is clearly stated
- Context and constraints described, with evidence linked
- At least two options listed
- Decider identified
Definition of Done (DoD)
- Decision recorded with decider and date
- Consequences and follow-up work captured as linked issues
- Documentation updated through a
docs/PR where files change - Linked issue(s) updated with latest status and closed after merge
- The related epic is not closed; it is updated with a comment reflecting the closed issue
The engineering-related checklist items apply only where relevant; no file changes are proposed. Checklist wording does not authorise updates to linked records or comments on the epic—those require separate approval.
Sentry account evidence and manual verification — 26 October 2026
Screenshot evidence
Screenshots supplied on 25 October show:
- Plan: Developer; free trial ended
- Organisation:
lightspeedwp; data storage region European Union - Project:
thisonetimeonacid; platform React - Usage period: 26 September–25 October 2026
- Usage: 11 errors against a 5,000 allowance; 1 replay against 50; 321 spans against 5 million
- No billing details or payment method on file; displayed additional spend $0
- Debug-file access inherits the organisation’s Admin setting
- Allowed Domains is
*; JavaScript source fetching enabled; SCM Source Context disabled - Book repository connection shows 0 mappings; the Nova News repository shows 1 mapping
- Verify TLS/SSL appears disabled
These are screenshot observations, not a current account inspection. Subscription totals do not establish which project, environment or deployment generated the data, or whether collection continues.
A Security Token was visible in a supplied screenshot. Its value is deliberately excluded. Do not attach the original screenshot to this GitHub-synchronised issue. Review the token’s purpose and dependencies, then obtain approval for replacement where appropriate.
Manual checklist — inspection only
Account, access and ownership
- Confirm effective retention for errors, replays and spans
- Identify the monitoring owner, backup and authorised users/roles
- Record the approved usage budget and notification arrangements
- Review organisation membership settings against intended access
Existing telemetry
- Identify the project, environment, release and dates responsible for recorded errors, replay and spans
- Determine whether data came from production, previews, development or earlier testing
- Confirm current Replay and tracing behaviour without generating new events
- Record discrepancies against the proposed errors-only launch configuration
Repository and source access
- Review why the book repository has no mappings and whether the Nova News mapping belongs in this project
- Review unrestricted Allowed Domains, JavaScript source fetching and disabled TLS verification
- Review the exposed token’s purpose and dependent services; prepare a separate remediation proposal without reproducing it
- Verify source-map access restrictions and distinguish configured controls from tested behaviour
Netlify
- Record the site, connected repository, production branch, production URL and deployed commit SHA
- Record presence and scopes—not values—of
SENTRY_AUTH_TOKEN,SENTRY_ORG,SENTRY_PROJECTandVITE_SENTRY_DSN - Distinguish production, branch and Deploy Preview contexts
- Identify authorised configuration, deployment and monitoring-disable operators
Approval boundary
This checklist authorises evidence gathering only. It does not authorise setting changes, token replacement, builds, deployments, test events or Sentry activation.
After inspection, prepare an exact configuration/remediation proposal for approval. The recommendation remains errors-only initially, with Replay, tracing and preview monitoring disabled pending separate approval.
Release decision remains not decided.
Sentry onboarding and repository mapping — 12 November 2026
User supplied the Sentry project creation page, agent handoff and agent setup guide as future implementation references.
These references do not authorise creating another project, installing SDKs, changing authentication or sending test errors. Verify the existing project and SDK first to avoid duplicate setup.
Do not persist the supplied short-lived handoff credential. Obtain a fresh handoff through Sentry when authorised implementation proceeds. The example account, organisation and setup-code placeholders are not verified account details.
Repository mapping evidence
- The supplied screenshot shows project
thisonetimeonacid, a repository selection truncated in the interface, empty-to-empty path prefixes and branchmain. - The dialog is open with a Save button; persistence is unverified.
- Confirm the full repository identity, relevant deployment revision and source branch before changing the mapping.
- Compare an existing Sentry stack-frame filename with its corresponding repository path before choosing prefixes. Do not guess paths from the screenshot.
Required implementation instructions
Explain each mapping field, provide exact verified values and a worked filename-to-repository example, then describe saving, validation and reversal. Distinguish repository source links from source-map upload and symbolication. Any new test event requires separate permission.
Preserve existing activation gates and unrelated issue content.
Existing-event inspection for repository mapping
Use an existing Sentry error event to establish mapping values. Do not generate test events, change settings, save mappings or alter authentication.
Inspection steps
- Select organisation
lightspeedwpand projectthisonetimeonacid. Open Issues, select an existing error and choose one event occurrence. Record its event ID and timestamp. - Find and expand a stack frame labelled In App. Copy its filename, function and line number. If no such frame exists, record that finding without changing classification settings.
- If the displayed path is unclear, open the event’s
{}JSON view. Copy only the selected frame’sfilenameandabs_path, preserving exact values where present. Do not copy the full event JSON. - Record the selected event’s environment and release. Mark absent fields as “not shown”; do not infer them.
- Open the linked release, where available, and inspect associated commits. Record the repository and relevant commit SHA/link. If several commits are listed, distinguish the list from a verified event or deployment revision.
- Locate the corresponding source file in the repository. Record its repository-relative path and the revision inspected. Do not guess a source file from a minified asset name.
- Compare the frame filename with that repository path before proposing replacement prefixes. Treat the mapping branch as a fallback, not proof of the deployed revision. Confirm the intended fallback branch separately.
Repository mapping links stack frames to repository files. It does not itself upload source maps or establish correct JavaScript symbolication.
Evidence checklist
Event ID:
Event timestamp:
Environment:
Release:
In App frame available: yes / no
Frame filename:
Frame abs_path:
Function and line:
Full repository name:
Matching repository-relative path:
Repository revision inspected:
Associated release commit SHA/link:
Verified deployment SHA, if available:
Intended fallback branch and supporting evidence:
Missing or unclear information:
Privacy and approval boundary
Collect only the fields above. Exclude credentials, tokens, DSN values, full event JSON, request payloads and personal data. Review screenshots for sensitive information before sharing.
Missing release, commit or source-path evidence remains explicitly unresolved. It does not authorise creating another event or guessing mapping values.
After inspection, prepare an exact mapping proposal with verified values, a worked path-translation example, validation and reversal instructions. Obtain separate approval before changing settings; any new test event also requires separate permission.
References
Open Sentry mapping questions for Chris
@chris
- Can an existing In App frame be identified? Record its exact
filename,abs_path, function and line. - Which repository file and revision correspond to that frame?
- What environment, release and commit are associated with the event? Mark unavailable evidence explicitly.
- Based on those paths, what stack-trace and repository prefixes should be proposed?
- Which fallback branch should be used, and what supports that choice?
These are unresolved questions—not approved mapping values. Exclude credentials and personal data; do not generate events or change settings.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Activity
linear-code commentedon Oct 20, 2026
TOA-357