Repository navigation
docs: repository - Correct agent and contributor guidance - #17
Open
netlify-coding[bot] wants to merge 1 commit into
Open
netlify-coding[bot] wants to merge 1 commit into
netlify-coding[bot] wants to merge 1 commit into
Conversation
…ac09402f2a450aa88b1021f)
✅ Deploy Preview for thisonetimeonacid ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
Important Review skippedThis PR was authored by a bot without an assigned CodeRabbit review seat. Ask an organization administrator to assign a seat to the bot. See the seat-assignment guide. After the seat is assigned, request a review again. ⚙️ Run configuration
You can disable this status message by setting the
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
|
Autopilot could not be updated. Open Coding to check access and billing. |
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.
Documentation Pull Request
See the organisation’s Automation Governance & Release Strategy. Template and canonical-label conflicts remain noted below.
Linked issues
Relates to GitHub issue #2, the repository documentation follow-up.
Documentation context: TOA-3, verified through the issue’s Linear linkback.
Retained deployment context: TOA-2.
This PR corrects contributor and agent guidance; it does not reimplement the dependency-name fix. These are references, not closing links. No issue is claimed complete.
What changed
pnpm.overridesand the command in src/app/netlify.toml as unresolved remnants.enginespin.type-checkandverifyare not available package scripts.import.meta.envcontradictions without changing code, with references to vite.config.ts and theimport.meta.env.DEVguidance in guidelines/Guidelines.md.Only the two root guidance documents changed. Dependencies, lockfiles, runtime versions, deployment settings, environment variables, workflows, components, guidelines and the changelog were not modified.
Audience & placement
Preview / Screenshots
Retained references:
Netlify reported the preview ready for head commit
f04980a70b87f41158076ef38714df588473d57a.The existing description attributes the original run to Claude and records a prompt truncated at “deployment fi...”. These remain previously reported information, not independently verified attribution. Missing prompt text has not been reconstructed.
Notes
Base:
76b1528538a9a3658393552c86308ed9a354885donmain.Head:
f04980a70b87f41158076ef38714df588473d57a.Previously reported validation
The original agent reported Node 24.21.0 and npm 11.19.0 with dependencies already installed. Commands were not independently rerun during this metadata review; that environment does not establish Netlify’s current runtime.
npm ls --depth=0npm run journal:validatenpm run journal:check-linksnode --testagainst tests/speckit.test.mjsNot performed by the original agent:
npm ci,npm run build,npm run dev, type-checking, linting, browser or accessibility checks, or the accordion test, becausejsdomwas unavailable. The agent reported that validation commands left the working tree unchanged.Current checks and review evidence
Preview readiness does not establish clean-checkout validation, production routing, completed documentation review or fulfilled issue acceptance criteria.
Outstanding owner decisions
import.meta.envguidance.meta:no-changelog; this does not independently establish a PR exemption.autoprefixer.agent-repository-021fdoes not meet the organisation naming pattern or documentation issue’sdocs/requirement. No branch change is proposed.Metadata-governance findings
type:docs. The develop documentation template still uses legacytype:documentation; it is not substituted for the canonical type.area:documentationis unavailable in this repository. No unrelated area label is substituted.skip-changelog, while canonical labels definemeta:no-changelogandmeta:needs-changelog. PR changelog treatment remains pending an explicit decision.Changelog
No changelog file was changed. The documentation issue’s label does not independently establish a PR-level exemption. These notes describe the documentation changes, not a committed changelog entry.
Added
Changed
Fixed
Removed
Checklist (Global DoD / PR)
meta:no-changelogis applied.